C++ Logo

SG16

Advanced search

Subject: Re: P2295R3 Support for UTF-8 as a portable source file encoding
From: Peter Brett (pbrett_at_[hidden])
Date: 2021-04-29 05:39:05


Hi Corentin,

I think this is a big improvement!

Does anyone know what “physical” means in [lex.phases]:1? I feel like we could remove both occurrences of “physical” from this paragraph without any normative effect.

There is an obvious incomplete merge with P2314, in that the current P2295 wording suggests that UCN doesn’t occur for UTF-8 source files. Just to clarify this, please could we insert a paragraph break before “Any source file character…”?

I don’t have any concerns about forwarding this paper to EWG in its current form.

Best regards,

                            Peter


From: SG16 <sg16-bounces_at_[hidden]> On Behalf Of Corentin via SG16
Sent: 29 April 2021 08:35
To: SG16 <sg16_at_[hidden]>
Cc: Corentin <corentin.jabot_at_[hidden]>
Subject: [SG16] P2295R3 Support for UTF-8 as a portable source file encoding

EXTERNAL MAIL
Per request in yesterday's meeting,
here is P2295R3 Support for UTF-8 as a portable source file encoding.

I am looking forward to your feedback

http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2021/p2295r3.pdf$>



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