C++ Logo


Advanced search

Re: [wg14/wg21 liaison] C and C++ Compatibility Jun Agenda

From: Aaron Ballman <compatibility.sg.chair_at_[hidden]>
Date: Fri, 3 Jun 2022 07:16:35 -0400
Reminder, the Jun SG22 meeting will be happening today in about 4
hours (https://www.timeanddate.com/worldclock/converter.html?iso=20220603T150000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440).

You can join the meeting at https://iso.zoom.us/j/5513145100, details
about the agenda are below.

Hope to see you there!


On Mon, May 30, 2022 at 10:24 AM Aaron Ballman
<compatibility.sg.chair_at_[hidden]> wrote:
> Our next meeting will be on Fri Jun 3, 2022 at 15:00 UTC
> (https://www.timeanddate.com/worldclock/converter.html?iso=20220603T150000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440).
> You can join the meeting at https://iso.zoom.us/j/5513145100
> We will be discussing the following papers:
> P2071R2 (https://wg21.link/p2071r2) Named Universal Character Escapes
> Proposes a new character escape sequence allowing the use of a
> character by Unicode name or name alias instead of by code point value
> (e.g., \N{LATIN CAPITAL LETTER A WITH MACRON}). The authors are
> looking for feedback on whether this approach is appropriate for C as
> well. Additionally, the authors are looking for evidence that \N is
> used as a conditional escape sequence with behavior other than turning
> it into N within a string literal.
> P2558R1 (https://wg21.link/p2558r1) Add @, $, and ` to the basic character set
> Proposes extending the basic character set to require inclusion of
> three new characters. Note the related paper WG14 N2701
> (https://www.open-std.org/jtc1/sc22/wg14/www/docs/n2701.htm) which has
> been adopted by WG14 for inclusion into C2x. The author is looking for
> feedback on whether this is appropriate for C++ as well.
> ~Aaron

Received on 2022-06-03 11:16:49