Subject: Re: [isocpp-core] Updated draft revision: D2029R3 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals
From: Tom Honermann (tom_at_[hidden])
Date: 2020-09-11 09:12:40
The updated revision, with additional changes suggested by Jens
elsewhere in this email thread, has been submitted for the next mailing
and is available at https://isocpp.org/files/papers/P2029R3.html.
If anyone has any further review comments, please let me know!
Mike, I believe this is again ready for Core review.Â I know Core is
continuing to work through Davis' lookup paper, please let me know when
you can fit it in.
On 8/24/20 12:12 AM, Tom Honermann via Core wrote:
> Perhaps it is time to re-title this paper to "Rewrite [lex.ccon] and
> [lex.string]" :)
> An update of D2029R3 is available at
> https://rawgit.com/sg16-unicode/sg16/master/papers/d2029r3.html. This
> addresses the feedback provided at the July 20th, 2020, core issues
> processing telecon.Â The relevant changes include:
> * Changed the introductory and proposed resolution overview to
> remove incorrect uses of "narrowing integer conversion" in prose
> intended to describe something more like an "integral conversion".
> * [lex.ccon]pY: Added footnotes explaining that, for nonencodable
> character literals and multicharacter literals, the associated
> character encoding may be used solely to determine encodability
> and not to actually encode values.
> * [lex.ccon]pZ: Merged Z.1 into the introductory text to make the
> short circuiting behavior clear and renumbered the remaining
> * [lex.ccon]pZ: Specified that the determination of a character
> literal value during translation phase 4 uses the range of
> representable values of the character literal's type in
> translation phase 7.
> * [lex.string]pX: Added normative wording stating that the /n/ that
> appears in the string literal array type corresponds to the number
> of encoded code units.
> * [lex.string]pZ: Elevated notes related to stateful character
> encodings to normative encouragement.
> I believe this is ready for CWG review again.Â Jens, Richard, and
> Hubert, if you can provide any additional change requests before the
> next core issues processing telecon, I would appreciate it.Â I'm
> hoping that the next CWG review will be the last one!
> Core mailing list
> Subscription: https://lists.isocpp.org/mailman/listinfo.cgi/core
> Link to this post: http://lists.isocpp.org/core/2020/08/9750.php
SG16 list run by email@example.com