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.
