<html><body>
<p><font size="2" face="sans-serif"><b>Note the next meeting is in 2 days!</b></font><br>
<br>
<font size="2" face="sans-serif"> </font><font size="2" face="sans-serif"><b>Attendees</b></font><font size="2" face="sans-serif">: Jim, Rajan, Mike, David (12:00 EST)</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"><b> Old action items:</b></font><br>
<font size="2" face="sans-serif"> Jim: Changes to make to part 2:</font><br>
<font size="2" face="sans-serif"> Page 1: does not cover -> neither (Reworded differently)</font><br>
<font size="2" face="sans-serif"> Page 3: Remove lists unless there is an actual change in the identifiers (Done)</font><br>
<font size="2" face="sans-serif"> Page 8: Look at the phrase "they have the" to see if other places may have the existing wording (Kept)</font><br>
<font size="2" face="sans-serif"> Page 19: Line 4: Font on stdio.h is wrong (Done)</font><br>
<font size="2" face="sans-serif"> Jim: Changes to make to all parts: Want macro name: __STDC_WANT_IEC_60559_{BFP, DFP, TYPES, FUNCS, ...}__ (Done)</font><br>
<font size="2" face="sans-serif"> Jim: Send email about WANT macros (Done)</font><br>
<font size="2" face="sans-serif"> All: Review July 10th email regarding 5.2.4.2.2 reorg (Done)</font><br>
<br>
<font size="2" face="sans-serif"><b> Next meeting:</b></font><br>
<font size="2" face="sans-serif"> September 12th, 2013, 12:00 EST, 9:00 PDT</font><br>
<font size="2" face="sans-serif"> October 10th, 2013, 12:00 EST, 9:00 PDT</font><br>
<font size="2" face="sans-serif"> Same teleconference number.</font><br>
<br>
<font size="2" face="sans-serif"><b> New action items:</b></font><br>
<font size="2" face="sans-serif"> Part 1 ballot comments:</font><br>
<font size="2" face="sans-serif"> Jim: GB-JWT comments: Update the response column to the result of our discussion and make it our teleconference group suggested responses.</font><br>
<font size="2" face="sans-serif"> Jim: JWT comments: Submit them as "Editor's comments" with "Study group recommendations" with "Agree" in the last column.</font><br>
<font size="2" face="sans-serif"> Jim: Talk to John to see if we should post a draft with the changes we've agreed to so far.</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"><b> Part 1 comments:</b></font><br>
<font size="2" face="sans-serif"> GB-JWT document:</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"> GB5: We can make this a positive change. i.e. "Part 2 deals with DFP" instead of no change.</font><br>
<font size="2" face="sans-serif"> Jim: We can keep this as an alternative if "No change" is not accepted.</font><br>
<font size="2" face="sans-serif"> GB6: Seems good. If they have more objections, let them bring up more concrete issues why it is not good.</font><br>
<font size="2" face="sans-serif"> GB15: If there is a problem, we should not fix it here (let it be a C11 fix).</font><br>
<font size="2" face="sans-serif"> GB18: Agree to let WG14 look at it.</font><br>
<font size="2" face="sans-serif"> GB19: Mike: IEEE did discuss this issue and determined it (other character sets) was outside of scope for them. Note that this does not necessarily mean it is outside of the C11 scope.</font><br>
<font size="2" face="sans-serif"> C11 uses uppercase. We could defer to WG14 for this since it is referring to existing C11 text.</font><br>
<font size="2" face="sans-serif"> Mike: Only broken in the Turkish special case. It is a point issue so we should defer to WG14. i.e. This is not specific to this IEEE binding.</font><br>
<font size="2" face="sans-serif"> Jim: Making this change may make it incompatible with 60559 since it does not refer to uppercase versions.</font><br>
<font size="2" face="sans-serif"> It would be inconsistent though within the spirit.</font><br>
<font size="2" face="sans-serif"> The text is displayed in English so should the rules not be interpreted using english conversion rules?</font><br>
<font size="2" face="sans-serif"> GB20: This is a set of common changes requested to C11 and just happens to be brought up through this TS since it touches near the sections. We should defer these to WG14 and get guidance on how to handle them in the general sense.</font><br>
<font size="2" face="sans-serif"> GB24: Can help, but not really needed. We can add to make it clearer.</font><br>
<font size="2" face="sans-serif"> GB26: Doing this would require changes to this TS for any math function changes so it will be a large burden.</font><br>
<font size="2" face="sans-serif"> GB30: The "Missing the point" is for us, not the commenter. Perhaps we should say "Clarification is needed why a change is necessary."?</font><br>
<font size="2" face="sans-serif"> GB34: Wasn't this a discussion in WG14 about adding in all the INT macros here? Did we say no?</font><br>
<font size="2" face="sans-serif"> Jim: The discussion was to add all the width macros here and we just missed these ones.</font><br>
<font size="2" face="sans-serif"> GB39: Rajan: Should we allow values other than 1? Ex. -1 for indeterminate</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"> *Is it OK for Jim to update the response column to the result of our discussion and make it our teleconference group suggested responses?</font><br>
<font size="2" face="sans-serif"> Agreed.</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"> Comments from JWT:</font><br>
<font size="2" face="sans-serif"> *We discussed these already and will submit them as "Editor's comments" with "Study group recommendations" with "Agree" in the last column.</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"> *Jim has a draft with the changes we've discussed so far. He will talk to John to see if we should post it to the WG14 documents page.</font><br>
<font size="2" face="sans-serif"> </font><br>
<font size="2" face="sans-serif"> Part 2 (cfp2-20130910.pdf):</font><br>
<font size="2" face="sans-serif"> Looks good since we discussed the rounding mode in emails already.</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></body></html>