<html><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;"><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>This is part of action item:</div><div><br></div><div><blockquote type="cite"> Jim & Damian: Jim to send to CFP an email with suggested wording changes for complex.h. Damian to update the proposal based on these and other suggestions. Jim to get a document number for Damian, then submit the updated proposal.</blockquote></div><div><br></div><div>The changes (from CFP meeting discussion) are for the draft proposal in [Cfp-interest 3436]:</div><div><br></div><div>1. Change:</div><div><br></div><blockquote style="margin: 0px 0px 0px 40px; border: medium; padding: 0px;">Reference: N3467</blockquote><div><br></div><div>to:</div><div><br></div><blockquote style="margin: 0px 0px 0px 40px; border: medium; padding: 0px;">References: N3390, N3460, N3467</blockquote><div><br></div><div><br></div><div>2. In the suggested change to 7.3.1#3, change:</div><div><br></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>… its real and imaginary parts being positive or unsigned zero and one, respectively,</div></div></blockquote><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><br></div><div>to:</div><div><br></div></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div>… its real part being positive or unsigned zero and its imaginary part being one,</div></div></blockquote><div dir="auto" style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div><br></div><div><br></div><div>3. For the changes to 7.3.1#4, use code typeface (with strikethrough red) for code elements (f, l, float, and long double) in strikethrough red. </div><div><br></div><div><br></div><div>4. Replace the last sentence of the Background Rationale section of the proposal with:</div><div><br></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>The existing paragraph #4 is misstated: It says “… and<span id="x-apple-selection:start"></span><span id="x-apple-selection:end"></span> other functions … which are corresponding functions with <font face="Courier New">float</font> and <font face="Courier New">long double</font> parameters and return values.” However, the parameter types and most of the return types for these functions are complex types. Existing paragraph #4 is also missing an explanation of the scenario for the <font face="Courier New">CMPLX</font> family of macros. </div><div><br></div><div><br></div></blockquote>5. Place the Background Rationale section before the Suggested Changes section.<br><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div><br></div></blockquote><br></div></body></html>