Please keep the conversation on the mailing list, don't reply just to me. I've CC'd the gcc-help list where this belongs (not gcc@xxxxxxxxxxx). On 9 May 2018 at 11:43, SHIH YEN-TE wrote: > It won't get compiled... What is "it"? > error: unable to find string literal operator 'operator"" XXXX' > > > Am I missing something? Yes, you're missing the source code that you tried to compile, and the information about which GCC version you're using, and how you invoked it. > > > > ________________________________ > 寄件者: Jonathan Wakely <jwakely.gcc@xxxxxxxxx> > 寄件日期: 2018年5月9日 下午 04:58 > 收件者: SHIH YEN-TE > 副本: gcc@xxxxxxxxxxx > 主旨: Re: About Bug 52485 > > 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.
