[Development] QStringLiteral is broken(ish) on MSVC (compiler bug?)

Matthew Woehlke mwoehlke.floss at gmail.com
Mon Mar 18 17:02:01 CET 2019

On 16/03/2019 12.13, Giuseppe D'Angelo via Development wrote:
> What I meant is this: during phase 5 and 6, are string literals 
> simply sequences of symbols from a set, or are they already encoded 
> in some encoding? From my reading, it's the former (the execution
> character set is just this -- a set of symbols), and it's only after
> phase 6 that those symbols are encoded in sequences of
> char/char16_t/... values (depending on the string literal prefix).
I would certainly read 5 as *implying* that at the conclusion of that
phase, string literals have a definite encoding. *Not* applying that
assumption seems to be how we get the broken MSVC behavior of
"reinterpreting" a UTF-8 string as CP-1252.


More information about the Development mailing list