<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>Based on the status of the current issues, we will not hold the CFP meeting we reserved for tomorrow (February 8). Our next scheduled CFP meeting will be Wednesday, February 28.</div><div><br></div><div>Status</div><div><br></div><div>1. <a href="https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3101.pdf" style="font-variant-ligatures: normal; orphans: 2; widows: 2;">N3101</a><span style="font-variant-ligatures: normal; orphans: 2; widows: 2;"> 2023/02/05 Thomas, Issues with CFP response to NB comments</span></div><div>I’ve requested an n-number for an N3101 update to fix the problem Joseph reported in [SC22WG14.23086]. I don’t think CFP needs to do anything else with this until we hear from WG14.<br><br>2. <a href="http://mailman.oakapple.net/pipermail/cfp-interest/2023-February/002698.html" style="orphans: 2; widows: 2;">[Cfp-interest 2684] Re: floating constants issue </a><a name="2698" style="orphans: 2; widows: 2;"> </a><span style="orphans: 2; widows: 2;"> </span><i style="orphans: 2; widows: 2;">Jim Thomas</i><br>No negative response so far. This can be submitted as a NB comment for CD2.<br><br>3. <a href="http://mailman.oakapple.net/pipermail/cfp-interest/2023-February/002700.html" style="orphans: 2; widows: 2;">[Cfp-interest 2686] Re: incorrect example H.12.2p4 </a><a name="2700" style="orphans: 2; widows: 2;"> </a><span style="orphans: 2; widows: 2;"> </span><i style="orphans: 2; widows: 2;">Jim Thomas</i><br>No response yet. This can be submitted as a NB comment for CD2.<br><br>4. <a href="http://mailman.oakapple.net/pipermail/cfp-interest/2023-February/002692.html" style="orphans: 2; widows: 2;">[Cfp-interest 2678] H.2.1 </a><a name="2692" style="orphans: 2; widows: 2;"> </a><span style="orphans: 2; widows: 2;"> </span><i style="orphans: 2; widows: 2;">Fred J. Tydeman</i><br>This is strictly editorial. It can be sent to the editor, with a Cc to WG14.</div><div>Fred, will you do that?<br><br>5. issues with types</div><div><a href="http://mailman.oakapple.net/pipermail/cfp-interest/2023-February/002689.html" style="orphans: 2; widows: 2;">[Cfp-interest 2675] Re: WG14 IEEE 754-C binding meeting minutes 2023/01/31 </a><a name="2689" style="orphans: 2; widows: 2;"> </a><span style="orphans: 2; widows: 2;"> </span><i style="orphans: 2; widows: 2;">Vincent Lefevre</i></div><div><a href="http://mailman.oakapple.net/pipermail/cfp-interest/2023-February/002701.html" style="orphans: 2; widows: 2;">[Cfp-interest 2687] Re: WG14 IEEE 754-C binding meeting minutes 2023/01/31 </a><a name="2701" style="orphans: 2; widows: 2;"> </a><span style="orphans: 2; widows: 2;"> </span><i style="orphans: 2; widows: 2;">Jim Thomas</i></div><div><a href="http://mailman.oakapple.net/pipermail/cfp-interest/2023-February/002702.html" style="orphans: 2; widows: 2;">[Cfp-interest 2688] Re: WG14 IEEE 754-C binding meeting minutes 2023/01/31 </a><a name="2702" style="orphans: 2; widows: 2;"> </a><span style="orphans: 2; widows: 2;"> </span><i style="orphans: 2; widows: 2;">Vincent Lefevre</i></div><div><a href="http://mailman.oakapple.net/pipermail/cfp-interest/2023-February/002703.html" style="orphans: 2; widows: 2;">[Cfp-interest 2689] Re: WG14 IEEE 754-C binding meeting minutes 2023/01/31 </a><a name="2703" style="orphans: 2; widows: 2;"> </a><span style="orphans: 2; widows: 2;"> </span><i style="orphans: 2; widows: 2;">Vincent Lefevre</i></div><div><a href="http://mailman.oakapple.net/pipermail/cfp-interest/2023-February/002704.html" style="orphans: 2; widows: 2;">[Cfp-interest 2690] Re: WG14 IEEE 754-C binding meeting minutes 2023/01/31 </a><a name="2704" style="orphans: 2; widows: 2;"> </a><span style="orphans: 2; widows: 2;"> </span><i style="orphans: 2; widows: 2;">Jim Thomas</i><i style="orphans: 2; widows: 2;"><br></i>Email discussion is continuing.</div><div><br></div><div>Please let me know if you are aware of other CFP issues for C23.<br><br>- Jim Thomas<br><br><br><br><br></div></body></html>