[Cfp-interest 1997] AIs related to range errors clarifications

Jim Thomas jaswthomas at sbcglobal.net
Sat Apr 24 17:08:11 PDT 2021


Action items:

>    Jim: Look at the use of the word “normal” in the C standard to ensure
> the use in range error clarifications is OK.
>    Jim: Range errors: Issue 1: Instead of “below” in the footnote, use a
> clause/subclause number.
>    Jim: Create proposals for range error clarifications.
> 


Please review the following:

https://wiki.edg.com/pub/CFP/WebHome/C23_proposal_-_range_error_definition-20210424.pdf <https://wiki.edg.com/pub/CFP/WebHome/C23_proposal_-_range_error_definition-20210424.pdf>

https://wiki.edg.com/pub/CFP/WebHome/C23_proposal_-_overflow_and_underflow_definitions-20210424.pdf <https://wiki.edg.com/pub/CFP/WebHome/C23_proposal_-_overflow_and_underflow_definitions-20210424.pdf>

https://wiki.edg.com/pub/CFP/WebHome/C23_proposal_-_Annex_F_overflow_and_underflow-20210424.pdf <https://wiki.edg.com/pub/CFP/WebHome/C23_proposal_-_Annex_F_overflow_and_underflow-20210424.pdf>

https://wiki.edg.com/pub/CFP/WebHome/C23_proposal_-_effects_of_fenv_exception_functions-20210424.pdf <https://wiki.edg.com/pub/CFP/WebHome/C23_proposal_-_effects_of_fenv_exception_functions-20210424.pdf>


- Jim Thomas



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


More information about the Cfp-interest mailing list