Reminder: this is happening in about five hours (17:00 UTC
(https://www.timeanddate.com/worldclock/converter.html?iso=20210604T170000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440&p6=tz_cest)!

You can join the meeting at https://iso.zoom.us/j/5513145100 with the
same password used as last time.

We will be discussing the following papers:

P2312R1 (https://wg21.link/p2312r1) Introduce the nullptr constant
P2338R0 (https://wg21.link/p2338r0) Freestanding Library: Character
primitives and the C library
P1949R7 (https://wg21.link/p1949r7) C++ Identifier Syntax using
Unicode Standard Annex 31

Thanks!

~Aaron

On Thu, May 27, 2021 at 6:47 AM Aaron Ballman
<compatibility.sg.chair_at_[hidden]> wrote:
>
> Our next meeting will be on Fri June 4, 2021 at 17:00 UTC
> (https://www.timeanddate.com/worldclock/converter.html?iso=20210604T170000&p1=tz_pt&p2=tz_mt&p3=tz_ct&p4=tz_et&p5=1440&p6=tz_cest).
>
> You can join the meeting at https://iso.zoom.us/j/5513145100 with the
> same password used as last time.
>
> We will be discussing the following papers:
>
> P2312R1 (https://wg21.link/p2312r1) Introduce the nullptr constant
> Proposes to add 'nullptr' to C as a logical replacement for the NULL
> macro. This constant is intended to be compatible with the C++ nullptr
> concept. The author is especially interested in hearing about
> potential accidental incompatibilities with C++ or other
> implementation concerns.
>
> P2338R0 (https://wg21.link/p2338r0) Freestanding Library: Character
> primitives and the C library
> Proposes requiring much of the C library (and C portions of the C++
> library) to be available in freestanding implementations in C++. This
> includes many of the character/string based functions (strcpy, memcpy,
> etc).
>
> P1949R7 (https://wg21.link/p1949r7) C++ Identifier Syntax using
> Unicode Standard Annex 31
> Proposes mapping the allowable characters in an identifier to the ones
> specified by the Unicode standard in Annex 31 (Unicode Identifier and
> Pattern Syntax). This paper has been approved for a plenary vote to
> include it in C++23 but is not yet adopted. The author is looking for
> feedback and potentially polls on whether these changes should also be
> pursued in C.
>
> Thanks!
>
> ~Aaron