Tuesday, 30 June 2020
- Re: [SG16] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
- Re: [SG16] [isocpp-core] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
- Re: [SG16] [isocpp-core] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
- Re: [SG16] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
- Re: [SG16] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
- Re: [SG16] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
- Re: [SG16] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
- Re: [SG16] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
- Re: [SG16] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
- Re: [SG16] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
Sunday, 28 June 2020
- Re: [SG16] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
- Re: [SG16] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
- [SG16] New draft revision: D2029R2 (Proposed resolution for core issues 411, 1656, and 2333; numeric and universal character escapes in character and string literals)
Wednesday, 24 June 2020
Tuesday, 23 June 2020
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- [SG16] SG16 meeting summary for June 17th, 2020
- [SG16] WG21 SG16 (Unicode) teleconference
Monday, 22 June 2020
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] [boost] [review] [text] Text formal review
- Re: [SG16] [boost] [review] [text] Text formal review
- Re: [SG16] Emojis in identifiers
Sunday, 21 June 2020
- Re: [SG16] [boost] [review] [text] Text formal review
- Re: [SG16] [boost] [review] [text] Text formal review
- Re: [SG16] [boost] [review] [text] Text formal review
- [SG16] [boost] [review] [text] Text formal review
- Re: [SG16] What do we want from source to internal conversion?
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] What do we want from source to internal conversion?
Saturday, 20 June 2020
- Re: [SG16] What do we want from source to internal conversion?
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- Re: [SG16] Handling of non-basic characters in early translation phases
- [SG16] Handling of non-basic characters in early translation phases
Friday, 19 June 2020
Thursday, 18 June 2020
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- Re: [SG16] Emojis in identifiers
- [SG16] Emojis in identifiers
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] Virtual evolution meeting on Unicode identifiers, Thursday June 18th @ 10AM Pacific
- Re: [SG16] [isocpp-ext] Virtual evolution meeting on Unicode identifiers, Thursday June 18th @ 10AM Pacific
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] [isocpp-ext] Virtual evolution meeting on Unicode identifiers, Thursday June 18th @ 10AM Pacific
Wednesday, 17 June 2020
- Re: [SG16] C9X RATIONALE WG14/N850
- [SG16] C9X RATIONALE WG14/N850
- Re: [SG16] [isocpp-core] Seeking guidance on use, overloading, or overriding of terms used in normative references
- Re: [SG16] Goals for rewording [lex] et. al..
- Re: [SG16] [isocpp-core] Seeking guidance on use, overloading, or overriding of terms used in normative references
- Re: [SG16] Goals for rewording [lex] et. al..
- [SG16] Seeking guidance on use, overloading, or overriding of terms used in normative references
- Re: [SG16] Goals for rewording [lex] et. al..
- [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-17)
Tuesday, 16 June 2020
Monday, 15 June 2020
- Re: [SG16] What do we want from source to internal conversion?
- Re: [SG16] What do we want from source to internal conversion?
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] What do we want from source to internal conversion?
- Re: [SG16] What do we want from source to internal conversion?
- Re: [SG16] What do we want from source to internal conversion?
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] What do we want from source to internal conversion?
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] What do we want from source to internal conversion?
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] What do we want from source to internal conversion?
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] What do we want from source to internal conversion?
- [SG16] What do we want from source to internal conversion?
- Re: [SG16] Terminology
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
Sunday, 14 June 2020
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] [wg14/wg21 liaison] Characters literals in preprocessor conditionals
- Re: [SG16] Terminology
- Re: [SG16] [wg14/wg21 liaison] Characters literals in preprocessor conditionals
- Re: [SG16] [wg14/wg21 liaison] Characters literals in preprocessor conditionals
- Re: [SG16] [wg14/wg21 liaison] Characters literals in preprocessor conditionals
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Terminology
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
Saturday, 13 June 2020
- Re: [SG16] SG16 meeting summary for June 10th, 2020
- Re: [SG16] SG16 meeting summary for June 10th, 2020
- [SG16] SG16 meeting summary for June 10th, 2020
- [SG16] Updated: WG21 SG16 (Unicode) teleconference
- [SG16] Updated: WG21 SG16 (Unicode) teleconference
- Re: [SG16] WG21 SG16 (Unicode) teleconference
- [SG16] WG21 SG16 (Unicode) teleconference
Friday, 12 June 2020
- Re: [SG16] Characters literals in preprocessor conditionals
- Re: [SG16] Characters literals in preprocessor conditionals
Thursday, 11 June 2020
- [SG16] Fwd: [review] [text] Text formal review
- Re: [SG16] Characters literals in preprocessor conditionals
- Re: [SG16] Characters literals in preprocessor conditionals
- Re: [SG16] Terminology
- [SG16] Characters literals in preprocessor conditionals
- Re: [SG16] Terminology
- Re: [SG16] Terminology
Wednesday, 10 June 2020
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- [SG16] Agreeing with Corentin's point re: problem with strict use of abstract characters
- Re: [SG16] Terminology
- Re: [SG16] Terminology
- Re: [SG16] Terminology
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- [SG16] Terminology
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
Tuesday, 9 June 2020
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- Re: [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
- [SG16] Reminder: SG16 telecon tomorrow (Wednesday, 2020-06-10)
Friday, 5 June 2020
- [SG16] P1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
Thursday, 4 June 2020
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- [SG16] D1949R4 - C++ Identifier Syntax using Unicode Standard Annex 31
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
Wednesday, 3 June 2020
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
Tuesday, 2 June 2020
- Re: [SG16] [isocpp-core] To which extent characters can be replaced or removed in phase 1?
- Re: [SG16] Is it an error to encounter a character without a valid UCN?
- [SG16] Is it an error to encounter a character without a valid UCN?
Monday, 1 June 2020
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] Fwd: Making wide-character literals containing multiple c-char ill-formed
- Re: [SG16] Fwd: Making wide-character literals containing multiple c-char ill-formed
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] Fwd: Making wide-character literals containing multiple c-char ill-formed
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] During lexing, What constitute new lines and whitespaces ?
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] During lexing, What constitute new lines and whitespaces ?
- Re: [SG16] During lexing, What constitute new lines and whitespaces ?
- Re: [SG16] Fwd: Making wide-character literals containing multiple c-char ill-formed
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] During lexing, What constitute new lines and whitespaces ?
- Re: [SG16] During lexing, What constitute new lines and whitespaces ?
- Re: [SG16] During lexing, What constitute new lines and whitespaces ?
- Re: [SG16] During lexing, What constitute new lines and whitespaces ?
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- [SG16] During lexing, What constitute new lines and whitespaces ?
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- [SG16] Fwd: Making wide-character literals containing multiple c-char ill-formed
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding
- Re: [SG16] Conversion of grapheme clusters to (wide) execution encoding