About Bug 52485

About Bug 52485

[SHIH YEN-TE]

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. I know it is ridiculous, but we must know the real world is somehow ridiculous as well as nothing is perfect.

Re: About Bug 52485

[Marc Glisse]

On Wed, 9 May 2018, 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. I know it is ridiculous, 
> but we must know the real world is somehow ridiculous as well as nothing 
> is perfect.

You have the wrong approach.

Apparently, you are using an unmaintained library (if it was maintained, 
it would be compatible with C++11 by now), so there is no problem 
modifying it, especially just to add a few spaces. A single run of 
clang-tidy would likely fix all of them for you.

-- 
Marc Glisse

Re: About Bug 52485

[Will Hawkins]

Thanks to your brand new Bugzilla account, you may now comment! :-)


You will receive instructions on how to reset your default default
password and access your account. Please let me know if you have any
questions or trouble gaining access.

I'd be happy to help in any way that I can!

Thanks for contributing to GCC!
Will


On Wed, May 9, 2018 at 4:08 AM, SHIH YEN-TE <shihyente@hotmail.com> 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. I know it is ridiculous, but we must know the real world is somehow ridiculous as well as nothing is perfect.
>
>

Re: About Bug 52485

[Jonathan Wakely]

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.