[cfp-interest 3398] Re: Results of CFP papers in the WG14 2025/02/24 meeting

[Jim Thomas]

Rajan,

Thanks for representing our papers, and for the report!

See response about N3357 below.

- Jim

> On Feb 27, 2025, at 7:54 AM, RAJAN BHAKTA <rbhakta at us.ibm.com> wrote:
> 
> Hello,
>  
> Here are the unofficial (official requires the meeting closure review of decisions reached and meeting minutes) results for our papers:
>  
> N3357 failed, all other papers (N3461*, N3460, N3492*, N3405*, N3452) passed.
> * Also put into the list for guidance for previous standards.
>  
> Details:
>  
> N3357: frexp and double – Failed (not integrated into C2Y).
>   Ballman: Just throwing in "model" may not be as clear. Can we have more words around it to show it is the floating point model. Something like a footnote.
>   Jens: Perhaps say "the model given in 5.2.5.3.3"?
>   Seacord: Say "C model" vs "model".

We proposed 

… a model floating-point number (5.2.5.3.3) …

5.2.5.3.3 begins "The characteristics of floating types are defined in terms of a model that describes a representation of floating-point numbers …”, and refers to “Model floating-point numbers" in paragraphs 4-7. The parenthetical reference seems clear enough to me, but I don’t have any objection to the suggestions: 

#2
… a floating-point number in the C model given in 5.2.5.3.3 ...

#3
 …  If value is not a floating-point number in the C model …

Was this the only objection to N3357? Would an updated paper help?

- Jim
>  
>   ^Straw poll: Decision: Put N3357 into C2Y?
>     0+1/6+13/0+3. No consensus to put N3357 into C2Y.
>  
> N3461: Range error definition followup (updates N3383) – Passed (Put into C2Y and previous standard guidance)
>   Jens: Would be helpful to say the function the changes apply to.
>  
>   ^Straw poll: Decision: Put N3461 into C2Y?
>     6+14/0/0+2. Put N3461 into C2Y.
>  
>   ^Decision: Put N3461 into the list of corrections to previous revisions to C.
>     Unanimous consent.
>  
> N3460: Complex operators (updates N3406) – Passed (Put into C2Y)
>   Jens: Very happy with this.
>   
>   ^Straw poll: Decision: Put N3460 into C2Y?
>     6+15/0/0+2. Put N3460 (move parts of complex/real operations into main body of the standard) into C2Y.
>  
> N3492: Improved treatment of error conditions for functions that round result to narrow type - Passed (Put into C2Y and previous standard guidance)
>   Banham: Why are we weakening?
>   Rajan: Divergent practice.
>  
>   ^Straw poll: Decision: Put N3492 into C2Y?
>     5+10/0+2/1+7. Put N3492 into C2Y.
>   ^Decision: Put N3492 into the list of corrections to previous revisions to C.
>     Unanimous consent.
>  
> N3405: Improved wording for treatment of error conditions in <math.h> - Passed (Put into C2Y and previous standard guidance)
>   Jens: "Can" should be "may".
>   Seacord: This is not either or, it is must. So it is correct the way it is.
>  
>   ^Straw poll: Decision: Put N3405 into C2Y?
>     5+10/0+1/0+6. Put N3405 into C2Y.
>   ^Decision: Put N3405 into the list of corrections to previous revisions to C.
>     Unanimous consent.
>  
> N3452: Complex literals warning – Passed (Put into C2Y)
>   Seacord: "Since" means passage of time. Should use "Because" instead.
>   
>   ^Straw poll: Decision: Put N3452 into C2Y?
>     5+14/0/0+5. Put N3452 into C2Y.
>  
> Regards,
> 
> Rajan Bhakta
>  
> _______________________________________________
> 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/20250227/48f7a1dd/attachment-0001.htm>