<html><body>
<p><font size="2" face="sans-serif">n1757: IEEE binding part 2</font><br>
<font size="2" face="sans-serif"> <a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1766.pdf">http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1766.pdf</a></font><br>
<font size="2" face="sans-serif"> Presenter: Jim Thomas</font><br>
<font size="2" face="sans-serif"> Make all parts based on C11 + previous parts:</font><br>
<font size="2" face="sans-serif"> Blaine: Do you have an applied change document?</font><br>
<font size="2" face="sans-serif"> Jim: I do, but as a text document</font><br>
<font size="2" face="sans-serif"> Larry: Hard to do as a PDF</font><br>
<font size="2" face="sans-serif"> John: Too much of a burden for this group</font><br>
<font size="2" face="sans-serif"> uchar encodings:</font><br>
<font size="2" face="sans-serif"> Blaine: Are the encodings canonical?</font><br>
<font size="2" face="sans-serif"> Jim: Up to byte order as for other C data types</font><br>
<font size="2" face="sans-serif"> Moving forward:</font><br>
<font size="2" face="sans-serif"> Teleconference meeting on October 10th, for focused review.</font><br>
<font size="2" face="sans-serif"> Can have a mid-October - mid-November WG14 review to have a PDTS ballot at end of November. If significant comments, we can have a WG14 telecon at the end of November and ballot at the beginning of December.</font><br>
<font size="2" face="sans-serif"> This will allow ballot resolution for our WG14 April meeting</font><br>
<font size="2" face="sans-serif"> Blaine: To what degree has this been sanity tested? i.e. Empty functions, headers, compiled fine</font><br>
<font size="2" face="sans-serif"> Jim: This is an extension to the decimal TR so already has implementations out there. Intel also has implemented this internally. There is no reference implementation.</font><br>
<font size="2" face="sans-serif"> John: That is the goal of a TS so we want people to create implementations, and not have reference ones needed.</font><br>
<font size="2" face="sans-serif"> Agree to move forward with the plan. </font><br>
<br>
<font size="2" face="sans-serif">n1758: IEEE binding part 3</font><br>
<font size="2" face="sans-serif"> <a href="http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1765.pdf">http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1765.pdf</a></font><br>
<font size="2" face="sans-serif"> Presenter: Jim Thomas</font><br>
<font size="2" face="sans-serif"> Type structure additions:</font><br>
<font size="2" face="sans-serif"> WG14: Seems good now since it is simpler</font><br>
<font size="2" face="sans-serif"> String to/from encoding functions:</font><br>
<font size="2" face="sans-serif"> Blaine: Are the contents of the string described by IEEE?</font><br>
<font size="2" face="sans-serif"> Jim: It is in C11.</font><br>
<font size="2" face="sans-serif"> John: What is the effect of issuing a new TC for C11</font><br>
<font size="2" face="sans-serif"> Jim: We couldn't change 1 and maybe 2, but later ones can be based on C11 + all TC's.</font><br>
<font size="2" face="sans-serif"> Douglas: Make sure all parts define the set of values N can have.</font><br>
<font size="2" face="sans-serif"> Blaine: The N's give implementations leeway to say what they support (except the required ones).</font><br>
<font size="2" face="sans-serif"> John: Has work been done on parts 4 and 5? We can keep the 1 year schedule if so.</font><br>
<br>
<font size="2" face="sans-serif">Regards,<br>
<br>
Rajan Bhakta<br>
z/OS XL C/C++ Compiler Technical Architect<br>
ISO C Standards Representative for Canada<br>
C Compiler Development<br>
Contact: rbhakta@us.ibm.com, Rajan Bhakta/Houston/IBM</font><br>
</body></html>