[Cfp-interest 2646] Re: 2023/01 WG14 final meeting results

[Jim Thomas]

It looks like the best time for our followup CFP meeting will be

	Tuesday, January 31, 8 AM PST / 11 AM EST / 4 PM UTC

Later today I’ll send separate email with Zoom information and suggested responses to the issues from the WG14 meeting.

- Jim Thomas

> On Jan 28, 2023, at 10:40 AM, Jim Thomas <jaswthomas at sbcglobal.net> wrote:
> 
> I think we should follow Rajan’s recommendation and arrange a CFP meeting next week to followup on the issues he noted.
> 
> If you plan to attend, which of these days would you be available at the usual CFP time (8 AM PST / 11 AM EST / 4 PM UTC):
> 
> Tuesday, January 31
> Wednesday, February 1
> Thursday, February 2
> 
> - Jim Thomas
> 
> 
> 
> 
>> On Jan 27, 2023, at 9:52 AM, Rajan Bhakta <rbhakta at us.ibm.com> wrote:
>> 
>> Key points:
>> We will not finish reviewing all the comments this meeting so it will continue on for another week: February 13-17, 2023.
>> There will be a second CD ballot.
>> All CFP resolutions in N3082 were accepted with some caveats for US42-169 (wrong “similar” section), GB-286 (specification wanted now), GB-287 (specification wanted now for main body of the standard)
>>  
>> Details:
>> US42-169: We listed “Similar 7.24.1.3 has …” but that section does not seem similar at all. We need to look at this and provide feedback before the extended WG14 meeting (including the February part) ends.
>> GB-286: WG14 wants us to give the specification for wcstofN and wcstodN functions. If we can do that before the February meeting, we can address the comment then. If not, WG14 will ask us to do so for CD 2.
>> GB-287: WG14 wants us to give wording to allow hexadecimal input into strtod* in the main body of the standard.
>>  
>> My recommendations (can discuss on the reflector):
>> We should have a CFP meeting to write the specification for GB-286, GB-287 and review it before the next WG14 meeting (in February). We should send it in at least one week before the meeting.
>> We should update the reference in US42-169 to whatever we intended, or just strike that reference and instead make it similar to nextafter.
>>  
>> Regards,
>> 
>> Rajan Bhakta
>> z/OS XL C/C++ Compiler Technical Architect
>> ISO C Standards Representative (Canada, USA), PL22.11 Chair
>> C/C++ Compiler Development
>> rbhakta at us.ibm.com <mailto:rbhakta at us.ibm.com>
>>  
>> IBM
>>  
>> _______________________________________________
>> Cfp-interest mailing list
>> Cfp-interest at oakapple.net <mailto:Cfp-interest at oakapple.net>
>> http://mailman.oakapple.net/mailman/listinfo/cfp-interest 
>> _______________________________________________
>> Cfp-interest mailing list
>> Cfp-interest at oakapple.net <mailto:Cfp-interest at oakapple.net>
>> http://mailman.oakapple.net/mailman/listinfo/cfp-interest
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.oakapple.net/pipermail/cfp-interest/attachments/20230129/f697b1e3/attachment-0001.htm>