Date: Wed, 26 Oct 2022 11:56:42 -0400
Please review the following. If you agree with the proposed change and
have no further information to add, then there is no need to respond. If
you disagree with the proposed change, have corrections or new
information to offer, or have comments on the candidate polls, then
*please reply by Monday, October 31st*.
FR 5.3p5.2 [lex.charset] <http://eel.is/c++draft/lex.charset>
Codepoint names in identifiers
GitHub nbballot issue #423
<https://github.com/cplusplus/nbballot/issues/423>.
Comment:
The XID_Start and XID_Continue properties that form the identifier
grammar are extracted from Unicode. But character names are extracted
from ISO 10646.
Because Unicode and ISO 10646 do not have the same release schedule, not
all characters valid in identifiers can be spelled with the \N{} syntax.
This inconsistency could be avoided by referring to Unicode directly in
the specification of the \N{} escape sequences.
Proposed change:
Please refer to Unicode consistently for all Unicode properties, using a
consistent set of references pertaining to the same version of Unicode.
SG16 chair notes:
This comment is related to FR [Bibliography] Unify references to Unicode
<https://github.com/cplusplus/nbballot/issues/412>.
Candidate polls:
* [FR-XX]: SG16 recommends accepting the comment in the direction of
the proposed change by 1) replacing references to ISO/IEC 10646 with
references to the Unicode Standard, and 2) updating all Unicode
references to Unicode 15.
* [FR-XX]: SG16 recommends rejecting the comment as not a defect.
Tom.
have no further information to add, then there is no need to respond. If
you disagree with the proposed change, have corrections or new
information to offer, or have comments on the candidate polls, then
*please reply by Monday, October 31st*.
FR 5.3p5.2 [lex.charset] <http://eel.is/c++draft/lex.charset>
Codepoint names in identifiers
GitHub nbballot issue #423
<https://github.com/cplusplus/nbballot/issues/423>.
Comment:
The XID_Start and XID_Continue properties that form the identifier
grammar are extracted from Unicode. But character names are extracted
from ISO 10646.
Because Unicode and ISO 10646 do not have the same release schedule, not
all characters valid in identifiers can be spelled with the \N{} syntax.
This inconsistency could be avoided by referring to Unicode directly in
the specification of the \N{} escape sequences.
Proposed change:
Please refer to Unicode consistently for all Unicode properties, using a
consistent set of references pertaining to the same version of Unicode.
SG16 chair notes:
This comment is related to FR [Bibliography] Unify references to Unicode
<https://github.com/cplusplus/nbballot/issues/412>.
Candidate polls:
* [FR-XX]: SG16 recommends accepting the comment in the direction of
the proposed change by 1) replacing references to ISO/IEC 10646 with
references to the Unicode Standard, and 2) updating all Unicode
references to Unicode 15.
* [FR-XX]: SG16 recommends rejecting the comment as not a defect.
Tom.
Received on 2022-10-26 15:56:46