C++ Logo


Advanced search

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

From: Aaron Ballman <compatibility.sg.chair_at_[hidden]>
Date: Sun, 18 Sep 2022 11:00:00 -0400
Reminder: the SG22 meeting will be happening about 24 hours from now.
Hope to see you there!


On Wed, Sep 7, 2022 at 1:31 PM Aaron Ballman
<compatibility.sg.chair_at_[hidden]> wrote:
> Our next meeting will be on Mon Sept 19, 2022 at 15:00 UTC
> (https://www.timeanddate.com/worldclock/converter.html?iso=20220919T150000&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
> P2142R1 (https://wg21.link/p2142r1) Allow '.' operator to work on pointers
> This paper explores allowing pointer member access through the '.'
> operator instead of requiring it to go through the '->' operator. The
> author is looking for feedback on the proposal, and expects to take a
> straw poll on whether SG22 thinks there should be further work along
> these lines in both committees.
> P2621R0 (https://wg21.link/p2621r0) UB? In my Lexer?
> The paper is proposing to strengthen lexing-related undefined behavior
> into requiring a diagnostic or making it well-defined. It does not
> attempt to address all preprocessing related undefined behavior. The
> author is looking for encouragement with the idea as well as feedback
> on impact to implementations which may have extensions in these areas.
> P1854R3 (https://wg21.link/p1854r3) Conversion to literal encoding
> should not lead to loss of meaning
> This paper proposes making use of characters which cannot be
> represented in the literal encoding be ill-formed when use in
> character and string literals. Further, it restricts the set of valid
> characters in a multicharacter literal. Both are done in an attempt to
> make lexing less surprising in the presence of non-Latin characters in
> the source. The author is looking for feedback on the idea,
> particularly in C, as the paper was already approved by EWG in WG21.
> ~Aaron

Received on 2022-09-18 15:00:06