C++ Logo

SG16

Advanced search

Subject: Re: [SG16-Unicode] [wg14/wg21 liaison] [isocpp-core] Source file encoding (was: What is the proper term for the locale dependent run-time character set/encoding used for the character classification and conversion functions?)
From: Thiago Macieira (thiago_at_[hidden])
Date: 2019-08-14 14:53:12


On Wednesday, 14 August 2019 10:01:19 PDT Joseph Myers wrote:
> The present implementation-defined interpretation of the byte sequence in
> source files allows a default of "UTF-8 in strings, comments can use
> arbitrary bytes" (which thus allows existing source files in a range of
> ASCII-compatible 8-bit character sets if the non-ASCII characters only
> appear in comments, without needing to tell the compiler which character
> set is being used).

That's not correct. MSVC does interpret the bytes in comments and will
complain if it can't decode from the 8-bit ACS to UTF-16.

That also means most legacy 8-bit-encoded files with high-bit comments will
not compile with /utf-8.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel System Software Products

SG16 list run by sg16-owner@lists.isocpp.org