<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Aug 5, 2021, at 12:18 PM, Rajan Bhakta <<a href="mailto:rbhakta@us.ibm.com" class="">rbhakta@us.ibm.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><p class=""><font size="2" face="sans-serif" class="">Looking at the specification, I think the only thing that really works is to do something like the following:</font><br class=""><font size="2" face="sans-serif" class="">1) Say for freestanding that error conditions do not necessarily have to be handled (including setting errno). This would have the new side effect of not requiring using exceptions as well.</font><br class=""><font size="2" face="sans-serif" class="">or</font><br class=""><font size="2" face="sans-serif" class="">2) Change the strtod family of functions to allow exceptions to be used for error reporting instead of just errno. This would be a change to the general C standard, but likely more palatable.</font><br class=""></p></div></div></blockquote><div><br class=""></div>I think 2) would be straightforward, following 7.12.1 #5 and #6, introducing stdilb_errhandling, STDLIB_ERRNO, and STDLIB_ERREXCEPT. We’d need to insert in F.5: "The expression stdlib_errhandling & STDLIB_ERREXCEPT shall evaluate to a nonzero value.”</div><div><br class=""></div><div>- Jim Thomas</div><div><blockquote type="cite" class=""><div class=""><div class=""><p class=""><br class=""><font size="2" face="sans-serif" class="">With regards to the whitespace and decimal point scanning, as long as we allow a freestanding implementation to have just the C locale (as it is now) and a single fixed code page, I think it would work for freestanding. The issues described in WG14 19444 still apply however meaning the code is not necessarily portable, but this may be something we either accept, or mandate that the C locale must be used.</font><br class=""><br class=""><font size="2" face="sans-serif" class="">Regards,<br class=""><br class=""></font><font size="2" face="sans-serif" class=""><b class="">Rajan Bhakta</b></font><font size="2" face="sans-serif" class=""><br class="">z/OS XL C/C++ Compiler Technical Architect<br class="">ISO C Standards Representative (Canada, USA), PL22.11 Chair<br class="">C/C++ Compiler Development</font><br class=""><font size="2" face="sans-serif" class=""><a href="mailto:rbhakta@us.ibm.com" class="">rbhakta@us.ibm.com</a></font><br class=""><br class=""><font size="2" face="sans-serif" class="">IBM</font><br class="">
<br class="">
</p></div>
_______________________________________________<br class="">Cfp-interest mailing list<br class=""><a href="mailto:Cfp-interest@oakapple.net" class="">Cfp-interest@oakapple.net</a><br class="">http://mailman.oakapple.net/mailman/listinfo/cfp-interest<br class=""></div></blockquote></div><br class=""></body></html>