<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 20, 2013, at 8:01 PM, "Fred J. Tydeman" <<a href="mailto:tydeman@tybor.com">tydeman@tybor.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Wed, 20 Mar 2013 18:09:42 -0700 Jim Thomas wrote:<br><blockquote type="cite"><br><blockquote type="cite"><br>PDF page 26, lines 26-28: Do we want SNANF32, SNANF64, SNANF80 (or<br>SNANF64X), SNANF128?<br></blockquote><br>No. For example, SNANF and Part 3's SNANF32 have different types.<br></blockquote><br>Part 3, PDF page 8, last paragraph mentions redundant ways to<br>refer to the same format. So, I am somewhat confused.<br></blockquote><div><br></div><div>"<span style="font-family: ArialMT; font-size: 10pt; ">This specification incudes interchange and extended nomenclatures for types that, in some cases, already
have C nomenclatures" needs to be changed. The different nomenclature are for different types, even if the formats are the same.</span></div>
<div class="page" title="Page 8">
<div class="layoutArea">
<div class="column"><p><span style="font-size: 10.000000pt; font-family: 'ArialMT'"> <br></span></p>
</div>
</div>
</div><blockquote type="cite"><br>Part 3, PDF page 10, ISSUE 2 mentions that Part 1 5.1 should be<br>split to match Part 3. Seems like now would be a good time to<br>do that.<br></blockquote><div><br></div>Right, except we can't change the document because it's in WG 14 review.</div><div><br></div><div>-Jim</div><div><br><blockquote type="cite"><br>---<br>Fred J. Tydeman Tydeman Consulting<br><a href="mailto:tydeman@tybor.com">tydeman@tybor.com</a> Testing, numerics, programming<br>+1 (775) 287-5904 Vice-chair of PL22.11 (ANSI "C")<br>Sample C99+FPCE tests: <a href="http://www.tybor.com">http://www.tybor.com</a><br>Savers sleep well, investors eat well, spenders work forever.<br></blockquote></div><br></body></html>