https://codereview.qt-project.org/#/c/183817/
On Mon, Jan 30, 2017 at 4:42 PM, Marc Mutz <marc.m...@kdab.com> wrote: > On Monday 30 January 2017 02:21:57 Thiago Macieira wrote: > > qCDebug(lcTuioSet) << "Processing SET for token " << classId << id > << " > > @ " << x << y << "∡" << angle << > > > > That's easy to fix by using "\342\210\241" instead. > > Which is totally and utterly opaque. So much so that one feels forced to > add a > comment > > // ∡ > > but then MSVC complains, too. > > Lose-lose. > > The question really is: why does this come up only now? Is it because of > MSVC2015, and does it thus mean that only compilers that provide the /utf-8 > option warn? In that case, the correct thing is to enable the option and > leave > UTF-8 chars in the source alone. > > Thanks, > Marc > > -- > Marc Mutz <marc.m...@kdab.com> | Senior Software Engineer > KDAB (Deutschland) GmbH & Co.KG, a KDAB Group Company > Tel: +49-30-521325470 > KDAB - The Qt, C++ and OpenGL Experts > _______________________________________________ > Development mailing list > Development@qt-project.org > http://lists.qt-project.org/mailman/listinfo/development >
_______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
