<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="">754 5.12.1 also says<div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">Language standards should provide an optional conversion of NaNs in a supported format to external character sequences which appends to the basic NaN character sequences a suffix that can represent the NaN payload (see 6.2). The form and interpretation of the payload suffix is language-defined. The language standard shall require that any such optional output sequences be accepted as input in conversion of external character sequences to supported formats.</div></blockquote><div class=""><br class=""></div><div class="">This might not be relevant to Rajan’s proposal (email today).</div><div class=""><br class=""></div><div class="">- Jim Thomas<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jul 26, 2018, at 4:38 PM, Fred J. Tydeman <<a href="mailto:tydeman@tybor.com" class="">tydeman@tybor.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Wed, 25 Jul 2018 11:24:55 -0500 Rajan Bhakta wrote:<br class=""><blockquote type="cite" class=""><br class=""> NaNQ/NaNS proposal:<br class=""><br class=""> Look at current 754 draft to see if NaNQ/NaNS violates it.<br class=""><br class=""></blockquote>754: 5.12.1: <br class="">Conversion of a quiet NaN in a supported format to an external character sequence shall produce a<br class="">language-defined one of "nan" or a sequence that is equivalent except for case (e.g., "NaN"), with an<br class="">optional preceding sign. (This standard does not interpret the sign of a NaN.)<br class=""><br class="">Conversion of a signaling NaN in a supported format to an external character sequence should produce a<br class="">language-defined one of "snan" or "nan" or a sequence that is equivalent except for case, with an optional<br class="">preceding sign. If the conversion of a signaling NaN produces "nan" or a sequence that is equivalent except<br class="">for case, with an optional preceding sign, then the invalid operation exception should be signaled.<br class=""><br class="">Conversion of an external character sequence "snan" (regardless of case) with an optional preceding sign,<br class="">to a supported format should either produce a signaling NaN or else produce a quiet NaN and signal the<br class="">invalid operation exception.<br class=""><br class=""><br class="">Since the above is 'should', not 'shall', NaNS is allowed by 754.<br class="">However, NaNQ is not allowed.<br class=""><br class="">C99/C11/C17 allow for NaN(Q) and NaN(S), but not NaNQ and NaNS.<br class=""><br class=""><br class="">---<br class="">Fred J. Tydeman Tydeman Consulting<br class=""><a href="mailto:tydeman@tybor.com" class="">tydeman@tybor.com</a> Testing, numerics, programming<br class="">+1 (702) 608-6093 Vice-chair of PL22.11 (ANSI "C")<br class="">Sample C99+FPCE tests: <a href="http://www.tybor.com" class="">http://www.tybor.com</a><br class="">Savers sleep well, investors eat well, spenders work forever.<br class=""><br class="">_______________________________________________<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></div></blockquote></div><br class=""></div></body></html>