This is the mail archive of the gcc-help@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Prohibit enum <-> int mixup

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: weigelt at metux dot de, gcc-help at gcc dot gnu dot org
Date: Sun, 30 Jan 2011 20:54:58 +0000
Subject: Re: Prohibit enum <-> int mixup
References: <20110129164124.GA27641@nibiru.local> <mcr39obpn8r.fsf@google.com> <20110129204856.GA29226@nibiru.local> <AANLkTi=1eim813RowJe0gya19nemWZPeLp_AwiZucU0S@mail.gmail.com> <AANLkTimua1k+ZkEBgEibggvSMDjiP4+sBgGwNj0moS_b@mail.gmail.com> <20110130201121.GD29226@nibiru.local> <AANLkTinKOkAEfyPyFTbtjtUEe9MvM-AoX7n3ZjCoCvK1@mail.gmail.com> <20110130203231.GE29226@nibiru.local>

On 30 January 2011 20:32, Enrico Weigelt wrote:
>
> I'll have to add --std=c++0x parameter - does that have any other
> side effects I should be aware of ?

-std=c++0x enables lots of things, but if you don't use e.g. variadic
templates or the decltype keyword you shouldn't notice.  The only
thing I can think of affecting valid code is changing the meaning of
the 'auto' keyword, which noone sensible uses anyway.

Follow-Ups:
- Re: Prohibit enum <-> int mixup
  - From: Kevin P. Fleming
- Re: Prohibit enum <-> int mixup
  - From: Ian Lance Taylor

References:
- Prohibit enum <-> int mixup
  - From: Enrico Weigelt
- Re: Prohibit enum <-> int mixup
  - From: Ian Lance Taylor
- Re: Prohibit enum <-> int mixup
  - From: Enrico Weigelt
- Re: Prohibit enum <-> int mixup
  - From: Jonathan Wakely
- Re: Prohibit enum <-> int mixup
  - From: Jonathan Wakely
- Re: Prohibit enum <-> int mixup
  - From: Enrico Weigelt
- Re: Prohibit enum <-> int mixup
  - From: Jonathan Wakely
- Re: Prohibit enum <-> int mixup
  - From: Enrico Weigelt

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]