This is the mail archive of the gcc@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: About Bug 52485

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: SHIH YEN-TE <shihyente at hotmail dot com>
Cc: "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
Date: Wed, 9 May 2018 09:58:36 +0100
Subject: Re: About Bug 52485
References: <BL0PR20MB2067F524AE80917B4C8DA3ECB6990@BL0PR20MB2067.namprd20.prod.outlook.com>

On 9 May 2018 at 09:08, SHIH YEN-TE wrote:
> Want to comment on "Bug 52485 - [c++11] add an option to disable c++11 user-defined literals"
>
>
> It's a pity GCC doesn't support this, which forces me to give up introducing newer C++ standard into my project.

Why do you have to give up?

> I know it is ridiculous, but we must know the real world is somehow ridiculous as well as nothing is perfect.

Which is why GCC will only warn and not error when it sees ill-formed
uses of macros following string literals without whitespace. So you
should still be able to compile code that isn't compatible with C++11
user-defined literals.

References:
- About Bug 52485
  - From: SHIH YEN-TE

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