Further notes:

SG-16 did review and agree with the wording.

CWG asked for the wording to be changed to replace all whitespaces in phase
1.
Because I do not see how that would be compatible with my goal of having a
clear grammar for whitespace and comments, I elected not to pursue that
work further.

I do agree with the GB comment that the current state is undesirable but I
do not know how to remediate that issue.

Thanks,
Corentin


On Wed, Oct 26, 2022 at 5:57 PM Tom Honermann via SG16 <
sg16_at_[hidden]> wrote:

> Please review the following. If you agree with the proposed change and
> have no further information to add, then there is no need to respond. If
> you disagree with the proposed change, have corrections or new information
> to offer, or have comments on the candidate polls, then *please reply by
> Monday, October 31st*. GB 5.2 [lex.phases]
> <http://eel.is/c++draft/lex.phases> Clarification of wording on new-line
> and whitespace
>
> GitHub nbballot issue #432
> <https://github.com/cplusplus/nbballot/issues/432>.
> Comment:
>
> Clarification of wording on new-line and whitespace.
> The specification of new-line and whitespace should be updated following
> changes to the C++ working paper, such as P2314 adopted in Oct 2021.
> Proposed change:
>
> We propose adopting a revision of P2348 ("Whitespaces Wording Revamp").
> SG16 chair notes:
>
> Did SG16 review P2348? I can't recall.
>
> Link to CWG review of P2348.
> Candidate polls:
>
> - [GB-XX]: SG16 recommends accepting the comment in the direction of
> the proposed change.
> - [GB-XX]: SG16 recommends rejecting the comment as not a defect.
>
>
>
> Tom.
> --
> SG16 mailing list
> SG16_at_[hidden]
> https://lists.isocpp.org/mailman/listinfo.cgi/sg16
>