From owner-sc22wg14+sc22wg14-domo2=www.open-std.org@open-std.org Sat Mar 9 23:37:23 2024 Return-Path: X-Original-To: sc22wg14-domo2 Delivered-To: sc22wg14-domo2@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 77DF3356D26; Sat, 9 Mar 2024 23:37:23 +0100 (CET) Delivered-To: sc22wg14@open-std.org Received: from smtp90.iad3b.emailsrvr.com (smtp90.iad3b.emailsrvr.com [146.20.161.90]) by www.open-std.org (Postfix) with ESMTP id 14D5935691C for ; Sat, 9 Mar 2024 23:37:21 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=honermann.net; s=20180930-2j89z3ji; t=1710023840; bh=VwaqZW19wM62uMpB/8tfHyGYt6nRgO3dljNttPzWEag=; h=Date:Subject:To:From:From; b=ihC2eoJ3PNiM0js3gzX3yNwjQ0li1cT16jEgZ3Y+zS4dUxKL6flg13dqPu0IgsoNy ztP8Vrvy5IEQjagKuvR1Qmf/aiierySrNyeviZp+a0gIAa7kSph88iZV8EXNv0Z2kr 7lRyj9EMeWBcF2ebC6MwZmCb/cJs+LTS9H+CgwP4= X-Auth-ID: tom@honermann.net Received: by smtp4.relay.iad3b.emailsrvr.com (Authenticated sender: tom-AT-honermann.net) with ESMTPSA id 7FB70200FA; Sat, 9 Mar 2024 17:37:20 -0500 (EST) Content-Type: multipart/alternative; boundary="------------6KIIHXf5WhZZTBdi06XktOyZ" Message-ID: <87492d54-8c27-47ca-a3dc-f7db724eeac2@honermann.net> Date: Sat, 9 Mar 2024 17:37:20 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [SC22WG14.24736] D.2.1 and UAX#31 revision 39 Content-Language: en-US To: Joseph Myers , sc22wg14@open-std.org References: <20240213223038.E4AB3356D43@www.open-std.org> From: Tom Honermann In-Reply-To: <20240213223038.E4AB3356D43@www.open-std.org> X-Classification-ID: e61d354f-5044-4846-a1a6-5fdbbf82bc9a-1-1 Sender: owner-sc22wg14@open-std.org Precedence: bulk This is a multi-part message in MIME format. --------------6KIIHXf5WhZZTBdi06XktOyZ Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit For anyone wishing to pursue a paper for this, WG21 SG16 discussed the Unicode 15.1.0 change to UAX #31 in the context of C++ CWG issue CWG 2843 (Undated reference to Unicode makes C++ a moving target) . Summaries of our discussion can be found at the following locations. Discussion of the UAX #31 change is in the last entry. * 2024-01-10 SG16 meeting . * 2024-02-07 SG16 meeting . * 2024-02-21 SG16 meeting . With respect to the UAX31-R1a rule, SG16 established consensus to accept the Unicode 15.1.0 changes to default identifiers (as opposed to adopting a profile like the Default-Ignorable Exclusion Profile ) and intends to amend our conformance statement in annex E accordingly. I encourage WG14 to do similarly so that identifier syntax remains compatible across C and C++. Tom. On 2/13/24 5:30 PM, Joseph Myers wrote: > D.2.1 Restricted Format Characters refers to an option UAX#31-R1a that > appears to have been removed in the latest revision (revision 39) of > UAX#31. > > Rather than attempting to do anything about this for C23, I suggest that > the people dealing with Unicode issues for C should write a short paper > for C2y that either removes D.2.1 or otherwise addresses how it refers to > something no longer in UAX#31. (In the absence of such a paper, this is > now on my list of issues to file once we have an issue tracking system set > up.) > --------------6KIIHXf5WhZZTBdi06XktOyZ Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit

For anyone wishing to pursue a paper for this, WG21 SG16 discussed the Unicode 15.1.0 change to UAX #31 in the context of C++ CWG issue CWG 2843 (Undated reference to Unicode makes C++ a moving target). Summaries of our discussion can be found at the following locations. Discussion of the UAX #31 change is in the last entry.

With respect to the UAX31-R1a rule, SG16 established consensus to accept the Unicode 15.1.0 changes to default identifiers (as opposed to adopting a profile like the Default-Ignorable Exclusion Profile) and intends to amend our conformance statement in annex E accordingly. I encourage WG14 to do similarly so that identifier syntax remains compatible across C and C++.

Tom.

On 2/13/24 5:30 PM, Joseph Myers wrote:
D.2.1 Restricted Format Characters refers to an option UAX#31-R1a that 
appears to have been removed in the latest revision (revision 39) of 
UAX#31.

Rather than attempting to do anything about this for C23, I suggest that 
the people dealing with Unicode issues for C should write a short paper 
for C2y that either removes D.2.1 or otherwise addresses how it refers to 
something no longer in UAX#31.  (In the absence of such a paper, this is 
now on my list of issues to file once we have an issue tracking system set 
up.)
--------------6KIIHXf5WhZZTBdi06XktOyZ--