This is the mail archive of the gcc-patches@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: [ C++ 4.6 Patch] allow uninitialized const or reference members with -fpermissive

From: Jason Merrill <jason at redhat dot com>
To: Fabien Chêne <fabien dot chene at gmail dot com>
Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>
Date: Tue, 24 May 2011 21:37:14 -0400
Subject: Re: [ C++ 4.6 Patch] allow uninitialized const or reference members with -fpermissive
References: <BANLkTi=boEPmYasJKte_Co=g_HyRiH4oeg@mail.gmail.com> <4DD83624.1080705@redhat.com> <BANLkTinrYwnNbH75eMA0LVU-hyOGVRXJZQ@mail.gmail.com>

On 05/24/2011 04:40 PM, Fabien Chêne wrote:

Indeed. I have also added two testcases to check sfinae on 'new T',
with and without -fpermissive, which leads to a different result.

We don't want to do that; overload resolution should always produce the same result. We can only be permissive in non-SFINAE context.

Jason

Follow-Ups:
- Re: [ C++ 4.6 Patch] allow uninitialized const or reference members with -fpermissive
  - From: Fabien Chêne

References:
- [ C++ 4.6 Patch] allow uninitialized const or reference members with -fpermissive
  - From: Fabien Chêne
- Re: [ C++ 4.6 Patch] allow uninitialized const or reference members with -fpermissive
  - From: Jason Merrill
- Re: [ C++ 4.6 Patch] allow uninitialized const or reference members with -fpermissive
  - From: Fabien Chêne

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