<html aria-label="message body"><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">These comments refer to <a href="https://cfp-wiki.esi.com.au/pub/CFP/WebHome/C2Y-F-Introduction-20260401.pdf">https://cfp-wiki.esi.com.au/pub/CFP/WebHome/C2Y-F-Introduction-20260401.pdf</a> .<div><br></div><div>1.</div><div>The first statement in your F.3#20 is<div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>No C function f in Table F.2 and Table F.3 is required to be correctly rounded. </div><div><br></div><div>To the contrary, all C functions in Table F.2 are required to be correctly rounded.</div><div><br></div><div>2.</div><div>In F.3#1, in the convertToIntegerTiesToAway row, second column, add a comma after ufromfp.</div><div><br></div><div>3.</div><div>I think the new table about rounding directions (F.3#???) belongs in current F.3#10. It could be introduced with something like:</div><div><br></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div>The C rounding directions refer to the ISO/IEC 60559 rounding direction attributes and correspond to the rounding direction macros (7.6) as shown in Table n.</div></div></blockquote><div><div><br></div><div>followed by the table.</div><div><br></div><div>To accomodate decimal, a column for the rounding direction macros for decimal could be added to the table and a reference to the table could be added at the end of F.3#18. </div><div><br></div><div>The table title might be</div><div><br></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><div>Table F.n — ISO/IEC 60559 rounding for C </div></div></blockquote><div><div><br></div><div>The header might be:</div><div><br></div><div>Rounding direction | ISO/IEC 60559 attribute | Macro for binary | Macro for decimal</div><div><br></div><div>Since the only information added by the table is the correspondence between the C rounding directions “toward zero”, etc. and 60559 attributes, that correspondence could be stated in words and a table would not be necessary.</div><div><br></div><div>If the table is added, some of the text in #10 and #18 could be omitted.</div><div><br></div><div>4.</div><div>General comment: I haven’t reviewed all of this paper. The given Rationale claims many miscellaneous improvements have been made. With so many suggested changes I find it difficult to focus on a specific issue, understand whether there’s a problem that needs to fixed, and review the suggested changes for that specific issue. The emerging SpecialCases proposal follows from a CFP decision to pursue regularizing the form for specification of special cases in Annex F. It also addresses multiple issues but those mostly relate to the agreed objective and we've discussed issues separately. For “F-Introduction” is there a unifying objective that CFP needs to agree on pursuing? Are there specific issues that would be better addressed in separate papers?</div><div><br></div><div>- Jim Thomas<br id="lineBreakAtBeginningOfMessage"><div><br></div></div></div></body></html>