On Thursday, 14 March 2019 13:54:29 PDT NIkolai Marchenko wrote:
> I've posted about this issue (I think) on slack a bit earlier, see
> https://cpplang.slack.com/archives/C29936TQC/p154989901601
For those who can't read it, the suggestion was to use the /utf-8 option to
the compiler (with
I've posted about this issue (I think) on slack a bit earlier, see
https://cpplang.slack.com/archives/C29936TQC/p154989901601
On Thu, Mar 14, 2019 at 11:51 PM Matthew Woehlke
wrote:
> While working on some modernization of my application — in particular,
> converting some UTF-8 literals to
On 14/03/2019 16.50, Matthew Woehlke wrote:
> While working on some modernization of my application — in particular,
> converting some UTF-8 literals to use QStringLiteral — I noticed a
> concerning compiler warning:
>
> warning C4566: character represented by universal-character-name
>
While working on some modernization of my application — in particular,
converting some UTF-8 literals to use QStringLiteral — I noticed a
concerning compiler warning:
warning C4566: character represented by universal-character-name
'\u' cannot be represented in the current code page
