Date: Wed, 11 May 2022 12:08:27 -0400
Thank you, Steve!
This appears to address the primary concerns raised during our last
telecon <https://github.com/sg16-unicode/sg16-meetings#april-27th-2022>.
A few minor comments:
1. In the example in section 3.1, please add a comment to indicate the
character denoted by \u0060.
2. In section 3.6, there seems to be something missing between
"semantics if" and "is allowed". Perhaps some markup is missing.
"It is conditionally supported with implementation defined semantics
if is allowed, from which we can infer that universal character
names are conditionally supported."
3. In section 3.3, "invarient" -> "invariant".
Tom.
On 5/11/22 12:46 AM, Steve Downey wrote:
> I have updated 2558R1 with the requested addition of Annex C to Wording.
> https://isocpp.org/files/papers/P2558R1.html
>
> Add to Annex C
>
> *C.n C++ and ISO C++ 2023* [diff.cpp23]
>
> *C.n.1 [lex]: lexical conventions* [diff.cpp23.lex]
>
> 1
>
> *Affected subclause:* [lex.charset]
>
> *Change:* The characters $, @, and ` may not be represented as a
> /universal-character-name/ outside a literal
>
> *Rationale:* Inclusion of these characters in the basic character set.
>
> *Effect on original feature:* The characters were not allowed in
> semantically meaningful text outside of literals, but could still be
> present in early phases of translation as /universal-character-names/.
>
> [Example 1:
>
> |#include <stdio.h> #define STR(x)#x int main() { printf("%s",
> STR(\u0024)); // Was allowed, now is not an allowed UCN }|
>
> — end example]
>
> [Example 2:
>
> |#include <stdio.h> #define EAT(x) int main() { EAT(\u0024) // Was
> allowed, now is not an allowed UCN }|
>
> — end example]
>
>
>
> On Mon, May 9, 2022 at 5:30 PM Tom Honermann via SG16
> <sg16_at_[hidden]> wrote:
>
> SG16 will hold a telecon on Wednesday, May 11th, at 19:30 UTC
> (timezone conversion
> <https://www.timeanddate.com/worldclock/converter.html?iso=20220511T193000&p1=1440&p2=tz_pdt&p3=tz_mdt&p4=tz_cdt&p5=tz_edt&p6=tz_cest>).
>
> The agenda is:
>
> * D2286R8: Formatting Ranges
> <https://brevzin.github.io/cpp_proposals/2286_fmt_ranges/p2286r8.html>
> o Review and approve final wording updates.
> * D2558R1: Add @, $, and ` to the basic character set
> <https://isocpp.org/files/papers/D2558R1.html>
> o Continue review pending the availability of an updated
> revision.
> * D2572R0: std::format() fill character allowances
> <https://rawgit.com/tahonermann/std-proposals/master/d2572r0.html>
> o Continue review pending the availability of an updated
> revision.
>
> I expect this to be our last review of P2286 unless something
> surprising and new is identified.
>
> Further review of P2558 and P2572 are still contingent upon new
> draft revisions by their authors. If new revisions don't
> materialize, then we can hope for quite a short meeting!
>
> Tom.
>
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>
This appears to address the primary concerns raised during our last
telecon <https://github.com/sg16-unicode/sg16-meetings#april-27th-2022>.
A few minor comments:
1. In the example in section 3.1, please add a comment to indicate the
character denoted by \u0060.
2. In section 3.6, there seems to be something missing between
"semantics if" and "is allowed". Perhaps some markup is missing.
"It is conditionally supported with implementation defined semantics
if is allowed, from which we can infer that universal character
names are conditionally supported."
3. In section 3.3, "invarient" -> "invariant".
Tom.
On 5/11/22 12:46 AM, Steve Downey wrote:
> I have updated 2558R1 with the requested addition of Annex C to Wording.
> https://isocpp.org/files/papers/P2558R1.html
>
> Add to Annex C
>
> *C.n C++ and ISO C++ 2023* [diff.cpp23]
>
> *C.n.1 [lex]: lexical conventions* [diff.cpp23.lex]
>
> 1
>
> *Affected subclause:* [lex.charset]
>
> *Change:* The characters $, @, and ` may not be represented as a
> /universal-character-name/ outside a literal
>
> *Rationale:* Inclusion of these characters in the basic character set.
>
> *Effect on original feature:* The characters were not allowed in
> semantically meaningful text outside of literals, but could still be
> present in early phases of translation as /universal-character-names/.
>
> [Example 1:
>
> |#include <stdio.h> #define STR(x)#x int main() { printf("%s",
> STR(\u0024)); // Was allowed, now is not an allowed UCN }|
>
> — end example]
>
> [Example 2:
>
> |#include <stdio.h> #define EAT(x) int main() { EAT(\u0024) // Was
> allowed, now is not an allowed UCN }|
>
> — end example]
>
>
>
> On Mon, May 9, 2022 at 5:30 PM Tom Honermann via SG16
> <sg16_at_[hidden]> wrote:
>
> SG16 will hold a telecon on Wednesday, May 11th, at 19:30 UTC
> (timezone conversion
> <https://www.timeanddate.com/worldclock/converter.html?iso=20220511T193000&p1=1440&p2=tz_pdt&p3=tz_mdt&p4=tz_cdt&p5=tz_edt&p6=tz_cest>).
>
> The agenda is:
>
> * D2286R8: Formatting Ranges
> <https://brevzin.github.io/cpp_proposals/2286_fmt_ranges/p2286r8.html>
> o Review and approve final wording updates.
> * D2558R1: Add @, $, and ` to the basic character set
> <https://isocpp.org/files/papers/D2558R1.html>
> o Continue review pending the availability of an updated
> revision.
> * D2572R0: std::format() fill character allowances
> <https://rawgit.com/tahonermann/std-proposals/master/d2572r0.html>
> o Continue review pending the availability of an updated
> revision.
>
> I expect this to be our last review of P2286 unless something
> surprising and new is identified.
>
> Further review of P2558 and P2572 are still contingent upon new
> draft revisions by their authors. If new revisions don't
> materialize, then we can hope for quite a short meeting!
>
> Tom.
>
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>
Received on 2022-05-11 16:08:30