<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;">Action items from the 2 August CFP meeting:<div><br></div><div><blockquote type="cite"><p class="MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"> Jim: Be consistent with the rest of the standard for section 5.3 in the TS (the "if and only if" part).</p><p class="MsoNormal" style="margin: 0in; font-size: 11pt; font-family: Calibri, sans-serif;"> All: Consider weakening "if and only if" to "if" to allow more implementation latitude. Comes with the cost of being less consistent with the rest of the standard.</p><br class="Apple-interchange-newline"></blockquote><div><br></div><div>cfp4r 5.3 says:<div><br></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;"><div>The types and functions whose definitions or declarations are specified in this document are defined or declared by the <math.h> headers if and only if __STDC_WANT_IEC_60559_FUNCS_EXT__ is defined as a macro at the point in the source file where the header is first included.</div></blockquote><div><br></div><div>The issue was whether “if and only if” should be replaced by “if”. The WANT macros in the standard are</div><div><br></div><div>__STDC_WANT_IEC_60559_EXT__</div><div>__STDC_WANT_LIB_EXT1__</div><div>__STDC_WANT_IEC_60559_TYPES_EXT__</div><div><br></div><div>It’s usual in the standard for library interfaces conditioned by these WANT macros to be defined or declared only if the WANT macro is appropriately defined by the user. The reason is namespace protection, and WG 14 members have expressed significant interest in namespace protection. I think we should keep the “if and only” wording, for namespace protection and consistency.</div></div></div><div><br></div><div>- Jim Thomas</div></body></html>