3 ms·
Well, technically the rule only talks about entries that "fail to compile". An entry that still compiles is fine, see rule 12. In practice this means the Unicod
by GlitchMr 5y ago
Well, technically the rule only talks about entries that "fail to compile". An entry that still compiles is fine, see rule 12. In practice this means the Unicode abuse like this is only allowed in strings.
- lifthrasiir 5y agoWhen the rule was originally introduced in 2001 [1] it was a total ban. It seems that the rule was slightly relaxed in 2013 [2], but I think it still massively discourages any octet >= 128 because there is no portable way to set the input encoding (like GCC `-finput-charset`, which is ignored by Clang AFAIK). [1] https://www.ioccc.org/2001/rules https://www.ioccc.org/2001/rules [2] https://www.ioccc.org/2013/rules.txt https://www.ioccc.org/2013/rules.txt