diff options
| -rw-r--r-- | libstdc++-v3/ChangeLog | 11 | ||||
| -rw-r--r-- | libstdc++-v3/docs/html/ext/howto.html | 7 | ||||
| -rw-r--r-- | libstdc++-v3/docs/html/ext/lwg-active.html | 6978 | ||||
| -rw-r--r-- | libstdc++-v3/docs/html/ext/lwg-defects.html | 4658 | ||||
| -rw-r--r-- | libstdc++-v3/include/bits/list.tcc | 69 |
5 files changed, 6934 insertions, 4789 deletions
diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index e5658be7a05..afd8d1d1e35 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,14 @@ +2003-11-08 Paolo Carlini <pcarlini@suse.de> + + PR libstdc++/12967 + * include/bits/list.tcc (merge): Implement resolution of + DR 300 [WP]. + * docs/html/ext/howto.html: Add entry for DR 300; tweak entry + for DR 231. + + * docs/html/ext/lwg-active.html, docs/html/ext/lwg-defects.html: + Import R27. + 2003-11-07 Jonathan Wakely <redi@gcc.gnu.org> * libsupc++/vec.cc: Conform to C++STYLE. diff --git a/libstdc++-v3/docs/html/ext/howto.html b/libstdc++-v3/docs/html/ext/howto.html index f9e7cb6e4d4..21b5dad072b 100644 --- a/libstdc++-v3/docs/html/ext/howto.html +++ b/libstdc++-v3/docs/html/ext/howto.html @@ -593,7 +593,7 @@ for const instances. </dd> - <dt><a href="lwg-active.html#231">231</a>: + <dt><a href="lwg-defects.html#231">231</a>: <em>Precision in iostream?</em> </dt> <dd>For conversion from a floating-point type, <code>str.precision()</code> @@ -646,6 +646,11 @@ <dd>If <code>(this == &rhs)</code> do nothing. </dd> + <dt><a href="lwg-defects.html#300">300</a>: + <em>List::merge() specification incomplete</em> + </dt> + <dd>If <code>(this == &x)</code> do nothing. + </dd> <!-- <dt><a href="lwg-defects.html#"></a>: <em></em> diff --git a/libstdc++-v3/docs/html/ext/lwg-active.html b/libstdc++-v3/docs/html/ext/lwg-active.html index a69d6c67c40..235e51dce36 100644 --- a/libstdc++-v3/docs/html/ext/lwg-active.html +++ b/libstdc++-v3/docs/html/ext/lwg-active.html @@ -1,15 +1,14 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> -<html> -<head><title>C++ Standard Library Active Issues List</title></head> -<body bgcolor="#ffffff" text="#000000"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"><html><head><title>C++ Standard Library Active Issues List</title></head> + +<body text="#000000" bgcolor="#ffffff"> <table> -<tr> +<tbody><tr> <td align="left">Doc. no.</td> -<td align="left">J16/02-0048 = WG21 N1390</td> +<td align="left">N1515 = 03-0098</td> </tr> <tr> <td align="left">Date:</td> -<td align="left">10 Sep 2002</td> +<td align="left">20 Sep 2003</td> </tr> <tr> <td align="left">Project:</td> @@ -19,19 +18,19 @@ <td align="left">Reply to:</td> <td align="left">Matt Austern <austern@apple.com></td> </tr> -</table> -<h1>C++ Standard Library Active Issues List (Revision 23)</h1> +</tbody></table> +<h1>C++ Standard Library Active Issues List (Revision 27)</h1> <p>Reference ISO/IEC IS 14882:1998(E)</p> <p>Also see:</p> <ul> <li> -<a href="lwg-toc.html">Table of Contents</a> for all library issues.</li> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-toc.html">Table of Contents</a> for all library issues.</li> <li> -<a href="lwg-index.html">Index by Section</a> for all library issues.</li> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-index.html">Index by Section</a> for all library issues.</li> <li> -<a href="lwg-status.html">Index by Status</a> for all library issues.</li> - <li><a href="lwg-defects.html">Library Defect Reports List</a></li> - <li><a href="lwg-closed.html">Library Closed Issues List</a></li> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-status.html">Index by Status</a> for all library issues.</li> + <li><a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html">Library Defect Reports List</a></li> + <li><a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html">Library Closed Issues List</a></li> </ul> <p>The purpose of this document is to record the status of issues which have come before the Library Working Group (LWG) of the ANSI @@ -41,10 +40,10 @@ <p>This document contains only library issues which are actively being considered by the Library Working Group. That is, issues which have a - status of <a href="lwg-active.html#New">New</a>, <a href="lwg-active.html#Open">Open</a>, - <a href="lwg-active.html#Ready">Ready</a>, and <a href="lwg-active.html#Review">Review</a>. See - <a href="lwg-defects.html">Library Defect Reports List</a> for issues considered defects and - <a href="lwg-closed.html">Library Closed Issues List</a> for issues considered closed.</p> + status of <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a>, + <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Ready">Ready</a>, and <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a>. See + <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html">Library Defect Reports List</a> for issues considered defects and + <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html">Library Closed Issues List</a> for issues considered closed.</p> <p>The issues in these lists are not necessarily formal ISO Defect Reports (DR's). While some issues will eventually be elevated to @@ -77,8 +76,8 @@ <p>Public information as to how to obtain a copy of the C++ Standard, join the standards committee, submit an issue, or comment on an issue - can be found in the C++ FAQ at <a href="http://www.research.att.com/~austern/csc/faq.html">http://www.research.att.com/~austern/csc/faq.html</a>. - Public discussion of C++ Standard related issues occurs on <a href="news:comp.std.c%2B%2B">news:comp.std.c++</a>. + can be found in the comp.std.c++ FAQ. + Public discussion of C++ Standard related issues occurs on <a href="news://comp.std.c%2b%2b/">news:comp.std.c++</a>. </p> <p>For committee members, files available on the committee's private @@ -88,167 +87,185 @@ directory as the issues list files. </p> <h2>Revision History</h2> <ul> +<li>R27: +Pre-Kona mailing. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#404">404</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#431">431</a>. +</li> +<li>R26: +Post-Oxford mailing: reflects decisions made at the Oxford meeting. +All issues in Ready status were voted into DR status. All issues in +DR status were voted into WP status. +</li> +<li>R25: +Pre-Oxford mailing. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#390">390</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#402">402</a>. +</li> +<li>R24: +Post-Santa Cruz mailing: reflects decisions made at the Santa Cruz +meeting. All Ready issues from R23 with the exception of <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#253">253</a>, which has been given a new proposed resolution, were +moved to DR status. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#383">383</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#389">389</a>. (Issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#387">387</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#389">389</a> were discussed +at the meeting.) Made progress on issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#225">225</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#226">226</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#229">229</a>: <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#225">225</a> and <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#229">229</a> have been moved to Ready status, and the only remaining +concerns with <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#226">226</a> involve wording. +</li> <li>R23: -Pre-Santa Cruz mailing. Added new issues <a href="lwg-active.html#367">367</a>-<a href="lwg-active.html#382">382</a>. +Pre-Santa Cruz mailing. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#367">367</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#382">382</a>. Moved issues in the TC to TC status. </li> <li>R22: -Post-Curaçao mailing. Added new issues <a href="lwg-active.html#362">362</a>-<a href="lwg-active.html#366">366</a>. +Post-Curaçao mailing. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#362">362</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#366">366</a>. </li> <li>R21: -Pre-Curaçao mailing. Added new issues <a href="lwg-closed.html#351">351</a>-<a href="lwg-active.html#361">361</a>. +Pre-Curaçao mailing. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#351">351</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#361">361</a>. </li> <li>R20: Post-Redmond mailing; reflects actions taken in Redmond. Added -new issues <a href="lwg-active.html#336">336</a>-<a href="lwg-active.html#350">350</a>, of which issues -<a href="lwg-active.html#347">347</a>-<a href="lwg-active.html#350">350</a> were added since Redmond, hence +new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#336">336</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#350">350</a>, of which issues +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#347">347</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#350">350</a> were added since Redmond, hence not discussed at the meeting. All Ready issues were moved to DR status, with the exception of issues -<a href="lwg-defects.html#284">284</a>, <a href="lwg-active.html#241">241</a>, and <a href="lwg-closed.html#267">267</a>. +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#284">284</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#241">241</a>, and <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#267">267</a>. Noteworthy issues discussed at Redmond include -<a href="lwg-active.html#120">120</a> <a href="lwg-active.html#202">202</a>, <a href="lwg-active.html#226">226</a>, <a href="lwg-active.html#233">233</a>, -<a href="lwg-defects.html#270">270</a>, <a href="lwg-active.html#253">253</a>, <a href="lwg-active.html#254">254</a>, <a href="lwg-active.html#323">323</a>. +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#120">120</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#202">202</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#226">226</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#233">233</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#270">270</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#253">253</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#254">254</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#323">323</a>. </li> <li>R19: Pre-Redmond mailing. Added new issues -<a href="lwg-active.html#323">323</a>-<a href="lwg-defects.html#335">335</a>. +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#323">323</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#335">335</a>. </li> <li>R18: Post-Copenhagen mailing; reflects actions taken in Copenhagen. -Added new issues <a href="lwg-defects.html#312">312</a>-<a href="lwg-defects.html#317">317</a>, and discussed -new issues <a href="lwg-defects.html#271">271</a>-<a href="lwg-closed.html#314">314</a>. +Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#312">312</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#317">317</a>, and discussed +new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#271">271</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#314">314</a>. Changed status of issues -<a href="lwg-defects.html#103">103</a> <a href="lwg-defects.html#118">118</a> <a href="lwg-defects.html#136">136</a> <a href="lwg-defects.html#153">153</a> -<a href="lwg-defects.html#165">165</a> <a href="lwg-defects.html#171">171</a> <a href="lwg-defects.html#183">183</a> <a href="lwg-defects.html#184">184</a> -<a href="lwg-defects.html#185">185</a> <a href="lwg-defects.html#186">186</a> <a href="lwg-defects.html#214">214</a> <a href="lwg-defects.html#221">221</a> -<a href="lwg-defects.html#234">234</a> <a href="lwg-defects.html#237">237</a> <a href="lwg-defects.html#243">243</a> <a href="lwg-defects.html#248">248</a> -<a href="lwg-defects.html#251">251</a> <a href="lwg-defects.html#252">252</a> <a href="lwg-defects.html#256">256</a> <a href="lwg-defects.html#260">260</a> -<a href="lwg-defects.html#261">261</a> <a href="lwg-defects.html#262">262</a> <a href="lwg-defects.html#263">263</a> <a href="lwg-defects.html#265">265</a> -<a href="lwg-defects.html#268">268</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#103">103</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#118">118</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#136">136</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#153">153</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#165">165</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#171">171</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#183">183</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#184">184</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#185">185</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#186">186</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#214">214</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#221">221</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#234">234</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#237">237</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#243">243</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#248">248</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#251">251</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#252">252</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#256">256</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#260">260</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#261">261</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#262">262</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#263">263</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#265">265</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#268">268</a> to DR. Changed status of issues -<a href="lwg-defects.html#49">49</a> <a href="lwg-defects.html#109">109</a> <a href="lwg-defects.html#117">117</a> <a href="lwg-defects.html#182">182</a> -<a href="lwg-defects.html#228">228</a> <a href="lwg-defects.html#230">230</a> <a href="lwg-defects.html#232">232</a> <a href="lwg-defects.html#235">235</a> -<a href="lwg-defects.html#238">238</a> <a href="lwg-active.html#241">241</a> <a href="lwg-defects.html#242">242</a> <a href="lwg-defects.html#250">250</a> -<a href="lwg-defects.html#259">259</a> <a href="lwg-defects.html#264">264</a> <a href="lwg-defects.html#266">266</a> <a href="lwg-closed.html#267">267</a> -<a href="lwg-defects.html#271">271</a> <a href="lwg-defects.html#272">272</a> <a href="lwg-defects.html#273">273</a> <a href="lwg-defects.html#275">275</a> -<a href="lwg-defects.html#281">281</a> <a href="lwg-defects.html#284">284</a> <a href="lwg-defects.html#285">285</a> <a href="lwg-defects.html#286">286</a> -<a href="lwg-defects.html#288">288</a> <a href="lwg-defects.html#292">292</a> <a href="lwg-defects.html#295">295</a> <a href="lwg-defects.html#297">297</a> -<a href="lwg-defects.html#298">298</a> <a href="lwg-defects.html#301">301</a> <a href="lwg-defects.html#303">303</a> <a href="lwg-defects.html#306">306</a> -<a href="lwg-defects.html#307">307</a> <a href="lwg-defects.html#308">308</a> <a href="lwg-defects.html#312">312</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#49">49</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#109">109</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#117">117</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#182">182</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#228">228</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#230">230</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#232">232</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#235">235</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#238">238</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#241">241</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#242">242</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#250">250</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#259">259</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#264">264</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#266">266</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#267">267</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#271">271</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#272">272</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#273">273</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#275">275</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#281">281</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#284">284</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#285">285</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#286">286</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#288">288</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#292">292</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#295">295</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#297">297</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#298">298</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#301">301</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#303">303</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#306">306</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#307">307</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#308">308</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#312">312</a> to Ready. Closed issues -<a href="lwg-closed.html#111">111</a> <a href="lwg-closed.html#277">277</a> <a href="lwg-closed.html#279">279</a> <a href="lwg-closed.html#287">287</a> -<a href="lwg-closed.html#289">289</a> <a href="lwg-closed.html#293">293</a> <a href="lwg-closed.html#302">302</a> <a href="lwg-closed.html#313">313</a> -<a href="lwg-closed.html#314">314</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#111">111</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#277">277</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#279">279</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#287">287</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#289">289</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#293">293</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#302">302</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#313">313</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#314">314</a> as NAD. </li> <li>R17: Pre-Copenhagen mailing. Converted issues list to XML. Added proposed -resolutions for issues <a href="lwg-defects.html#49">49</a>, <a href="lwg-defects.html#76">76</a>, <a href="lwg-active.html#91">91</a>, <a href="lwg-defects.html#235">235</a>, <a href="lwg-defects.html#250">250</a>, <a href="lwg-closed.html#267">267</a>. -Added new issues <a href="lwg-active.html#278">278</a>-<a href="lwg-defects.html#311">311</a>. +resolutions for issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#49">49</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#76">76</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#91">91</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#235">235</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#250">250</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#267">267</a>. +Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#278">278</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#311">311</a>. </li> <li>R16: post-Toronto mailing; reflects actions taken in Toronto. Added new -issues <a href="lwg-defects.html#265">265</a>-<a href="lwg-closed.html#277">277</a>. Changed status of issues -<a href="lwg-defects.html#3">3</a>, <a href="lwg-defects.html#8">8</a>, <a href="lwg-defects.html#9">9</a>, <a href="lwg-defects.html#19">19</a>, -<a href="lwg-defects.html#26">26</a>, <a href="lwg-defects.html#31">31</a>, <a href="lwg-defects.html#61">61</a>, -<a href="lwg-defects.html#63">63</a>, <a href="lwg-defects.html#86">86</a>, <a href="lwg-defects.html#108">108</a>, -<a href="lwg-defects.html#112">112</a>, <a href="lwg-defects.html#114">114</a>, <a href="lwg-defects.html#115">115</a>, -<a href="lwg-defects.html#122">122</a>, <a href="lwg-defects.html#127">127</a>, <a href="lwg-defects.html#129">129</a>, -<a href="lwg-defects.html#134">134</a>, <a href="lwg-defects.html#137">137</a>, <a href="lwg-defects.html#142">142</a>, -<a href="lwg-defects.html#144">144</a>, <a href="lwg-defects.html#146">146</a>, <a href="lwg-defects.html#147">147</a>, -<a href="lwg-defects.html#159">159</a>, <a href="lwg-defects.html#164">164</a>, <a href="lwg-defects.html#170">170</a>, -<a href="lwg-defects.html#181">181</a>, <a href="lwg-defects.html#199">199</a>, <a href="lwg-defects.html#208">208</a>, -<a href="lwg-defects.html#209">209</a>, <a href="lwg-defects.html#210">210</a>, <a href="lwg-defects.html#211">211</a>, -<a href="lwg-defects.html#212">212</a>, <a href="lwg-defects.html#217">217</a>, <a href="lwg-defects.html#220">220</a>, -<a href="lwg-defects.html#222">222</a>, <a href="lwg-defects.html#223">223</a>, <a href="lwg-defects.html#224">224</a>, -<a href="lwg-defects.html#227">227</a> to "DR". Reopened issue <a href="lwg-active.html#23">23</a>. Reopened -issue <a href="lwg-active.html#187">187</a>. Changed issues <a href="lwg-closed.html#2">2</a> and -<a href="lwg-closed.html#4">4</a> to NAD. Fixed a typo in issue <a href="lwg-defects.html#17">17</a>. Fixed -issue <a href="lwg-defects.html#70">70</a>: signature should be changed both places it -appears. Fixed issue <a href="lwg-defects.html#160">160</a>: previous version didn't fix +issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#265">265</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#277">277</a>. Changed status of issues +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#3">3</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#8">8</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#9">9</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#19">19</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#26">26</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#31">31</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#61">61</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#63">63</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#86">86</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#108">108</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#112">112</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#114">114</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#115">115</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#122">122</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#127">127</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#129">129</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#134">134</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#137">137</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#142">142</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#144">144</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#146">146</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#147">147</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#159">159</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#164">164</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#170">170</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#181">181</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#199">199</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#208">208</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#209">209</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#210">210</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#211">211</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#212">212</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#217">217</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#220">220</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#222">222</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#223">223</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#224">224</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#227">227</a> to "DR". Reopened issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#23">23</a>. Reopened +issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#187">187</a>. Changed issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#2">2</a> and +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#4">4</a> to NAD. Fixed a typo in issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#17">17</a>. Fixed +issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#70">70</a>: signature should be changed both places it +appears. Fixed issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#160">160</a>: previous version didn't fix the bug in enough places. </li> <li>R15: pre-Toronto mailing. Added issues -<a href="lwg-active.html#233">233</a>-<a href="lwg-defects.html#264">264</a>. Some small HTML formatting +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#233">233</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#264">264</a>. Some small HTML formatting changes so that we pass Weblint tests. </li> <li>R14: post-Tokyo II mailing; reflects committee actions taken in -Tokyo. Added issues <a href="lwg-defects.html#228">228</a> to <a href="lwg-defects.html#232">232</a>. (00-0019R1/N1242) +Tokyo. Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#228">228</a> to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#232">232</a>. (00-0019R1/N1242) </li> <li>R13: -pre-Tokyo II updated: Added issues <a href="lwg-defects.html#212">212</a> to <a href="lwg-defects.html#227">227</a>. +pre-Tokyo II updated: Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#212">212</a> to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#227">227</a>. </li> <li>R12: -pre-Tokyo II mailing: Added issues <a href="lwg-defects.html#199">199</a> to -<a href="lwg-defects.html#211">211</a>. Added "and paragraph 5" to the proposed resolution -of issue <a href="lwg-defects.html#29">29</a>. Add further rationale to issue -<a href="lwg-closed.html#178">178</a>. +pre-Tokyo II mailing: Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#199">199</a> to +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#211">211</a>. Added "and paragraph 5" to the proposed resolution +of issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#29">29</a>. Add further rationale to issue +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#178">178</a>. </li> <li>R11: post-Kona mailing: Updated to reflect LWG and full committee actions in Kona (99-0048/N1224). Note changed resolution of issues -<a href="lwg-closed.html#4">4</a> and <a href="lwg-defects.html#38">38</a>. Added issues <a href="lwg-closed.html#196">196</a> -to <a href="lwg-defects.html#198">198</a>. Closed issues list split into "defects" and -"closed" documents. Changed the proposed resolution of issue -<a href="lwg-closed.html#4">4</a> to NAD, and changed the wording of proposed resolution -of issue <a href="lwg-defects.html#38">38</a>. +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#4">4</a> and <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#38">38</a>. Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#196">196</a> +to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#198">198</a>. Closed issues list split into "defects" and +"closed" documents. Changed the proposed resolution of issue +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#4">4</a> to NAD, and changed the wording of proposed resolution +of issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#38">38</a>. </li> <li>R10: -pre-Kona updated. Added proposed resolutions <a href="lwg-defects.html#83">83</a>, -<a href="lwg-defects.html#86">86</a>, <a href="lwg-active.html#91">91</a>, <a href="lwg-active.html#92">92</a>, -<a href="lwg-defects.html#109">109</a>. Added issues <a href="lwg-closed.html#190">190</a> to -<a href="lwg-defects.html#195">195</a>. (99-0033/D1209, 14 Oct 99) +pre-Kona updated. Added proposed resolutions <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#83">83</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#86">86</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#91">91</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#92">92</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#109">109</a>. Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#190">190</a> to +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#195">195</a>. (99-0033/D1209, 14 Oct 99) </li> <li>R9: -pre-Kona mailing. Added issues <a href="lwg-closed.html#140">140</a> to -<a href="lwg-defects.html#189">189</a>. Issues list split into separate "active" and -"closed" documents. (99-0030/N1206, 25 Aug 99) +pre-Kona mailing. Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#140">140</a> to +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#189">189</a>. Issues list split into separate "active" and +"closed" documents. (99-0030/N1206, 25 Aug 99) </li> <li>R8: post-Dublin mailing. Updated to reflect LWG and full committee actions in Dublin. (99-0016/N1193, 21 Apr 99) </li> <li>R7: -pre-Dublin updated: Added issues <a href="lwg-closed.html#130">130</a>, <a href="lwg-closed.html#131">131</a>, -<a href="lwg-defects.html#132">132</a>, <a href="lwg-defects.html#133">133</a>, <a href="lwg-defects.html#134">134</a>, -<a href="lwg-closed.html#135">135</a>, <a href="lwg-defects.html#136">136</a>, <a href="lwg-defects.html#137">137</a>, -<a href="lwg-closed.html#138">138</a>, <a href="lwg-defects.html#139">139</a> (31 Mar 99) +pre-Dublin updated: Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#130">130</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#131">131</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#132">132</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#133">133</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#134">134</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#135">135</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#136">136</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#137">137</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#138">138</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#139">139</a> (31 Mar 99) </li> <li>R6: -pre-Dublin mailing. Added issues <a href="lwg-defects.html#127">127</a>, <a href="lwg-closed.html#128">128</a>, -and <a href="lwg-defects.html#129">129</a>. (99-0007/N1194, 22 Feb 99) +pre-Dublin mailing. Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#127">127</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#128">128</a>, +and <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#129">129</a>. (99-0007/N1194, 22 Feb 99) </li> <li>R5: -update issues <a href="lwg-defects.html#103">103</a>, <a href="lwg-defects.html#112">112</a>; added issues -<a href="lwg-defects.html#114">114</a> to <a href="lwg-defects.html#126">126</a>. Format revisions to prepare +update issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#103">103</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#112">112</a>; added issues +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#114">114</a> to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#126">126</a>. Format revisions to prepare for making list public. (30 Dec 98) </li> <li>R4: -post-Santa Cruz II updated: Issues <a href="lwg-defects.html#110">110</a>, -<a href="lwg-closed.html#111">111</a>, <a href="lwg-defects.html#112">112</a>, <a href="lwg-closed.html#113">113</a> added, several +post-Santa Cruz II updated: Issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#110">110</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#111">111</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#112">112</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#113">113</a> added, several issues corrected. (22 Oct 98) </li> <li>R3: -post-Santa Cruz II: Issues <a href="lwg-closed.html#94">94</a> to <a href="lwg-defects.html#109">109</a> +post-Santa Cruz II: Issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#94">94</a> to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#109">109</a> added, many issues updated to reflect LWG consensus (12 Oct 98) </li> <li>R2: -pre-Santa Cruz II: Issues <a href="lwg-closed.html#73">73</a> to <a href="lwg-closed.html#93">93</a> added, -issue <a href="lwg-defects.html#17">17</a> updated. (29 Sep 98) +pre-Santa Cruz II: Issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#73">73</a> to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#93">93</a> added, +issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#17">17</a> updated. (29 Sep 98) </li> <li>R1: -Correction to issue <a href="lwg-defects.html#55">55</a> resolution, <a href="lwg-defects.html#60">60</a> code -format, <a href="lwg-defects.html#64">64</a> title. (17 Sep 98) +Correction to issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#55">55</a> resolution, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#60">60</a> code +format, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#64">64</a> title. (17 Sep 98) </li> </ul> <h2> @@ -318,6 +335,12 @@ format, <a href="lwg-defects.html#64">64</a> title. (17 Sep 98) complete and no further action is possible under ISO rules.</p> <p> +<b><a name="WP">WP</a></b> - (Working Paper) - The proposed + resolution has not been accepted as a Technical Corrigendum, but + the full WG21 committee has voted to apply the Defect Report's Proposed + Resolution to the working paper.</p> + + <p> <b><a name="RR">RR</a></b> - (Record of Response) - The full WG21 committee has determined that this issue is not a defect in the Standard. Action on this issue is thus complete and no further @@ -328,17 +351,17 @@ format, <a href="lwg-defects.html#64">64</a> title. (17 Sep 98) status, the LWG believes that this issue should be revisited at the next revision of the standard. It is usually paired with NAD.</p> - <p>Issues are always given the status of <a href="lwg-active.html#New">New</a> when + <p>Issues are always given the status of <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> when they first appear on the issues list. They may progress to - <a href="lwg-active.html#Open">Open</a> or <a href="lwg-active.html#Review">Review</a> while the LWG + <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> or <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> while the LWG is actively working on them. When the LWG has reached consensus on the disposition of an issue, the status will then change to - <a href="lwg-active.html#Dup">Dup</a>, <a href="lwg-active.html#NAD">NAD</a>, or <a href="lwg-active.html#Ready">Ready</a> as appropriate. Once the full J16 committee votes to + <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Dup">Dup</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#NAD">NAD</a>, or <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Ready">Ready</a> as appropriate. Once the full J16 committee votes to forward Ready issues to the Project Editor, they are given the - status of Defect Report ( <a href="lwg-active.html#DR">DR</a>). These in turn may - become the basis for Technical Corrigenda (<a href="lwg-active.html#TC">TC</a>), + status of Defect Report ( <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#DR">DR</a>). These in turn may + become the basis for Technical Corrigenda (<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a>), or are closed without action other than a Record of Response - (<a href="lwg-active.html#RR">RR</a> ). The intent of this LWG process is that + (<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#RR">RR</a> ). The intent of this LWG process is that only issues which are truly defects in the Standard move to the formal ISO DR status. </p> @@ -346,15 +369,16 @@ format, <a href="lwg-defects.html#64">64</a> title. (17 Sep 98) <h2>Active Issues</h2> <hr> <a name="23"><h3>23. Num_get overflow result</h3></a><p> -<b>Section:</b> 22.2.2.1.2 <a href="lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> -<p>The current description of numeric input does not account for the possibility of -overflow. This is an implicit result of changing the description to rely on the definition -of scanf() (which fails to report overflow), and conflicts with the documented behavior of +<b>Section:</b> 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<p>The current description of numeric input does not account for the +possibility of overflow. This is an implicit result of changing the +description to rely on the definition of scanf() (which fails to +report overflow), and conflicts with the documented behavior of traditional and current implementations. </p> -<p>Users expect, when reading a character sequence that results in a value unrepresentable -in the specified type, to have an error reported. The standard as written does not permit -this. </p> +<p>Users expect, when reading a character sequence that results in a +value unrepresentable in the specified type, to have an error +reported. The standard as written does not permit this. </p> <p><b>Further comments from Dietmar:</b></p> @@ -370,7 +394,7 @@ and hard to trace, so I will describe it briefly: <ul> <li> - According to 22.2.2.1.2 <a href="lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> + According to 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> paragraph 11 <tt>failbit</tt> is set if <tt>scanf()</tt> would return an input error; otherwise a value is converted to the rules of <tt>scanf</tt>. @@ -412,7 +436,7 @@ and hard to trace, so I will describe it briefly: <p>The basic problem is that we've defined our behavior, including our error-reporting behavior, in terms of C90. However, C90's method of reporting overflow in scanf is not technically an -"input error". The <tt>strto_*</tt> functions are more precise.</p> +"input error". The <tt>strto_*</tt> functions are more precise.</p> <p>There was general consensus that <tt>failbit</tt> should be set upon overflow. We considered three options based on this:</p> @@ -428,12 +452,69 @@ upon overflow. We considered three options based on this:</p> <p>Straw poll: (1) 5; (2) 0; (3) 8.</p> -<p>PJP will provide wording.</p> +<p><b>Further discussion from Santa Cruz:</b></p> + +<p>There was some discussion of what the intent of our error + reporting mechanism was. There was general agreement on the + following principles:</p> +<ul> +<li>We want to convert strings to numbers in the same way as the + C <tt>strto*</tt> functions do. The same things that those + functions would consider errors, we consider errors.</li> +<li>Overflow is an error. Floating-point underflow is not an error. + 1.e-9999999, for example, should be treated as 0. (A negative + number whose magnitude is too large is still overflow, and is just + the same error as a positive number whose magnitude is too large. + Finally, <tt>strtoul</tt> already specifies what happens if you + try to convert a sequence beginning with a minus sign into an + unsigned value.)</li> +<li>Our mechanism for reporting errors is to set failbit. Our + mechanism is not errno. Nothing in the standard should + require or imply that streams or facets ever set errno. + (Even if some implementations might have that effect.) </li> +</ul> + +<p>The crux of the disagreement was that some people, but not all, + believed that the design was also based on a fourth principle: + whenever converstion fails and failbit is set, nothing is to be + extracted and the value of the variable being extracted into is + guaranteed to be unchanged.</p> + +<p>Some people believe that upon overflow, an implementation should + "extract" a special value that allows the user to tell that it was + overflow instead of some other kind of error. Straw poll: 1 person + believed the standard should require that, 2 thought it should + forbid it, and 6 thought the standard should allow but not require + it.</p> <p><b>Proposed resolution:</b></p> +<p>typo: 22.2.2.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a>, para 2, bullet 3. Strike "in." from +the end.</p> + +<p>Change 22.2.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.nm.put"> [lib.locale.nm.put]</a>, para 11, bullet 2 from:</p> +<blockquote> +The sequence of chars accumulated in stage 2 would have +caused scanf to report an input failure. ios_base::failbit is +assigned to err. +</blockquote> + +<p>to:</p> +<blockquote> +The sequence of chars accumulated in stage 2 would have +caused scanf to report an input failure or to store a value +outside the range representable by val. ios_base::failbit is +assigned to err. +</blockquote> + +<p><i>[PJP provided wording. this treats overflow or underflow the same +as an ill-formed field. It's not exactly the consensus from Santa +Cruz, but he thinks it's the simplest and most robust rule and that it +corresponds to widespread common practice.]</i></p> + + <hr> <a name="44"><h3>44. Iostreams use operator== on int_type values</h3></a><p> -<b>Section:</b> 27 <a href="lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 27 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>Many of the specifications for iostreams specify that character values or their int_type equivalents are compared using operators == or !=, though in other places traits::eq() or traits::eq_int_type is @@ -441,78 +522,266 @@ specified to be used throughout. This is an inconsistency; we should change uses of == and != to use the traits members instead. </p> <p><b>Proposed resolution:</b></p> -<p><i>[Kona: Nathan to supply proposed wording]</i></p> +<p><i>[Pre-Kona: Dietmar supplied wording]</i></p> -<p><i>[ -Tokyo: the LWG reaffirmed that this is a defect, and requires careful -review of clause 27 as the changes are context sensitive. -]</i></p> +<p>List of changes to clause 27:</p> +<ol> +<li> + In lib.basic.ios.members paragraph 13 (postcondition clause for + 'fill(cT)') change + +<blockquote> + fillch == fill() +</blockquote> + + to + +<blockquote> + traits::eq(fillch, fill()) +</blockquote> + + +</li> +<li> + In lib.istream.unformatted paragraph 7 (effects clause for + 'get(cT,streamsize,cT)'), third bullet, change -<hr> -<a name="91"><h3>91. Description of operator>> and getline() for string<> might cause endless loop</h3></a><p> -<b>Section:</b> 21.3.7.9 <a href="lib-strings.html#lib.string.io"> [lib.string.io]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> -<p>Operator >> and getline() for strings read until eof() -in the input stream is true. However, this might never happen, if the -stream can't read anymore without reaching EOF. So shouldn't it be -changed into that it reads until !good() ? </p> -<p><b>Proposed resolution:</b></p> -<p>In 21.3.7.9 <a href="lib-strings.html#lib.string.io"> [lib.string.io]</a>, paragraph 1, replace:</p> <blockquote> -Effects: Begins by constructing a sentry object k as if k were -constructed by typename basic_istream<charT,traits>::sentry k( is). If -bool( k) is true, it calls str.erase() and then extracts characters -from is and appends them to str as if by calling str.append(1, c). If -is.width() is greater than zero, the maximum number n of characters -appended is is.width(); otherwise n is str.max_size(). Characters are -extracted and appended until any of the following occurs: + c == delim for the next available input character c </blockquote> -<p>with:</p> + + to + +<blockquote> + traits::eq(c, delim) for the next available input character c + </blockquote> + +</li> +<li> + In lib.istream.unformatted paragraph 12 (effects clause for + 'get(basic_streambuf<cT,Tr>&,cT)'), third bullet, change + <blockquote> -Effects: Behaves as a formatted input function (27.6.1.2.1 <a href="lib-iostreams.html#lib.istream.formatted.reqmts"> [lib.istream.formatted.reqmts]</a>). After constructing a sentry object, if the -sentry converts to true, calls str.erase() and then extracts -characters from is and appends them to str as if by calling -str.append(1,c). If is.width() is greater than zero, the maximum -number n of characters appended is is.width(); otherwise n is -str.max_size(). Characters are extracted and appended until any of the -following occurs: + c == delim for the next available input character c </blockquote> -<p>In 21.3.7.9 <a href="lib-strings.html#lib.string.io"> [lib.string.io]</a>, paragraph 6, replace</p> + to + <blockquote> -Effects: Begins by constructing a sentry object k as if by typename -basic_istream<charT,traits>::sentry k( is, true). If bool( k) is true, -it calls str.erase() and then extracts characters from is and appends -them to str as if by calling str.append(1, c) until any of the -following occurs: + traits::eq(c, delim) for the next available input character c </blockquote> -<p>with:</p> + +</li> +<li> + In lib.istream.unformatted paragraph 17 (effects clause for + 'getline(cT,streamsize,cT)'), second bullet, change + <blockquote> -Effects: Behaves as an unformatted input function (27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>), except that it does not affect the value returned -by subsequent calls to basic_istream<>::gcount(). After -constructing a sentry object, if the sentry converts to true, calls -str.erase() and then extracts characters from is and appends them to -str as if by calling str.append(1,c) until any of the following -occurs: + c == delim for the next available input character c </blockquote> -<p><i>[Redmond: Made changes in proposed resolution. <tt>operator>></tt> -should be a formatted input function, not an unformatted input function. -<tt>getline</tt> should not be required to set <tt>gcount</tt>, since -there is no mechanism for <tt>gcount</tt> to be set except by one of -<tt>basic_istream</tt>'s member functions.]</i></p> + to -<p><i>[Curaçao: Nico agrees with proposed resolution.]</i></p> +<blockquote> + traits::eq(c, delim) for the next available input character c + </blockquote> + +</li> +<li> + In lib.istream.unformatted paragraph 24 (effects clause for + 'ignore(int,int_type)'), second bullet, change + +<blockquote> + c == delim for the next available input character c +</blockquote> + + to + +<blockquote> + traits::eq_int_type(c, delim) for the next available input + character c +</blockquote> + +</li> +<li> + In lib.istream.unformatted paragraph 25 (notes clause for + 'ignore(int,int_type)'), second bullet, change + +<blockquote> + The last condition will never occur if delim == traits::eof() +</blockquote> + + to + +<blockquote> + The last condition will never occur if + traits::eq_int_type(delim, traits::eof()). +</blockquote> + +</li> +<li> + In lib.istream.sentry paragraph 6 (example implementation for the + sentry constructor) change + +<blockquote> + while ((c = is.rdbuf()->snextc()) != traits::eof()) { +</blockquote> + + to + +<blockquote> + while (!traits::eq_int_type(c = is.rdbuf()->snextc(), traits::eof())) { +</blockquote> + +</li> +</ol> + +<p>List of changes to Chapter 21:</p> + +<ol> +<li> + In lib.string::find paragraph 1 (effects clause for find()), + second bullet, change + +<blockquote> + at(xpos+I) == str.at(I) for all elements ... +</blockquote> + + to + +<blockquote> + traits::eq(at(xpos+I), str.at(I)) for all elements ... +</blockquote> + +</li> +<li> + In lib.string::rfind paragraph 1 (effects clause for rfind()), + second bullet, change + +<blockquote> + at(xpos+I) == str.at(I) for all elements ... +</blockquote> + + to + +<blockquote> + traits::eq(at(xpos+I), str.at(I)) for all elements ... +</blockquote> + +</li> +<li> + In lib.string::find.first.of paragraph 1 (effects clause for + find_first_of()), second bullet, change + +<blockquote> + at(xpos+I) == str.at(I) for all elements ... +</blockquote> + + to + +<blockquote> + traits::eq(at(xpos+I), str.at(I)) for all elements ... +</blockquote> + +</li> +<li> + In lib.string::find.last.of paragraph 1 (effects clause for + find_last_of()), second bullet, change + +<blockquote> + at(xpos+I) == str.at(I) for all elements ... +</blockquote> + + to + +<blockquote> + traits::eq(at(xpos+I), str.at(I)) for all elements ... +</blockquote> + +</li> +<li> + In lib.string::find.first.not.of paragraph 1 (effects clause for + find_first_not_of()), second bullet, change + +<blockquote> + at(xpos+I) == str.at(I) for all elements ... +</blockquote> + + to + +<blockquote> + traits::eq(at(xpos+I), str.at(I)) for all elements ... +</blockquote> +</li> + +<li> + In lib.string::find.last.not.of paragraph 1 (effects clause for + find_last_not_of()), second bullet, change + +<blockquote> + at(xpos+I) == str.at(I) for all elements ... +</blockquote> + + to + +<blockquote> + traits::eq(at(xpos+I), str.at(I)) for all elements ... +</blockquote> +</li> + +<li> + In lib.string.ios paragraph 5 (effects clause for getline()), + second bullet, change + +<blockquote> + c == delim for the next available input character c +</blockquote> + + to + +<blockquote> + traits::eq(c, delim) for the next available input character c +</blockquote> +</li> + +</ol> + +<p>Notes:</p> +<ul> +<li> + Fixing this issue highlights another sloppyness in + lib.istream.unformatted paragraph 24: this clause mentions a "character" + which is then compared to an 'int_type' (see item 5. in the list + below). It is not clear whether this requires explicit words and + if so what these words are supposed to be. A similar issue exists, + BTW, for operator*() of istreambuf_iterator which returns the result + of sgetc() as a character type (see lib.istreambuf.iterator::op* + paragraph 1), and for operator++() of istreambuf_iterator which + passes the result of sbumpc() to a constructor taking a char_type + (see lib.istreambuf.iterator::operator++ paragraph 3). Similarily, the + assignment operator ostreambuf_iterator passes a char_type to a function + taking an int_type (see lib.ostreambuf.iter.ops paragraph 1). +</li> +<li> + It is inconsistent to use comparisons using the traits functions in + Chapter 27 while not using them in Chapter 21, especially as some + of the inconsistent uses actually involve streams (eg. getline() on + streams). To avoid leaving this issue open still longer due to this + inconsistency (it is open since 1998), a list of changes to Chapter + 21 is below. +</li> +<li> + In Chapter 24 there are several places with statements like "the end + of stream is reached (streambuf_type::sgetc() returns traits::eof())" + (lib.istreambuf.iterator paragraph 1, lib.ostreambuf.iter.ops + paragraph 5). It is unclear whether these should be clarified to use + traits::eq_int_type() for detecting traits::eof(). +</li> +</ul> -<p><b>Rationale:</b></p> -<p>The real issue here is whether or not these string input functions -get their characters from a streambuf, rather than by calling an -istream's member functions, a streambuf signals failure either by -returning eof or by throwing an exception; there are no other -possibilities. The proposed resolution makes it clear that these two -functions do get characters from a streambuf.</p> <hr> <a name="92"><h3>92. Incomplete Algorithm Requirements</h3></a><p> -<b>Section:</b> 25 <a href="lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> +<b>Section:</b> 25 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> <p>The standard does not state, how often a function object is copied, called, or the order of calls inside an algorithm. This may lead to surprising/buggy behavior. Consider the following example: </p> @@ -560,37 +829,16 @@ advantage of function objects being able to have a state. Without any cost it could be avoided (just implement it directly instead of calling find_if()). </p> <p><b>Proposed resolution:</b></p> -<p> In [lib.function.objects] 20.3 Function objects add as new -paragraph 6 (or insert after paragraph 1): </p> - -<p>Option 1: </p> -<blockquote> -Predicates are functions or function objects that fulfill the -following requirements:<br> - They return a Boolean value (bool -or a value convertible to bool)<br> - It doesn't matter for the -behavior of a predicate how often it is copied or assigned and how -often it is called. -</blockquote> -<p>Option 2: </p> +<p>Add a new paragraph following 25 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a> paragraph 8:</p> <blockquote> -- if it's a function:<br> - All calls with the same -argument values yield the same result.<br> - if it's a function -object:<br> - In any sequence of calls to operator () without -calling any non-constant member function, all calls with the same -argument values yield the same result. <br> - After an assignment -or copy both objects return the same result for the same values. +[Note: Unless otherwise specified, algorithms that take function +objects as arguments are permitted to copy those function objects +freely. Programmers for whom object identity is important should +consider using a wrapper class that points to a noncopied +implementation object, or some equivalent solution.] </blockquote> -<p><i>[Santa Cruz: The LWG believes that there may be more to this than -meets the eye. It applies to all function objects, particularly -predicates. Two questions: (1) must a function object be -copyable? (2) how many times is a function object called? These -are in effect questions about state. Function objects appear to -require special copy semantics to make state work, and may fail if -calling alters state and calling occurs an unexpected number of -times.]</i></p> - <p><i>[Dublin: Pete Becker felt that this may not be a defect, but rather something that programmers need to be educated about. There was discussion of adding wording to the effect that the number @@ -598,38 +846,35 @@ and order of calls to function objects, including predicates, not affect the behavior of the function object.]</i></p> <p><i>[Pre-Kona: Nico comments: It seems the problem is that we don't -have a clear statement of "predicate" in the -standard. People including me seemed to think "a function +have a clear statement of "predicate" in the +standard. People including me seemed to think "a function returning a Boolean value and being able to be called by an STL algorithm or be used as sorting criterion or ... is a -predicate". But a predicate has more requirements: It should +predicate". But a predicate has more requirements: It should never change its behavior due to a call or being copied. IMHO we have to state this in the standard. If you like, see section 8.1.4 of my library book for a detailed discussion.]</i></p> -<p><i>[Kona: Nico will provide wording to the effect that "unless +<p><i>[Kona: Nico will provide wording to the effect that "unless otherwise specified, the number of copies of and calls to function -objects by algorithms is unspecified". Consider placing in -25 <a href="lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a> after paragraph 9.]</i></p> - -<p><i>[Pre-Tokyo: Angelika Langer comments: if the resolution is -that algorithms are free to copy and pass around any function objects, -then it is a valid question whether they are also allowed to change -the type information from reference type to value type.]</i></p> +objects by algorithms is unspecified". Consider placing in +25 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a> after paragraph 9.]</i></p> -<p><i>[Tokyo: Nico will discuss this further with Matt as there are -multiple problems beyond the underlying problem of no definition of -"Predicate".]</i></p> +<p><i>[Santa Cruz: The standard doesn't currently guarantee that + functions object won't be copied, and what isn't forbidden is + allowed. It is believed (especially since implementations that were + written in concert with the standard do make copies of function + objects) that this was intentional. Thus, no normative change is + needed. What we should put in is a non-normative note suggesting to + programmers that if they want to guarantee the lack of copying they + should use something like the <tt>ref</tt> wrapper.]</i></p> -<p><i>[Post-Tokyo: Nico provided the above proposed -resolutions.]</i></p> +<p><i>[Oxford: Matt provided wording.]</i></p> -<p><i>[Curaçao: Nico will provide wording to make options clearer: are -the exclusive, or is one a superset of the other?]</i></p> <hr> <a name="96"><h3>96. Vector<bool> is not a container</h3></a><p> -<b>Section:</b> 23.2.5 <a href="lib-containers.html#lib.vector.bool"> [lib.vector.bool]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> AFNOR <b>Date:</b> 7 Oct 1998</p> +<b>Section:</b> 23.2.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.bool"> [lib.vector.bool]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> AFNOR <b>Date:</b> 7 Oct 1998</p> <p> <tt>vector<bool></tt> is not a container as its reference and pointer types are not references and pointers. </p> @@ -659,7 +904,7 @@ vector<bool> would meet.<br> * Rename vector<bool>.<br> <br> No alternative had strong, wide-spread, support and every alternative -had at least one "over my dead body" response.<br> +had at least one "over my dead body" response.<br> <br> There was also mention of a transition scheme something like (1) add vector_bool and deprecate vector<bool> in the next standard. (2) @@ -691,34 +936,44 @@ solution.]</i></p> <hr> <a name="98"><h3>98. Input iterator requirements are badly written</h3></a><p> -<b>Section:</b> 24.1.1 <a href="lib-iterators.html#lib.input.iterators"> [lib.input.iterators]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> AFNOR <b>Date:</b> 7 Oct 1998</p> -<p>Table 72 in 24.1.1 <a href="lib-iterators.html#lib.input.iterators"> [lib.input.iterators]</a> specifies semantics for +<b>Section:</b> 24.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.input.iterators"> [lib.input.iterators]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> AFNOR <b>Date:</b> 7 Oct 1998</p> +<p>Table 72 in 24.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.input.iterators"> [lib.input.iterators]</a> specifies semantics for <tt>*r++</tt> of:</p> <p> <tt>{ T tmp = *r; ++r; return tmp; }</tt> </p> <p>There are two problems with this. First, the return type is -specified to be "T", as opposed to something like "convertible to T". +specified to be "T", as opposed to something like "convertible to T". This is too specific: we want to allow *r++ to return an lvalue.</p> <p>Second, writing the semantics in terms of code misleadingly suggests that the effects *r++ should precisely replicate the behavior -of this code, including side effects. (What if it's a user-defined -type whose copy constructor has observable behavior?) We should -replace the code with words, or else put some blanket statement in -clause 17 saying that code samples aren't intended to specify exactly -how many times a copy constructor is called, even if the copy -constructor has observable behavior. (See issue <a href="lwg-active.html#334">334</a> -for a similar problem.)</p> - -<p><i>[Issue still isn't clear. Matt will try to explain it more -clearly at the next meeting.]</i></p> +of this code, including side effects. (Does this mean that *r++ +should invoke the copy constructor exactly as many times as the sample +code above would?) See issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#334">334</a> for a similar +problem.</p> <p><b>Proposed resolution:</b></p> +In Table 72 in 24.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.input.iterators"> [lib.input.iterators]</a>, change the return type +for <tt>*r++</tt> from <tt>T</tt> to "convertible to T". +<p><b>Rationale:</b></p> +<p>This issue has two parts: the return type, and the number of times + the copy constructor is invoked.</p> + +<p>The LWG believes the the first part is a real issue. It's + inappropriate for the return type to be specified so much more + precisely for *r++ than it is for *r. In particular, if r is of + (say) type <tt>int*</tt>, then *r++ isn't <tt>int</tt>, + but <tt>int&</tt>.</p> + +<p>The LWG does not believe that the number of times the copy + constructor is invoked is a real issue. This can vary in any case, + because of language rules on copy constructor elision. That's too + much to read into these semantics clauses.</p> <hr> <a name="120"><h3>120. Can an implementor add specializations?</h3></a><p> -<b>Section:</b> 17.4.3.1 <a href="lib-intro.html#lib.reserved.names"> [lib.reserved.names]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> +<b>Section:</b> 17.4.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.reserved.names"> [lib.reserved.names]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> <p>The original issue asked whether a library implementor could specialize standard library templates for built-in types. (This was @@ -741,7 +996,7 @@ for the same type in two different translation units (ODR violation), and the core working group doesn't believe it is practical to relax that restriction.</p> -<p>The issue, then, is: are users allowed to implicitly instantiate +<p>The issue, then, is: are users allowed to explicitly instantiate standard library templates for non-user defined types? The status quo answer is 'yes'. Changing it to 'no' would give library implementors more freedom.</p> @@ -759,26 +1014,24 @@ prevent users from performing their own explicit instantiations: put each explicit instantiation in its own object file. (Different solutions might be necessary for Unix DSOs or MS-Windows DLLs.) On some platforms, library implementors might not need to do anything -special: the "undefined behavior" that results from having two +special: the "undefined behavior" that results from having two different explicit instantiations might be harmless.</p> <p><b>Proposed resolution:</b></p> -<p>Option 1.</p> -<blockquote> - <p>Append to 17.4.3.1 <a href="lib-intro.html#lib.reserved.names"> [lib.reserved.names]</a> paragraph 1: </p> + <p>Append to 17.4.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.reserved.names"> [lib.reserved.names]</a> paragraph 1: </p> <blockquote> A program may explicitly instantiate any templates in the standard library only if the declaration depends on a user-defined name of external linkage and the instantiation meets the standard library requirements for the original template. </blockquote> -</blockquote> -<p>Option 2.</p> +<p><b>Rationale:</b></p> +<p>The LWG considered another possible resolution:</p> <blockquote> <p>In light of the resolution to core issue 259, no normative changes in the library clauses are necessary. Add the following non-normative - note to the end of 17.4.3.1 <a href="lib-intro.html#lib.reserved.names"> [lib.reserved.names]</a> paragraph 1:</p> + note to the end of 17.4.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.reserved.names"> [lib.reserved.names]</a> paragraph 1:</p> <blockquote> [<i>Note:</i> A program may explicitly instantiate standard library templates, even when an explicit instantiation does not depend on @@ -786,177 +1039,40 @@ different explicit instantiations might be harmless.</p> </blockquote> </blockquote> -<p><i>[Copenhagen: LWG discussed three options. (1) Users may not -explicitly instantiate standard library templates, except on -user-defined types. Consequence: library implementors may freely -specialize or instantiate templates. (2) Users may explicitly -instantiate any standard library template. Consequence: if -implementors specialize or instantiate library templates, they may -need to take special steps to make sure users can do it too. (3) It -is implementation defined whether users may explicitly instantiate -standard library templates on non-user-defined types. Consequence: -library implementors may freely specialize or instantiate templates, -but may need to document some or all templates that have been -explicitly instantiated. -]</i></p> - -<p><i>[Straw poll (first number is favor, second is strongly oppose): 1 -- 4, 0; 2 - 9, 1; 3 - 0, 9. (Proposed resolution 1 was the original -proposed resolution.) Because there was no support for option 3, no -wording is provided.]</i></p> - -<p><i>[Redmond: discussed again; straw poll had results similar to -those of Copenhagen (1 - 1, 3; 2 - 8, 4; 3 - 6, 2). Most people said -they could live with any option. The only objection to option 2 is -potential implementation difficulty. Steve Clamage volunteered do a -survey to see if there are any popular platforms where option 2 would -present a real problem for implementors. See his reflector message, -c++std-lib-9002. -]</i></p> - -<p><i>[Steve and Pete Becker will talk to Jonathan Caves. The -Microsoft linker might present a problem if there are multiple copies, -some of which have static data and some of which are in DLLs. There -may be similar problems with the Apple linker; Matt will clarify -that.]</i></p> - -<hr> -<a name="123"><h3>123. Should valarray helper arrays fill functions be const?</h3></a><p> -<b>Section:</b> 26.3.5.4 <a href="lib-numerics.html#lib.slice.arr.fill"> [lib.slice.arr.fill]</a>, 26.3.7.4 <a href="lib-numerics.html#lib.gslice.array.fill"> [lib.gslice.array.fill]</a>, 26.3.8.4 <a href="lib-numerics.html#lib.mask.array.fill"> [lib.mask.array.fill]</a>, 26.3.9.4 <a href="lib-numerics.html#lib.indirect.array.fill"> [lib.indirect.array.fill]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998 </p> -<p>One of the operator= in the valarray helper arrays is const and one -is not. For example, look at slice_array. This operator= in Section -26.3.5.2 <a href="lib-numerics.html#lib.slice.arr.assign"> [lib.slice.arr.assign]</a> is const: </p> - -<p> <tt>void operator=(const valarray<T>&) const;</tt> </p> - -<p>but this one in Section 26.3.5.4 <a href="lib-numerics.html#lib.slice.arr.fill"> [lib.slice.arr.fill]</a> is not: </p> - -<p> <tt>void operator=(const T&); </tt> -</p> - -<p>The description of the semantics for these two functions is similar. </p> -<p><b>Proposed resolution:</b></p> - -<p>26.3.5 <a href="lib-numerics.html#lib.template.slice.array"> [lib.template.slice.array]</a> Template class slice_array</p> -<blockquote> - - <p>In the class template definition for slice_array, replace the member - function declaration</p> - <pre> - void operator=(const T&); - </pre> - <p>with</p> - <pre> - void operator=(const T&) const; - </pre> -</blockquote> - -<p>26.3.5.4 <a href="lib-numerics.html#lib.slice.arr.fill"> [lib.slice.arr.fill]</a> slice_array fill function</p> -<blockquote> - - <p>Change the function declaration</p> - <pre> - void operator=(const T&); - </pre> - <p>to</p> - <pre> - void operator=(const T&) const; - </pre> -</blockquote> - -<p>26.3.7 <a href="lib-numerics.html#lib.template.gslice.array"> [lib.template.gslice.array]</a> Template class gslice_array</p> -<blockquote> - - <p>In the class template definition for gslice_array, replace the member - function declaration</p> - <pre> - void operator=(const T&); - </pre> - <p>with</p> - <pre> - void operator=(const T&) const; - </pre> -</blockquote> - -<p>26.3.7.4 <a href="lib-numerics.html#lib.gslice.array.fill"> [lib.gslice.array.fill]</a> gslice_array fill function</p> -<blockquote> - - <p>Change the function declaration</p> - <pre> - void operator=(const T&); - </pre> - <p>to</p> - <pre> - void operator=(const T&) const; - </pre> -</blockquote> - -<p>26.3.8 <a href="lib-numerics.html#lib.template.mask.array"> [lib.template.mask.array]</a> Template class mask_array</p> -<blockquote> - - <p>In the class template definition for mask_array, replace the member - function declaration</p> - <pre> - void operator=(const T&); - </pre> - <p>with</p> - <pre> - void operator=(const T&) const; - </pre> -</blockquote> - -<p>26.3.8.4 <a href="lib-numerics.html#lib.mask.array.fill"> [lib.mask.array.fill]</a> mask_array fill function</p> -<blockquote> - - <p>Change the function declaration</p> - <pre> - void operator=(const T&); - </pre> - <p>to</p> - <pre> - void operator=(const T&) const; - </pre> -</blockquote> - -<p>26.3.9 <a href="lib-numerics.html#lib.template.indirect.array"> [lib.template.indirect.array]</a> Template class indirect_array</p> -<blockquote> - - <p>In the class template definition for indirect_array, replace the member - function declaration</p> - <pre> - void operator=(const T&); - </pre> - <p>with</p> - <pre> - void operator=(const T&) const; - </pre> -</blockquote> - -<p>26.3.9.4 <a href="lib-numerics.html#lib.indirect.array.fill"> [lib.indirect.array.fill]</a> indirect_array fill function</p> -<blockquote> - - <p>Change the function declaration</p> - <pre> - void operator=(const T&); - </pre> - <p>to</p> - <pre> - void operator=(const T&) const; - </pre> -</blockquote> - - -<p><i>[Redmond: Robert provided wording.]</i></p> - -<p><b>Rationale:</b></p> -<p>There's no good reason for one version of operator= being const and -another one not. Because of issue <a href="lwg-active.html#253">253</a>, this now -matters: these functions are now callable in more circumstances. In -many existing implementations, both versions are already const.</p> +<p>The LWG rejected this because it was believed that it would make + it unnecessarily difficult for library implementors to write + high-quality implementations. A program may not include an + explicit instantiation of the same template, for the same template + arguments, in two different translation units. If users are + allowed to provide explicit instantiations of Standard Library + templates for built-in types, then library implementors aren't, + at least not without nonportable tricks.</p> + +<p>The most serious problem is a class template that has writeable + static member variables. Unfortunately, such class templates are + important and, in existing Standard Library implementations, are + often explicitly specialized by library implementors: locale facets, + which have a writeable static member variable <tt>id</tt>. If a + user's explicit instantiation collided with the implementations + explicit instantiation, iostream initialization could cause locales + to be constructed in an inconsistent state.</p> + +<p>One proposed implementation technique was for Standard Library + implementors to provide explicit instantiations in separate object + files, so that they would not be picked up by the linker when the + user also provides an explicit instantiation. However, this + technique only applies for Standard Library implementations that + are packaged as static archives. Most Standard Library + implementations nowadays are packaged as dynamic libraries, so this + technique would not apply.</p> + +<p>The Committee is now considering standardization of dynamic + linking. If there are such changes in the future, it may be + appropriate to revisit this issue later.</p> <hr> <a name="167"><h3>167. Improper use of <tt>traits_type::length()</tt> </h3></a><p> -<b>Section:</b> 27.6.2.5.4 <a href="lib-iostreams.html#lib.ostream.inserters.character"> [lib.ostream.inserters.character]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<b>Section:</b> 27.6.2.5.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.inserters.character"> [lib.ostream.inserters.character]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>Paragraph 4 states that the length is determined using <tt>traits::length(s)</tt>. Unfortunately, this function is not defined for example if the character type is <tt>wchar_t</tt> and the @@ -965,7 +1081,7 @@ the character type is <tt>char</tt> and the type of <tt>s</tt> is either <tt>signed char const*</tt> or <tt>unsigned char const*</tt>.</p> <p><b>Proposed resolution:</b></p> -<p>Change 27.6.2.5.4 <a href="lib-iostreams.html#lib.ostream.inserters.character"> [lib.ostream.inserters.character]</a> paragraph 4 from:</p> +<p>Change 27.6.2.5.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.inserters.character"> [lib.ostream.inserters.character]</a> paragraph 4 from:</p> <blockquote> <p>Effects: Behaves like an formatted inserter (as described in lib.ostream.formatted.reqmts) of out. After a sentry object is @@ -980,226 +1096,61 @@ const*</tt>.</p> <blockquote> <p>Effects: Behaves like an formatted inserter (as described in lib.ostream.formatted.reqmts) of out. After a sentry object is - constructed it inserts characters. The number len of characters - starting at s to be inserted is</p> - <p> - - traits::length((const char*)s) if the second argument is of type - const charT*<br> - - char_traits<char>::length(s) if the second argument is of - type const char*, const signed char*, or const unsigned char* and - and charT is not char.<br> - </p> + constructed it inserts <i>n</i> characters starting at <i>s</i>, + where <i>n</i> is:</p> + <ul> + <li>traits::length(s) for the overload where the first argument is of + type basic_ostream<charT, traits>& and the second is + of type const charT*, and also for the overload where the first + argument is of type basic_ostream<char, traits>& and + the second is of type const char*.</li> + <li>std::char_traits<char>::length(s) + for the overload where the first argument is of type + basic_ostream<charT, traits>& and the second is of type + const char*.</li> + <li>traits::length(reinterpret_cast<const char*>(s)) + for the other two overloads.</li> + </ul> <p>Padding is determined as described in - lib.facet.num.put.virtuals. The len characters starting at s are - widened using out.widen (lib.basic.ios.members). The widened - characters and any required padding are inserted into out. Calls - width(0).</p> -</blockquote> - -<p><i>[Kona: It is clear to the LWG there is a defect here. -Dietmar will supply specific wording.]</i></p> - -<p><i>[Post-Tokyo: Dietmar supplied the above wording.]</i></p> - -<p><i>[Toronto: The original proposed resolution involved -char_traits<signed char> and char_traits<unsigned char>. -There was strong opposition to requiring that library implementors -provide those specializations of char_traits.]</i></p> - -<p><i>[Copenhagen: This still isn't quite right: proposed resolution -text got garbled when the signed char/unsigned char specializations -were removed. Dietmar will provide revised wording.]</i></p> -<hr> -<a name="179"><h3>179. Comparison of const_iterators to iterators doesn't work</h3></a><p> -<b>Section:</b> 23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 2 Jul 1998</p> -<p>Currently the following will not compile on two well-known standard -library implementations:</p> - -<blockquote> - <pre>#include <set> -using namespace std; - -void f(const set<int> &s) -{ - set<int>::iterator i; - if (i==s.end()); // s.end() returns a const_iterator -}</pre> -</blockquote> - -<p> -The reason this doesn't compile is because operator== was implemented -as a member function of the nested classes set:iterator and -set::const_iterator, and there is no conversion from const_iterator to -iterator. Surprisingly, (s.end() == i) does work, though, because of -the conversion from iterator to const_iterator. -</p> - -<p> -I don't see a requirement anywhere in the standard that this must -work. Should there be one? If so, I think the requirement would need -to be added to the tables in section 24.1.1. I'm not sure about the -wording. If this requirement existed in the standard, I would think -that implementors would have to make the comparison operators -non-member functions.</p> - -<p>This issues was also raised on comp.std.c++ by Darin -Adler. The example given was:</p> - -<blockquote> - <pre>bool check_equal(std::deque<int>::iterator i, -std::deque<int>::const_iterator ci) -{ -return i == ci; -}</pre> -</blockquote> - -<p>Comment from John Potter:</p> -<blockquote> - <p> - In case nobody has noticed, accepting it will break reverse_iterator. - </p> - - <p> - The fix is to make the comparison operators templated on two types. - </p> - - <pre> - template <class Iterator1, class Iterator2> - bool operator== (reverse_iterator<Iterator1> const& x, - reverse_iterator<Iterator2> const& y); - </pre> - - <p> - Obviously: return x.base() == y.base(); - </p> - - <p> - Currently, no reverse_iterator to const_reverse_iterator compares are - valid. - </p> - - <p> - BTW, I think the issue is in support of bad code. Compares should be - between two iterators of the same type. All std::algorithms require - the begin and end iterators to be of the same type. - </p> -</blockquote> -<p><b>Proposed resolution:</b></p> -<p>Insert this paragraph after 23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> paragraph 7:</p> -<blockquote> - <p>In the expressions</p> - <pre> - i == j - i != j - i < j - i <= j - i >= j - i > j - i - j - </pre> - <p>Where i and j denote objects of a container's iterator type, - either or both may be replaced by an object of the container's - const_iterator type referring to the same element with no - change in semantics.</p> + lib.facet.num.put.virtuals. The <i>n</i> characters starting at + <i>s</i> are widened using out.widen (lib.basic.ios.members). The + widened characters and any required padding are inserted into + out. Calls width(0).</p> </blockquote> -<p><i>[post-Toronto: Judy supplied a proposed resolution saying that -<tt>iterator</tt> and <tt>const_iterator</tt> could be freely mixed in -iterator comparison and difference operations.]</i></p> +<p><i>[Santa Cruz: Matt supplied new wording]</i></p> -<p><i>[Redmond: Dave and Howard supplied a new proposed resolution which -explicitly listed expressions; there was concern that the previous -proposed resolution was too informal.]</i></p> <p><b>Rationale:</b></p> -<p> -The LWG believes it is clear that the above wording applies only to -the nested types <tt>X::iterator</tt> and <tt>X::const_iterator</tt>, -where <tt>X</tt> is a container. There is no requirement that -<tt>X::reverse_iterator</tt> and <tt>X::const_reverse_iterator</tt> -can be mixed. If mixing them is considered important, that's a -separate issue. (Issue <a href="lwg-active.html#280">280</a>.) -</p> -<hr> -<a name="187"><h3>187. iter_swap underspecified</h3></a><p> -<b>Section:</b> 25.2.2 <a href="lib-algorithms.html#lib.alg.swap"> [lib.alg.swap]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 14 Aug 1999</p> -<p>The description of iter_swap in 25.2.2 paragraph 7,says that it ``exchanges the values'' -of the objects to which two iterators refer.<br> -<br> -What it doesn't say is whether it does so using swap or using the assignment operator and copy constructor.<br> -<br> -This question is an important one to answer, because swap is specialized to work efficiently for standard containers.<br> -For example:</p> -<blockquote> -<pre>vector<int> v1, v2; -iter_swap(&v1, &v2);</pre> -</blockquote> -<p>Is this call to iter_swap equivalent to calling swap(v1, v2)? Or is it equivalent to</p> -<blockquote> -<pre>{ -vector<int> temp = v1; -v1 = v2; -v2 = temp; -}</pre> -</blockquote> -<p>The first alternative is O(1); the second is O(n).</p> -<p>A LWG member, Dave Abrahams, comments:</p> -<blockquote> -<p>Not an objection necessarily, but I want to point out the cost of that requirement:</p> - <blockquote> -<p><tt>iter_swap(list<T>::iterator, list<T>::iterator)</tt></p> - </blockquote> -<p>can currently be specialized to be more efficient than iter_swap(T*,T*) for many T (by using splicing). Your proposal would make that optimization -illegal. </p> -</blockquote> - -<p><i>[Kona: The LWG notes the original need for iter_swap was proxy iterators -which are no longer permitted.]</i></p> -<p><b>Proposed resolution:</b></p> -<p>Change the effect clause of iter_swap in 25.2.2 paragraph 7 from:</p> -<blockquote> -<p>Exchanges the values pointed to by the two iterators a and b.</p> -</blockquote> -<p>to</p> -<blockquote> -<p> -<tt>swap(*a, *b)</tt>.</p> -</blockquote> - -<p><i>[post-Toronto: The LWG is concerned about possible -overspecification: there may be cases, such as Dave Abrahams's example -above, and such as vector<bool>'s iterators, where it makes more -sense for iter_swap to do something other than swap. If performance -is a concern, it may be better to have explicit complexity -requirements than to say how iter_swap should be implemented.]</i></p> - -<p><i>[Redmond: Discussed, with no consensus. There was very little -support for the proposed resolution. Some people favored closing this -issue as NAD. Others favored a more complicated specification of -<tt>iter_swap</tt>, which might distinguish between ordinary iterators -and proxies. A possible new issue: how do we know that the iterators -passed to <tt>iter_swap</tt> have Assignable value types? (If this -new issue is real, it extends far beyond just -<tt>iter_swap</tt>.)]</i></p> - +<p>We have five separate cases. In two of them we can use the +user-supplied traits class without any fuss. In the other three we +try to use something as close to that user-supplied class as possible. +In two cases we've got a traits class that's appropriate for +char and what we've got is a const signed char* or a const +unsigned char*; that's close enough so we can just use a reinterpret +cast, and continue to use the user-supplied traits class. Finally, +there's one case where we just have to give up: where we've got a +traits class for some arbitrary charT type, and we somehow have to +deal with a const char*. There's nothing better to do but fall back +to char_traits<char></p> <hr> <a name="197"><h3>197. max_size() underspecified</h3></a><p> -<b>Section:</b> 20.1.5 <a href="lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a>, 23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 21 Oct 1999</p> +<b>Section:</b> 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a>, 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 21 Oct 1999</p> <p>Must the value returned by max_size() be unchanged from call to call? </p> <p>Must the value returned from max_size() be meaningful? </p> <p>Possible meanings identified in lib-6827: </p> -<p>1) The largest container the implementation can support given "best -case" conditions - i.e. assume the run-time platform is "configured to -the max", and no overhead from the program itself. This may possibly +<p>1) The largest container the implementation can support given "best +case" conditions - i.e. assume the run-time platform is "configured to +the max", and no overhead from the program itself. This may possibly be determined at the point the library is written, but certainly no later than compile time.<br> <br> -2) The largest container the program could create, given "best case" +2) The largest container the program could create, given "best case" conditions - i.e. same platform assumptions as (1), but take into account any overhead for executing the program itself. (or, roughly -"storage=storage-sizeof(program)"). This does NOT include any resource +"storage=storage-sizeof(program)"). This does NOT include any resource allocated by the program. This may (or may not) be determinable at compile time.<br> <br> @@ -1215,21 +1166,21 @@ into account the actual currently available resources). This, obviously, has to be determined dynamically each time max_size() is called. </p> <p><b>Proposed resolution:</b></p> -<p>Change 20.1.5 <a href="lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> table 32 max_size() wording from:<br> +<p>Change 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> table 32 max_size() wording from:<br> <br> the largest value that can meaningfully be passed to X::allocate<br> to:<br> the value of the largest constant expression -(5.19 <a href="expr.html#expr.const"> [expr.const]</a>) that could ever meaningfully be passed to X::allocate</p> +(5.19 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/expr.html#expr.const"> [expr.const]</a>) that could ever meaningfully be passed to X::allocate</p> <p> -Change 23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> table 65 max_size() wording from:<br> +Change 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> table 65 max_size() wording from:<br> <br> size() of the largest possible container.<br> to:<br> the value of the largest constant expression -(5.19 <a href="expr.html#expr.const"> [expr.const]</a>) that could ever meaningfully be returned by X::size(). +(5.19 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/expr.html#expr.const"> [expr.const]</a>) that could ever meaningfully be returned by X::size(). </p> <p><i>[Kona: The LWG informally discussed this and asked Andy Sawyer to submit @@ -1238,8 +1189,8 @@ an issue.]</i></p> <p><i>[Tokyo: The LWG believes (1) above is the intended meaning.]</i></p> <p><i>[Post-Tokyo: Beman Dawes supplied the above resolution at the -request of the LWG. 21.3.3 <a href="lib-strings.html#lib.string.capacity"> [lib.string.capacity]</a> was not changed because it -references max_size() in 23.1. The term "compile-time" was +request of the LWG. 21.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.capacity"> [lib.string.capacity]</a> was not changed because it +references max_size() in 23.1. The term "compile-time" was avoided because it is not defined anywhere in the standard (even though it is used several places in the library clauses).]</i></p> @@ -1249,44 +1200,11 @@ function than as an allocator member function. For the latter, it is probably best thought of as an architectural limit. Nathan will provide new wording.]</i></p> <hr> -<a name="200"><h3>200. Forward iterator requirements don't allow constant iterators</h3></a><p> -<b>Section:</b> 24.1.3 <a href="lib-iterators.html#lib.forward.iterators"> [lib.forward.iterators]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 19 Nov 1999</p> -<p> -In table 74, the return type of the expression <tt>*a</tt> is given -as <tt>T&</tt>, where <tt>T</tt> is the iterator's value type. -For constant iterators, however, this is wrong. ("Value type" -is never defined very precisely, but it is clear that the value type -of, say, <tt>std::list<int>::const_iterator</tt> is supposed to be -<tt>int</tt>, not <tt>const int</tt>.) -</p> -<p><b>Proposed resolution:</b></p> -<p> -In table 74, in the <tt>*a</tt> and <tt>*r++</tt> rows, change the -return type from "<tt>T&</tt>" to "<tt>T&</tt> -if <tt>X</tt> is mutable, otherwise <tt>const T&</tt>". -In the <tt>a->m</tt> row, change the return type from -"<tt>U&</tt>" to "<tt>U&</tt> if <tt>X</tt> is mutable, -otherwise <tt>const U&</tt>". -</p> - -<p><i>[Tokyo: The LWG believes this is the tip of a larger iceberg; -there are multiple const problems with the STL portion of the library -and that these should be addressed as a single package. Note -that issue <a href="lwg-closed.html#180">180</a> has already been declared NAD Future for -that very reason.]</i></p> - -<p><i>[Redmond: the LWG thinks this is separable from other constness -issues. This issue is just cleanup; it clarifies language that was -written before we had iterator_traits. Proposed resolution was -modified: the original version only discussed *a. It was pointed out -that we also need to worry about *r++ and a->m.]</i></p> - -<hr> <a name="201"><h3>201. Numeric limits terminology wrong</h3></a><p> -<b>Section:</b> 18.2.1 <a href="lib-support.html#lib.limits"> [lib.limits]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Stephen Cleary <b>Date:</b> 21 Dec 1999</p> +<b>Section:</b> 18.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.limits"> [lib.limits]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Stephen Cleary <b>Date:</b> 21 Dec 1999</p> <p> -In some places in this section, the terms "fundamental types" and -"scalar types" are used when the term "arithmetic types" is intended. +In some places in this section, the terms "fundamental types" and +"scalar types" are used when the term "arithmetic types" is intended. The current usage is incorrect because void is a fundamental type and pointers are scalar types, neither of which should have specializations of numeric_limits. @@ -1295,26 +1213,34 @@ specializations of numeric_limits. <p>Change 18.2 [lib.support.limits] para 1 from:</p> <blockquote> -<p> The headers <limits>, <climits>, and <cfloat> supply characteristics of implementation-dependent fundamental types (3.9.1).</p> +<p> The headers <limits>, <climits>, and <cfloat> +supply characteristics of implementation-dependent fundamental types +(3.9.1).</p> </blockquote> <p>to:</p> <blockquote> -<p> The headers <limits>, <climits>, and <cfloat> supply characteristics of implementation-dependent arithmetic types (3.9.1).</p> +<p> The headers <limits>, <climits>, and <cfloat> +supply characteristics of implementation-dependent arithmetic types +(3.9.1).</p> </blockquote> <p>Change 18.2.1 [lib.limits] para 1 from:</p> <blockquote> -<p> The numeric_limits component provides a C++ program with information about various properties of the implementation's representation of the fundamental +<p> The numeric_limits component provides a C++ program with +information about various properties of the implementation's +representation of the fundamental types.</p> </blockquote> <p>to:</p> <blockquote> -<p> The numeric_limits component provides a C++ program with information about various properties of the implementation's representation of the arithmetic +<p> The numeric_limits component provides a C++ program with +information about various properties of the implementation's +representation of the arithmetic types.</p> </blockquote> @@ -1345,259 +1271,33 @@ types.</p> <p>Change 18.2.1.1 [lib.numeric.limits] para 1 from:</p> <blockquote> -<p> The member is_specialized makes it possible to distinguish between fundamental types, which have specializations, and non-scalar types, which +<p> The member is_specialized makes it possible to distinguish between +fundamental types, which have specializations, and non-scalar types, +which do not.</p> </blockquote> <p>to:</p> <blockquote> -<p> The member is_specialized makes it possible to distinguish between arithmetic types, which have specializations, and non-arithmetic types, +<p> The member is_specialized makes it possible to distinguish between +arithmetic types, which have specializations, and non-arithmetic types, which do not.</p> </blockquote> <p><i>[post-Toronto: The opinion of the LWG is that the wording in the standard, as well as the wording of the proposed resolution, is -flawed. The term "arithmetic types" is well defined in C +flawed. The term "arithmetic types" is well defined in C and C++, and it is not clear that the term is being used correctly. -It is also not clear that the term "implementation -dependent" has any useful meaning in this context. The biggest +It is also not clear that the term "implementation +dependent" has any useful meaning in this context. The biggest problem is that numeric_limits seems to be intended both for built-in types and for user-defined types, and the standard doesn't make it clear how numeric_limits applies to each of those cases. A wholesale review of numeric_limits is needed. A paper would be welcome.]</i></p> <hr> -<a name="202"><h3>202. unique() effects unclear when predicate not an equivalence relation</h3></a><p> -<b>Section:</b> 25.2.8 <a href="lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 13 Jan 2000</p> -<p> -What should unique() do if you give it a predicate that is not an -equivalence relation? There are at least two plausible answers: -</p> - -<blockquote> - -<p> - 1. You can't, because 25.2.8 says that it it "eliminates all but - the first element from every consecutive group of equal - elements..." and it wouldn't make sense to interpret "equal" as - meaning anything but an equivalence relation. [It also doesn't - make sense to interpret "equal" as meaning ==, because then there - would never be any sense in giving a predicate as an argument at - all.] -</p> - -<p> - 2. The word "equal" should be interpreted to mean whatever the - predicate says, even if it is not an equivalence relation - (and in particular, even if it is not transitive). -</p> - -</blockquote> - -<p> -The example that raised this question is from Usenet: -</p> - -<blockquote> - -<pre>int f[] = { 1, 3, 7, 1, 2 }; -int* z = unique(f, f+5, greater<int>());</pre> - -</blockquote> - -<p> -If one blindly applies the definition using the predicate -greater<int>, and ignore the word "equal", you get: -</p> - -<blockquote> - -<p> - Eliminates all but the first element from every consecutive group - of elements referred to by the iterator i in the range [first, last) - for which *i > *(i - 1). -</p> - -</blockquote> - -<p> -The first surprise is the order of the comparison. If we wanted to -allow for the predicate not being an equivalence relation, then we -should surely compare elements the other way: pred(*(i - 1), *i). If -we do that, then the description would seem to say: "Break the -sequence into subsequences whose elements are in strictly increasing -order, and keep only the first element of each subsequence". So the -result would be 1, 1, 2. If we take the description at its word, it -would seem to call for strictly DEcreasing order, in which case the -result should be 1, 3, 7, 2.<br> -<br> -In fact, the SGI implementation of unique() does neither: It yields 1, -3, 7. -</p> -<p><b>Proposed resolution:</b></p> -<p>Change 25.2.8 <a href="lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> paragraph 1 to:</p> -<blockquote> -For a nonempty range, eliminates all but the first element from every -consecutive group of equivalent elements referred to by the iterator -<tt>i</tt> in the range [first+1, last) for which the following -conditions hold: <tt>*(i-1) == *i</tt> or <tt>pred(*(i-1), *i) != -false</tt>. -</blockquote> - -<p> -Also insert a new paragraph, paragraph 2a, that reads: "Requires: The -comparison function must be an equivalence relation." -</p> - -<p><i>[Redmond: discussed arguments for and against requiring the -comparison function to be an equivalence relation. Straw poll: -14-2-5. First number is to require that it be an equivalence -relation, second number is to explicitly not require that it be an -equivalence relation, third number is people who believe they need -more time to consider the issue. A separate issue: Andy Sawyer -pointed out that "i-1" is incorrect, since "i" can refer to the first -iterator in the range. Matt provided wording to address this -problem.]</i></p> - -<p><i>[Curaçao: The LWG changed "... the range (first, -last)..." to "... the range [first+1, last)..." for -clarity. They considered this change close enough to editorial to not -require another round of review.]</i></p> - -<p><b>Rationale:</b></p> -<p>The LWG also considered an alternative resolution: change -25.2.8 <a href="lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> paragraph 1 to:</p> - -<blockquote> -For a nonempty range, eliminates all but the first element from every -consecutive group of elements referred to by the iterator -<tt>i</tt> in the range (first, last) for which the following -conditions hold: <tt>*(i-1) == *i</tt> or <tt>pred(*(i-1), *i) != -false</tt>. -</blockquote> - -<p> -Also insert a new paragraph, paragraph 1a, that reads: "Notes: The -comparison function need not be an equivalence relation." -</p> - - -<p>Informally: the proposed resolution imposes an explicit requirement -that the comparison function be an equivalence relation. The -alternative resolution does not, and it gives enough information so -that the behavior of unique() for a non-equivalence relation is -specified. Both resolutions are consistent with the behavior of -existing implementations.</p> -<hr> -<a name="225"><h3>225. std:: algorithms use of other unqualified algorithms</h3></a><p> -<b>Section:</b> 17.4.4.3 <a href="lib-intro.html#lib.global.functions"> [lib.global.functions]</a> <b>Status:</b> <a href="lwg-active.html#Review">Review</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 01 Apr 2000</p> -<p>Are algorithms in std:: allowed to use other algorithms without qualification, so functions in -user namespaces might be found through Koenig lookup?</p> -<p>For example, a popular standard library implementation includes this -implementation of std::unique:</p> -<blockquote> -<pre>namespace std { - template <class _ForwardIter> - _ForwardIter unique(_ForwardIter __first, _ForwardIter __last) { - __first = adjacent_find(__first, __last); - return unique_copy(__first, __last, __first); - } - }</pre> -</blockquote> -<p>Imagine two users on opposite sides of town, each using unique on his own -sequences bounded by my_iterators . User1 looks at his standard library -implementation and says, "I know how to implement a more efficient -unique_copy for my_iterators", and writes:</p> -<blockquote> -<pre>namespace user1 { - class my_iterator; - // faster version for my_iterator - my_iterator unique_copy(my_iterator, my_iterator, my_iterator); - }</pre> -</blockquote> -<p>user1::unique_copy() is selected by Koenig lookup, as he intended.</p> -<p>User2 has other needs, and writes:</p> -<blockquote> -<pre>namespace user2 { - class my_iterator; - // Returns true iff *c is a unique copy of *a and *b. - bool unique_copy(my_iterator a, my_iterator b, my_iterator c); - }</pre> -</blockquote> -<p>User2 is shocked to find later that his fully-qualified use of -std::unique(user2::my_iterator, user2::my_iterator, user2::my_iterator) fails to -compile (if he's lucky). Looking in the standard, he sees the following Effects -clause for unique():</p> -<blockquote> - <p>Effects: Eliminates all but the first element from every consecutive group - of equal elements referred to by the iterator i in the range [first, last) for - which the following corresponding conditions hold: *i == *(i - 1) or pred(*i, - *(i - 1)) != false</p> -</blockquote> -<p>The standard gives user2 absolutely no reason to think he can interfere with -std::unique by defining names in namespace user2. His standard library has been -built with the template export feature, so he is unable to inspect the -implementation. User1 eventually compiles his code with another compiler, and -his version of unique_copy silently stops being called. Eventually, he realizes -that he was depending on an implementation detail of his library and had no -right to expect his unique_copy() to be called portably.</p> -<p>On the face of it, and given above scenario, it may seem obvious that the -implementation of unique() shown is non-conforming because it uses unique_copy() -rather than ::std::unique_copy(). Most standard library implementations, -however, seem to disagree with this notion.</p> -<p> <i>[Tokyo: Steve Adamczyk from -the core working group indicates that "std::" is sufficient; -leading "::" qualification is not required because any namespace -qualification is sufficient to suppress Koenig lookup.]</i> -</p> -<p><b>Proposed resolution:</b></p> -<p>Add a paragraph and a note at the end of -17.4.4.3 <a href="lib-intro.html#lib.global.functions"> [lib.global.functions]</a>:</p> -<blockquote> - -<p>Unless otherwise specified, no global or non-member function in the -standard library shall use a function from another namespace which is -found through <i>argument-dependent name lookup</i> (3.4.2 <a href="basic.html#basic.lookup.koenig"> [basic.lookup.koenig]</a>).</p> - -<p>[Note: the phrase "unless otherwise specified" is intended to -allow Koenig lookup in cases like that of ostream_iterators:<br> - -<br> - Effects:</p> - <blockquote> -<p>*out_stream << value;<br> - if(delim != 0) *out_stream << delim;<br> - return (*this);</p> - <p>--end note]</p> - </blockquote> -</blockquote> - -<p><i>[Tokyo: The LWG agrees that this is a defect in the standard, but -is as yet unsure if the proposed resolution is the best -solution. Furthermore, the LWG believes that the same problem of -unqualified library names applies to wording in the standard itself, -and has opened issue <a href="lwg-active.html#229">229</a> accordingly. Any resolution of -issue <a href="lwg-active.html#225">225</a> should be coordinated with the resolution of -issue <a href="lwg-active.html#229">229</a>.]</i></p> - -<p><i>[Toronto: The LWG is not sure if this is a defect in the -standard. Most LWG members believe that an implementation of -<tt>std::unique</tt> like the one quoted in this issue is already -illegal, since, under certain circumstances, its semantics are not -those specified in the standard. The standard's description of -<tt>unique</tt> does not say that overloading <tt>adjacent_find</tt> -should have any effect.]</i></p> - -<p><i>[Curaçao: An LWG-subgroup spent an afternoon working on issues -225, 226, and 229. Their conclusion was that the issues should be -separated into an LWG portion (Howard's paper, N1387=02-0045), and a -EWG portion (Dave will write a proposal). The LWG and EWG had -(separate) discussions of this plan the next day. The proposed -resolution for this issue is in accordance with Howard's paper.]</i></p> - -<hr> <a name="226"><h3>226. User supplied specializations or overloads of namespace std function templates</h3></a><p> -<b>Section:</b> 17.4.3.1 <a href="lib-intro.html#lib.reserved.names"> [lib.reserved.names]</a> <b>Status:</b> <a href="lwg-active.html#Review">Review</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 01 Apr 2000</p> +<b>Section:</b> 17.4.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.reserved.names"> [lib.reserved.names]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 01 Apr 2000</p> <p>The issues are: </p> <p>1. How can a 3rd party library implementor (lib1) write a version of a standard algorithm which is specialized to work with his own class template? </p> @@ -1635,12 +1335,12 @@ namespace lib2 and somewhat slippery. The implementor needs to remember to write the using-declaration, or generic_sort will fail to compile when T is a built-in type. The second drawback is that the use of this style in lib2 effectively -"reserves" names in any namespace which defines types which may +"reserves" names in any namespace which defines types which may eventually be used with lib2. This may seem innocuous at first when applied to names like swap, but consider more ambiguous names like unique_copy() instead. It is easy to imagine the user wanting to define these names differently in his own namespace. A definition with semantics incompatible with the standard -library could cause serious problems (see issue <a href="lwg-active.html#225">225</a>).</p> +library could cause serious problems (see issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#225">225</a>).</p> <p>Why, you may ask, can't we just partially specialize std::swap()? It's because the language doesn't allow for partial specialization of function templates. If you write:</p> @@ -1661,8 +1361,8 @@ language rules. On the other hand, the following full specialization is legal:</ }</pre> </blockquote> -<p>This issue reflects concerns raised by the "Namespace issue -with specialized swap" thread on comp.lang.c++.moderated. A +<p>This issue reflects concerns raised by the "Namespace issue +with specialized swap" thread on comp.lang.c++.moderated. A similar set of concerns was earlier raised on the boost.org mailing list and the ACCU-general mailing list. Also see library reflector message c++std-lib-7354.</p> @@ -1682,11 +1382,11 @@ not provide an operator<< for std::pair<>. <p><b>Proposed resolution:</b></p> -<p>Adopt the wording in the <b>Customization Points</b> section of -Howard Hinnant's paper, N1387=02-0045.</p> +<p>Adopt the wording proposed in Howard Hinnant's paper N1439=03-0021, +"Proposed Resolution To LWG issues 225, 226, 229".</p> -<p><i>[Tokyo: Summary, "There is no conforming way to extend -std::swap for user defined templates." The LWG agrees that +<p><i>[Tokyo: Summary, "There is no conforming way to extend +std::swap for user defined templates." The LWG agrees that there is a problem. Would like more information before proceeding. This may be a core issue. Core issue 229 has been opened to discuss the core aspects of this problem. It was also noted that @@ -1695,8 +1395,8 @@ sources, but too late to be integrated into the issues list. ]</i></p> <p><i>[Post-Tokyo: A paper with several proposed resolutions, -J16/00-0029==WG21/N1252, "Shades of namespace std functions -" by Alan Griffiths, is in the Post-Tokyo mailing. It +J16/00-0029==WG21/N1252, "Shades of namespace std functions +" by Alan Griffiths, is in the Post-Tokyo mailing. It should be considered a part of this issue.]</i></p> <p><i>[Toronto: Dave Abrahams and Peter Dimov have proposed a @@ -1740,137 +1440,32 @@ unqualified call of <tt>swap</tt>. (And which other functions? Any?) A small group (Nathan, Howard, Jeremy, Dave, Matt, Walter, Marc) will try to put together a proposal before the next meeting.]</i></p> -<p><i>[Curaçao: An LWG-subgroup spent an afternoon working on issues +<p><i>[Curaçao: An LWG-subgroup spent an afternoon working on issues 225, 226, and 229. Their conclusion was that the issues should be separated into an LWG portion (Howard's paper, N1387=02-0045), and a EWG portion (Dave will write a proposal). The LWG and EWG had (separate) discussions of this plan the next day. The proposed resolution is the one proposed by Howard.]</i></p> -<hr> -<a name="229"><h3>229. Unqualified references of other library entities</h3></a><p> -<b>Section:</b> 17.4.1.1 <a href="lib-intro.html#lib.contents"> [lib.contents]</a> <b>Status:</b> <a href="lwg-active.html#Review">Review</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 19 Apr 2000</p> -<p>Throughout the library chapters, the descriptions of library entities refer -to other library entities without necessarily qualifying the names.</p> - -<p>For example, section 25.2.2 "Swap" describes the effect of -swap_ranges in terms of the unqualified name "swap". This section -could reasonably be interpreted to mean that the library must be implemented so -as to do a lookup of the unqualified name "swap", allowing users to -override any ::std::swap function when Koenig lookup applies.</p> - -<p>Although it would have been best to use explicit qualification with -"::std::" throughout, too many lines in the standard would have to be -adjusted to make that change in a Technical Corrigendum.</p> - -<p>Issue <a href="lwg-defects.html#182">182</a>, which addresses qualification of -<tt>size_t</tt>, is a special case of this. -</p> -<p><b>Proposed resolution:</b></p> -<p>To section 17.4.1.1 "Library contents" Add the following paragraph:</p> -<blockquote> - <p>Whenever a name x defined in the standard library is mentioned, the name x - is assumed to be fully qualified as ::std::x, unless explicitly described - otherwise. For example, if the Effects section for library function F is - described as calling library function G, the function ::std::G is meant.</p> -</blockquote> - -<p><i>[Post-Tokyo: Steve Clamage submitted this issue at the request of -the LWG to solve a problem in the standard itself similar to the -problem within implementations of library identified by issue <a href="lwg-active.html#225">225</a>. Any resolution of issue <a href="lwg-active.html#225">225</a> should be -coordinated with the resolution of this issue.]</i></p> - -<p><i>[post-Toronto: Howard is undecided about whether it is -appropriate for all standard library function names referred to in -other standard library functions to be explicitly qualified by -<tt>std</tt>: it is common advice that users should define global -functions that operate on their class in the same namespace as the -class, and this requires argument-dependent lookup if those functions -are intended to be called by library code. Several LWG members are -concerned that valarray appears to require argument-dependent lookup, -but that the wording may not be clear enough to fall under -"unless explicitly described otherwise".]</i></p> - -<p><i>[Curaçao: An LWG-subgroup spent an afternoon working on issues -225, 226, and 229. Their conclusion was that the issues should be -separated into an LWG portion (Howard's paper, N1387=02-0045), and a -EWG portion (Dave will write a proposal). The LWG and EWG had -(separate) discussions of this plan the next day. This paper resolves -issues 225 and 226. In light of that resolution, the proposed -resolution for the current issue makes sense.]</i></p> +<p><i>[Santa Cruz: the LWG agreed with the general direction of + Howard's paper, N1387. (Roughly: Koenig lookup is disabled unless + we say otherwise; this issue is about when we do say otherwise.) + However, there were concerns about wording. Howard will provide new + wording. Bill and Jeremy will review it.]</i></p> -<hr> -<a name="231"><h3>231. Precision in iostream?</h3></a><p> -<b>Section:</b> 22.2.2.2.2 <a href="lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#Review">Review</a> <b>Submitter:</b> James Kanze, Stephen Clamage <b>Date:</b> 25 Apr 2000</p> -<p>What is the following program supposed to output?</p> -<pre>#include <iostream> +<p><i>[Oxford: Howard proposed the new wording.]</i></p> - int - main() - { - std::cout.setf( std::ios::scientific , std::ios::floatfield ) ; - std::cout.precision( 0 ) ; - std::cout << 1.00 << '\n' ; - return 0 ; - }</pre> -<p>From my C experience, I would expect "1e+00"; this is what -<tt>printf("%.0e" , 1.00 );</tt> does. G++ outputs -"1.000000e+00".</p> - -<p>The only indication I can find in the standard is 22.2.2.2.2/11, -where it says "For conversion from a floating-point type, if -(flags & fixed) != 0 or if str.precision() > 0, then -str.precision() is specified in the conversion specification." -This is an obvious error, however, fixed is not a mask for a field, -but a value that a multi-bit field may take -- the results of and'ing -fmtflags with ios::fixed are not defined, at least not if -ios::scientific has been set. G++'s behavior corresponds to what might -happen if you do use (flags & fixed) != 0 with a typical -implementation (floatfield == 3 << something, fixed == 1 -<< something, and scientific == 2 << something).</p> - -<p>Presumably, the intent is either (flags & floatfield) != 0, or -(flags & floatfield) == fixed; the first gives something more or -less like the effect of precision in a printf floating point -conversion. Only more or less, of course. In order to implement printf -formatting correctly, you must know whether the precision was -explicitly set or not. Say by initializing it to -1, instead of 6, and -stating that for floating point conversions, if precision < -1, 6 -will be used, for fixed point, if precision < -1, 1 will be used, -etc. Plus, of course, if precision == 0 and flags & floatfield == -0, 1 should be = used. But it probably isn't necessary to emulate all -of the anomalies of printf:-).</p> -<p><b>Proposed resolution:</b></p> -<p> -Replace 22.2.2.2.2 <a href="lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a>, paragraph 11, with the following -sentence: -</p> -<blockquote> -For conversion from a floating-point type, -<tt><i>str</i>.precision()</tt> is specified in the conversion -specification. -</blockquote> <p><b>Rationale:</b></p> -<p>The floatfield determines whether numbers are formatted as if -with %f, %e, or %g. If the <tt>fixed</tt> bit is set, it's %f, -if <tt>scientific</tt> it's %e, and if both bits are set, or -neither, it's %g.</p> -<p>Turning to the C standard, a precision of 0 is meaningful -for %f and %e. For %g, precision 0 is taken to be the same as -precision 1.</p> -<p>The proposed resolution has the effect that if neither -<tt>fixed</tt> nor <tt>scientific</tt> is set we'll be -specifying a precision of 0, which will be internally -turned into 1. There's no need to call it out as a special -case.</p> -<p>The output of the above program will be "1e+00".</p> - -<p><i>[Post-Curaçao: Howard provided improved wording covering the case -where precision is 0 and mode is %g.]</i></p> - +<p>Informally: introduce a Swappable concept, and specify that the + value types of the iterators passed to certain standard algorithms + (such as iter_swap, swap_ranges, reverse, rotate, and sort) conform + to that concept. The Swappable concept will make it clear that + these algorithms use unqualified lookup for the calls + to <tt>swap</tt>. Also, in 26.3.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.valarray.transcend"> [lib.valarray.transcend]</a> paragraph 1, + state that the valarray transcendentals use unqualified lookup.</p> <hr> <a name="233"><h3>233. Insertion hints in associative containers</h3></a><p> -<b>Section:</b> 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 30 Apr 2000</p> +<b>Section:</b> 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 30 Apr 2000</p> <p> If <tt>mm</tt> is a multimap and <tt>p</tt> is an iterator into the multimap, then <tt>mm.insert(p, x)</tt> inserts @@ -1898,15 +1493,15 @@ disregard it entirely. The vote [in Redmond] was on whether to elaborately specify the use of the hint, or to require behavior only if the value could be inserted adjacent to the hint. I would like to ensure that we have a chance to -vote for a deterministic treatment: "before, if possible, otherwise -after, otherwise anywhere appropriate", as an alternative to the -proposed "before or after, if possible, otherwise [...]". +vote for a deterministic treatment: "before, if possible, otherwise +after, otherwise anywhere appropriate", as an alternative to the +proposed "before or after, if possible, otherwise [...]". </p> <p><b>Proposed resolution:</b></p> -<p>In table 69 "Associative Container Requirements" in 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a>, in the row for <tt>a.insert(p, t)</tt>, +<p>In table 69 "Associative Container Requirements" in 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a>, in the row for <tt>a.insert(p, t)</tt>, change</p> <blockquote> @@ -1958,72 +1553,17 @@ reference implementation.]</i></p> emerged from Copenhagen: it seemed excessively complicated, and went beyond fixing the defect that we identified in Toronto. PJP provided the new wording described in this issue. Nathan agrees that we -shouldn't adopt the more detailed semantics, and notes: "we know that +shouldn't adopt the more detailed semantics, and notes: "we know that you can do it efficiently enough with a red-black tree, but there are other (perhaps better) balanced tree techniques that might differ -enough to make the detailed semantics hard to satisfy."]</i></p> +enough to make the detailed semantics hard to satisfy."]</i></p> -<p><i>[Curaçao: Nathan should give us the alternative wording he +<p><i>[Curaçao: Nathan should give us the alternative wording he suggests so the LWG can decide between the two options.]</i></p> <hr> -<a name="241"><h3>241. Does unique_copy() require CopyConstructible and Assignable?</h3></a><p> -<b>Section:</b> 25.2.8 <a href="lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> May 15 2000</p> - -<p>Some popular implementations of unique_copy() create temporary -copies of values in the input sequence, at least if the input iterator -is a pointer. Such an implementation is built on the assumption that -the value type is CopyConstructible and Assignable.</p> - -<p>It is common practice in the standard that algorithms explicitly -specify any additional requirements that they impose on any of the -types used by the algorithm. An example of an algorithm that creates -temporary copies and correctly specifies the additional requirements -is accumulate(), 26.4.1 <a href="lib-numerics.html#lib.accumulate"> [lib.accumulate]</a>.</p> - -<p>Since the specifications of unique() and unique_copy() do not -require CopyConstructible and Assignable of the InputIterator's value -type the above mentioned implementations are not standard-compliant. I -cannot judge whether this is a defect in the standard or a defect in -the implementations.</p> -<p><b>Proposed resolution:</b></p> -<p>In 25.2.8 change:</p> - -<blockquote> --4- Requires: The ranges [first, last) and [result, result+(last-first)) -shall not overlap. -</blockquote> - -<p>to:</p> - -<blockquote> - <p>-4- Requires: The ranges [first, last) and [result, - result+(last-first)) shall not overlap. The expression *result = - *first must be valid. If neither InputIterator nor OutputIterator - meets the requirements of forward iterator then the value type of - InputIterator must be copy constructible. Otherwise copy - constructible is not required. </p> -</blockquote> - -<p><i>[Redmond: the original proposed resolution didn't impose an -explicit requirement that the iterator's value type must be copy -constructible, on the grounds that an input iterator's value type must -always be copy constructible. Not everyone in the LWG thought that -this requirement was clear from table 72. It has been suggested that -it might be possible to implement <tt>unique_copy</tt> without -requiring assignability, although current implementations do impose -that requirement. Howard provided new wording.]</i></p> - -<p><i>[ -Curaçao: The LWG changed the PR editorially to specify -"neither...nor...meet..." as clearer than -"both...and...do not meet...". Change believed to be so -minor as not to require re-review. -]</i></p> - -<hr> <a name="247"><h3>247. <tt>vector</tt>, <tt>deque::insert</tt> complexity</h3></a><p> -<b>Section:</b> 23.2.4.3 <a href="lib-containers.html#lib.vector.modifiers"> [lib.vector.modifiers]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Lisa Lippincott <b>Date:</b> 06 June 2000</p> +<b>Section:</b> 23.2.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.modifiers"> [lib.vector.modifiers]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Lisa Lippincott <b>Date:</b> 06 June 2000</p> <p>Paragraph 2 of 23.2.4.3 [lib.vector.modifiers] describes the complexity of <tt>vector::insert</tt>:</p> @@ -2056,7 +1596,7 @@ inserting at the end of the <tt>vector</tt>, and then using <p>I looked to see if <tt>deque</tt> had a similar problem, and was surprised to find that <tt>deque</tt> places no requirement on the -complexity of inserting multiple elements (23.2.1.3 <a href="lib-containers.html#lib.deque.modifiers"> [lib.deque.modifiers]</a>, +complexity of inserting multiple elements (23.2.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.deque.modifiers"> [lib.deque.modifiers]</a>, paragraph 3):</p> <blockquote> @@ -2093,15 +1633,14 @@ complicated than a while loop whose body is a single-element insert.]</i></p> <hr> <a name="253"><h3>253. valarray helper functions are almost entirely useless</h3></a><p> -<b>Section:</b> 26.3.2.1 <a href="lib-numerics.html#lib.valarray.cons"> [lib.valarray.cons]</a>, 26.3.2.2 <a href="lib-numerics.html#lib.valarray.assign"> [lib.valarray.assign]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Robert Klarer <b>Date:</b> 31 Jul 2000</p> +<b>Section:</b> 26.3.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.valarray.cons"> [lib.valarray.cons]</a>, 26.3.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.valarray.assign"> [lib.valarray.assign]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Robert Klarer <b>Date:</b> 31 Jul 2000</p> <p>This discussion is adapted from message c++std-lib-7056 posted November 11, 1999. I don't think that anyone can reasonably claim that the problem described below is NAD.</p> <p>These valarray constructors can never be called:</p> -<pre> - template <class T> +<pre> template <class T> valarray<T>::valarray(const slice_array<T> &); template <class T> valarray<T>::valarray(const gslice_array<T> &); @@ -2114,8 +1653,7 @@ that the problem described below is NAD.</p> <p>Similarly, these valarray assignment operators cannot be called:</p> -<pre> - template <class T> +<pre> template <class T> valarray<T> valarray<T>::operator=(const slice_array<T> &); template <class T> valarray<T> valarray<T>::operator=(const gslice_array<T> &); @@ -2127,8 +1665,7 @@ called:</p> <p>Please consider the following example:</p> -<pre> - #include <valarray> +<pre> #include <valarray> using namespace std; int main() @@ -2145,8 +1682,7 @@ std::slice_array<double>. This slice_array rvalue is then used to construct va2. The constructor that is used to construct va2 is declared like this:</p> -<pre> - template <class T> +<pre> template <class T> valarray<T>::valarray(const slice_array<T> &); </pre> @@ -2171,75 +1707,71 @@ classes are almost entirely useless.</p> <p><b>Proposed resolution:</b></p> <p>slice_array:</p> <ul> -<li> remove the copy constructor and copy-assignment operator declarations - from the slice_array class template definition in 26.3.5 <a href="lib-numerics.html#lib.template.slice.array"> [lib.template.slice.array]</a> </li> -<li> remove paragraph 3 of 26.3.5 <a href="lib-numerics.html#lib.template.slice.array"> [lib.template.slice.array]</a> +<li> Make the copy constructor and copy-assignment operator declarations + public in the slice_array class template definition in 26.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.slice.array"> [lib.template.slice.array]</a> </li> +<li> remove paragraph 3 of 26.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.slice.array"> [lib.template.slice.array]</a> </li> -<li> remove the copy constructor declaration from 26.3.5.1 <a href="lib-numerics.html#lib.cons.slice.arr"> [lib.cons.slice.arr]</a> +<li> remove the copy constructor declaration from 26.3.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.cons.slice.arr"> [lib.cons.slice.arr]</a> </li> -<li> change paragraph 1 of 26.3.5.1 <a href="lib-numerics.html#lib.cons.slice.arr"> [lib.cons.slice.arr]</a> to read "This constructor is declared - to be private. This constructor need not be defined."</li> -<li> remove the copy-assignment operator declaration from 26.3.5.2 <a href="lib-numerics.html#lib.slice.arr.assign"> [lib.slice.arr.assign]</a> +<li> change paragraph 1 of 26.3.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.cons.slice.arr"> [lib.cons.slice.arr]</a> to read "This constructor is declared + to be private. This constructor need not be defined."</li> +<li> remove the first sentence of paragraph 1 of 26.3.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.slice.arr.assign"> [lib.slice.arr.assign]</a> </li> -<li> remove the first sentence of paragraph 1 of 26.3.5.2 <a href="lib-numerics.html#lib.slice.arr.assign"> [lib.slice.arr.assign]</a> -</li> -<li> Change the first two words of the second sentence of paragraph 1 of - 26.3.5.2 <a href="lib-numerics.html#lib.slice.arr.assign"> [lib.slice.arr.assign]</a> to "This function."</li> +<li> Change the first three words of the second sentence of paragraph 1 of + 26.3.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.slice.arr.assign"> [lib.slice.arr.assign]</a> to "These assignment operators have"</li> </ul> <p>gslice_array:</p> <ul> -<li> remove the copy constructor and copy-assignment operator declarations - from the gslice_array class template definition in 26.3.7 <a href="lib-numerics.html#lib.template.gslice.array"> [lib.template.gslice.array]</a> </li> -<li> remove the note in paragraph 3 of 26.3.7 <a href="lib-numerics.html#lib.template.gslice.array"> [lib.template.gslice.array]</a> -</li> -<li> remove the copy constructor declaration from 26.3.7.1 <a href="lib-numerics.html#lib.gslice.array.cons"> [lib.gslice.array.cons]</a> +<li> Make the copy constructor and copy-assignment operator declarations + public in the gslice_array class template definition in 26.3.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.gslice.array"> [lib.template.gslice.array]</a> </li> +<li> remove the note in paragraph 3 of 26.3.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.gslice.array"> [lib.template.gslice.array]</a> </li> -<li> change paragraph 1 of 26.3.7.1 <a href="lib-numerics.html#lib.gslice.array.cons"> [lib.gslice.array.cons]</a> to read "This constructor is declared - to be private. This constructor need not be defined."</li> -<li> remove the copy-assignment operator declaration from 26.3.7.2 <a href="lib-numerics.html#lib.gslice.array.assign"> [lib.gslice.array.assign]</a> +<li> remove the copy constructor declaration from 26.3.7.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.gslice.array.cons"> [lib.gslice.array.cons]</a> </li> -<li> remove the first sentence of paragraph 1 of 26.3.7.2 <a href="lib-numerics.html#lib.gslice.array.assign"> [lib.gslice.array.assign]</a> +<li> change paragraph 1 of 26.3.7.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.gslice.array.cons"> [lib.gslice.array.cons]</a> to read "This constructor is declared + to be private. This constructor need not be defined."</li> +<li> remove the first sentence of paragraph 1 of 26.3.7.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.gslice.array.assign"> [lib.gslice.array.assign]</a> </li> -<li> Change the first two words of the second sentence of paragraph 1 of - 26.3.7.2 <a href="lib-numerics.html#lib.gslice.array.assign"> [lib.gslice.array.assign]</a> to "This function."</li> +<li> Change the first three words of the second sentence of paragraph 1 of + 26.3.7.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.gslice.array.assign"> [lib.gslice.array.assign]</a> to "These assignment operators have"</li> </ul> <p>mask_array:</p> <ul> -<li> remove the copy constructor and copy-assignment operator declarations - from the mask_array class template definition in 26.3.8 <a href="lib-numerics.html#lib.template.mask.array"> [lib.template.mask.array]</a> </li> -<li> remove the note in paragraph 2 of 26.3.8 <a href="lib-numerics.html#lib.template.mask.array"> [lib.template.mask.array]</a> +<li> Make the copy constructor and copy-assignment operator declarations + public in the mask_array class template definition in 26.3.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.mask.array"> [lib.template.mask.array]</a> </li> +<li> remove the note in paragraph 2 of 26.3.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.mask.array"> [lib.template.mask.array]</a> </li> -<li> remove the copy constructor declaration from 26.3.8.1 <a href="lib-numerics.html#lib.mask.array.cons"> [lib.mask.array.cons]</a> +<li> remove the copy constructor declaration from 26.3.8.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.mask.array.cons"> [lib.mask.array.cons]</a> </li> -<li> change paragraph 1 of 26.3.8.1 <a href="lib-numerics.html#lib.mask.array.cons"> [lib.mask.array.cons]</a> to read "This constructor is declared - to be private. This constructor need not be defined."</li> -<li> remove the first sentence of paragraph 1 of 26.3.8.2 <a href="lib-numerics.html#lib.mask.array.assign"> [lib.mask.array.assign]</a> +<li> change paragraph 1 of 26.3.8.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.mask.array.cons"> [lib.mask.array.cons]</a> to read "This constructor is declared + to be private. This constructor need not be defined."</li> +<li> remove the first sentence of paragraph 1 of 26.3.8.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.mask.array.assign"> [lib.mask.array.assign]</a> </li> -<li> Change the first two words of the second sentence of paragraph 1 of - 26.3.8.2 <a href="lib-numerics.html#lib.mask.array.assign"> [lib.mask.array.assign]</a> to "This function."</li> +<li> Change the first three words of the second sentence of paragraph 1 of + 26.3.8.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.mask.array.assign"> [lib.mask.array.assign]</a> to "These assignment operators have"</li> </ul> <p>indirect_array:</p> <ul> -<li>remove the copy constructor and copy-assignment operator declarations - from the indirect_array class definition in 26.3.9 <a href="lib-numerics.html#lib.template.indirect.array"> [lib.template.indirect.array]</a> +<li>Make the copy constructor and copy-assignment operator declarations + public in the indirect_array class definition in 26.3.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.indirect.array"> [lib.template.indirect.array]</a> </li> -<li> remove the note in paragraph 2 of 26.3.9 <a href="lib-numerics.html#lib.template.indirect.array"> [lib.template.indirect.array]</a> +<li> remove the note in paragraph 2 of 26.3.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.indirect.array"> [lib.template.indirect.array]</a> </li> -<li> remove the copy constructor declaration from 26.3.9.1 <a href="lib-numerics.html#lib.indirect.array.cons"> [lib.indirect.array.cons]</a> +<li> remove the copy constructor declaration from 26.3.9.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.indirect.array.cons"> [lib.indirect.array.cons]</a> </li> -<li> change the descriptive text in 26.3.9.1 <a href="lib-numerics.html#lib.indirect.array.cons"> [lib.indirect.array.cons]</a> to read "This constructor is - declared to be private. This constructor need not be defined."</li> -<li> remove the first sentence of paragraph 1 of 26.3.9.2 <a href="lib-numerics.html#lib.indirect.array.assign"> [lib.indirect.array.assign]</a> +<li> change the descriptive text in 26.3.9.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.indirect.array.cons"> [lib.indirect.array.cons]</a> to read "This constructor is + declared to be private. This constructor need not be defined."</li> +<li> remove the first sentence of paragraph 1 of 26.3.9.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.indirect.array.assign"> [lib.indirect.array.assign]</a> </li> -<li> Change the first two words of the second sentence of paragraph 1 of - 26.3.9.2 <a href="lib-numerics.html#lib.indirect.array.assign"> [lib.indirect.array.assign]</a> to "This function."</li> +<li> Change the first three words of the second sentence of paragraph 1 of + 26.3.9.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.indirect.array.assign"> [lib.indirect.array.assign]</a> to "These assignment operators have"</li> </ul> -<p><i>[This wording is taken from Robert Klarer's reflector message, -c++std-lib-7827. Gabriel Dos Reis agrees that this general solution -is correct.]</i></p> +<p><i>[Proposed resolution was modified in Santa Cruz: explicitly make +copy constructor and copy assignment operators public, instead of +removing them.]</i></p> <p><b>Rationale:</b></p> <p>Keeping the valarray constructors private is untenable. Merely making valarray a friend of the helper classes isn't good enough, @@ -2252,162 +1784,8 @@ believed we should make the assignment operators public, in addition to the copy constructors, for reasons of symmetry and user expectation.</p> <hr> -<a name="254"><h3>254. Exception types in clause 19 are constructed from <tt>std::string</tt> -</h3></a><p> -<b>Section:</b> 19.1 <a href="lib-diagnostics.html#lib.std.exceptions"> [lib.std.exceptions]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 01 Aug 2000</p> -<p> -Many of the standard exception types which implementations are -required to throw are constructed with a const std::string& -parameter. For example: -</p> - -<pre> - 19.1.5 Class out_of_range [lib.out.of.range] - namespace std { - class out_of_range : public logic_error { - public: - explicit out_of_range(const string& what_arg); - }; - } - - 1 The class out_of_range defines the type of objects thrown as excep- - tions to report an argument value not in its expected range. - - out_of_range(const string& what_arg); - - Effects: - Constructs an object of class out_of_range. - Postcondition: - strcmp(what(), what_arg.c_str()) == 0. -</pre> - -<p> -There are at least two problems with this: -</p> -<ol> -<li>A program which is low on memory may end up throwing -std::bad_alloc instead of out_of_range because memory runs out while -constructing the exception object.</li> -<li>An obvious implementation which stores a std::string data member -may end up invoking terminate() during exception unwinding because the -exception object allocates memory (or rather fails to) as it is being -copied.</li> -</ol> - -<p> -There may be no cure for (1) other than changing the interface to -out_of_range, though one could reasonably argue that (1) is not a -defect. Personally I don't care that much if out-of-memory is reported -when I only have 20 bytes left, in the case when out_of_range would -have been reported. People who use exception-specifications might care -a lot, though. -</p> - -<p> -There is a cure for (2), but it isn't completely obvious. I think a -note for implementors should be made in the standard. Avoiding -possible termination in this case shouldn't be left up to chance. The -cure is to use a reference-counted "string" implementation -in the exception object. I am not necessarily referring to a -std::string here; any simple reference-counting scheme for a NTBS -would do. -</p> - -<p><b>Further discussion, in email:</b></p> - -<p> -...I'm not so concerned about (1). After all, a library implementation -can add const char* constructors as an extension, and users don't -<i>need</i> to avail themselves of the standard exceptions, though this is -a lame position to be forced into. FWIW, std::exception and -std::bad_alloc don't require a temporary basic_string. -</p> - -<p> -...I don't think the fixed-size buffer is a solution to the problem, -strictly speaking, because you can't satisfy the postcondition -<br> - <tt> strcmp(what(), what_arg.c_str()) == 0</tt> -<br> -For all values of what_arg (i.e. very long values). That means that -the only truly conforming solution requires a dynamic allocation. -</p> - -<p><b>Further discussion, from Redmond:</b></p> - -<p>The most important progress we made at the Redmond meeting was -realizing that there are two separable issues here: the const -string& constructor, and the copy constructor. If a user writes -something like <tt>throw std::out_of_range("foo")</tt>, the const -string& constructor is invoked before anything gets thrown. The -copy constructor is potentially invoked during stack unwinding.</p> - -<p>The copy constructor is a more serious problem, becuase failure -during stack unwinding invokes <tt>terminate</tt>. The copy -constructor must be nothrow. <i>Curaçao: Howard thinks this -requirement is already present.</i> -</p> - -<p>The fundamental problem is that it's difficult to get the nothrow -requirement to work well with the requirement that the exception -objects store a string of unbounded size, particularly if you also try -to make the const string& constructor nothrow. Options discussed -include:</p> - -<ul> -<li>Limit the size of a string that exception objects are required to -throw: change the postconditions of 19.1.2 <a href="lib-diagnostics.html#lib.domain.error"> [lib.domain.error]</a> paragraph 3 -and 19.1.6 <a href="lib-diagnostics.html#lib.runtime.error"> [lib.runtime.error]</a> paragraph 3 to something like this: -"strncmp(what(), what_arg._str(), N) == 0, where N is an -implementation defined constant no smaller than 256".</li> -<li>Allow the const string& constructor to throw, but not the -copy constructor. It's the implementor's responsibility to get it -right. (An implementor might use a simple refcount class.)</li> -<li>Compromise between the two: an implementation is not allowed to -throw if the string's length is less than some N, but, if it doesn't -throw, the string must compare equal to the argument.</li> -<li>Add a new constructor that takes a const char*</li> -</ul> - -<p>(Not all of these options are mutually exclusive.)</p> - -<p><b>Proposed resolution:</b></p> -<p>NAD/Future</p> -<p><b>Rationale:</b></p> - -<p>Throwing a bad_alloc while trying to construct a message for another -exception-derived class is not necessarily a bad thing. And the -bad_alloc constructor already has a no throw spec on it (18.4.2.1).</p> - -<p> -The copy constructors of all exception-derived classes already have a -no throw spec. Reference 18.6.1, 19.1 and 15.4/13. -</p> - -<p><b>Future:</b></p> - -<p>All involved would like to see const char* constructors added, but -this should probably be done for C++0X as opposed to a DR.</p> - -<p>I believe the no throw specs currently decorating these functions -could be improved by some kind of static no throw spec checking -mechanism (in a future C++ language). As they stand, the copy -constructors might fail via a call to unexpected. I think what is -intended here is that the copy constructors can't fail.</p> - -<p><i>[Toronto: some LWG members thought this was merely a QoI issue, -but most believed that it was at least a borderline defect. There was -more support for nonnormative advice to implementors than for a -normative change.]</i></p> - -<p><i>[Redmond: discussed, without definite conclusion. Most LWG -members thought there was a real defect lurking here. The above -proposed resolution/rationale is from Howard, Herb, Kevlin, Martin, -and Dave.]</i></p> - -<hr> <a name="258"><h3>258. Missing allocator requirement</h3></a><p> -<b>Section:</b> 20.1.5 <a href="lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 22 Aug 2000</p> +<b>Section:</b> 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 22 Aug 2000</p> <p> From lib-7752: </p> @@ -2431,7 +1809,7 @@ Further discussion: Howard Hinnant writes, in lib-7757: <p> I think I can prove that this is not provable by Table 32. And I agree -it needs to be true except for the "and only if". If x1 != x2, I see no +it needs to be true except for the "and only if". If x1 != x2, I see no reason why it can't be true that Y(x1) == Y(x2). Admittedly I can't think of a practical instance where this would happen, or be valuable. But I also don't see a need to add that extra restriction. I think we @@ -2476,85 +1854,34 @@ the second line from the bottom in table 32 already implies the desired property. This issue should be considered in light of other issues related to allocator instances.]</i></p> <hr> -<a name="278"><h3>278. What does iterator validity mean?</h3></a><p> -<b>Section:</b> 23.2.2.4 <a href="lib-containers.html#lib.list.ops"> [lib.list.ops]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> P.J. Plauger <b>Date:</b> 27 Nov 2000</p> -<p> -Section 23.2.2.4 [lib.list.ops] states that -</p> -<pre> - void splice(iterator position, list<T, Allocator>& x); -</pre> -<p> -<i>invalidates</i> all iterators and references to list <tt>x</tt>. -</p> - -<p> -But what does the C++ Standard mean by "invalidate"? You -can still dereference the iterator to a spliced list element, but -you'd better not use it to delimit a range within the original -list. For the latter operation, it has definitely lost some of its -validity. -</p> - -<p> -If we accept the proposed resolution to issue <a href="lwg-defects.html#250">250</a>, -then we'd better clarify that a "valid" iterator need no -longer designate an element within the same container as it once did. -We then have to clarify what we mean by invalidating a past-the-end -iterator, as when a vector or string grows by reallocation. Clearly, -such an iterator has a different kind of validity. Perhaps we should -introduce separate terms for the two kinds of "validity." -</p> -<p><b>Proposed resolution:</b></p> -<p>Add the following text to the end of section 24.1 <a href="lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a>, -after paragraph 5:</p> -<blockquote> -An <i>invalid</i> iterator is an iterator that may be -singular. [Footnote: This definition applies to pointers, since -pointers are iterators. The effect of dereferencing an iterator that -has been invalidated is undefined.] -</blockquote> - -<p><i>[post-Copenhagen: Matt provided wording.]</i></p> - -<p><i>[Redmond: General agreement with the intent, some objections to -the wording. Dave provided new wording.]</i></p> - -<p><i>[Curaçao: The definition of "singular" is -contentious. The 278 resolution must be made consistent with -issue <a href="lwg-defects.html#208">208</a> and 24.1/5. Furthermore, a Rationale paragraph -is required.]</i></p> - -<hr> <a name="280"><h3>280. Comparison of reverse_iterator to const reverse_iterator</h3></a><p> -<b>Section:</b> 24.4.1 <a href="lib-iterators.html#lib.reverse.iterators"> [lib.reverse.iterators]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Steve Cleary <b>Date:</b> 27 Nov 2000</p> +<b>Section:</b> 24.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.reverse.iterators"> [lib.reverse.iterators]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Steve Cleary <b>Date:</b> 27 Nov 2000</p> <p> This came from an email from Steve Cleary to Fergus in reference to -issue <a href="lwg-active.html#179">179</a>. The library working group briefly discussed +issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#179">179</a>. The library working group briefly discussed this in Toronto and believed it should be a separate issue. There was also some reservations about whether this was a worthwhile problem to fix. </p> <p> -Steve said: "Fixing reverse_iterator. std::reverse_iterator can +Steve said: "Fixing reverse_iterator. std::reverse_iterator can (and should) be changed to preserve these additional -requirements." He also said in email that it can be done without -breaking user's code: "If you take a look at my suggested +requirements." He also said in email that it can be done without +breaking user's code: "If you take a look at my suggested solution, reverse_iterator doesn't have to take two parameters; there is no danger of breaking existing code, except someone taking the address of one of the reverse_iterator global operator functions, and I have to doubt if anyone has ever done that. . . <i>But</i>, just in case they have, you can leave the old global functions in as well -- they won't interfere with the two-template-argument functions. With -that, I don't see how <i>any</i> user code could break." +that, I don't see how <i>any</i> user code could break." </p> <p><b>Proposed resolution:</b></p> <p> -<b>Section:</b> 24.4.1.1 <a href="lib-iterators.html#lib.reverse.iterator"> [lib.reverse.iterator]</a> +<b>Section:</b> 24.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.reverse.iterator"> [lib.reverse.iterator]</a> add/change the following declarations:</p> -<pre> - A) Add a templated assignment operator, after the same manner +<pre> A) Add a templated assignment operator, after the same manner as the templated copy constructor, i.e.: template < class U > @@ -2578,7 +1905,7 @@ add/change the following declarations:</p> </pre> <p> Also make the addition/changes for these signatures in -24.4.1.3 <a href="lib-iterators.html#lib.reverse.iter.ops"> [lib.reverse.iter.ops]</a>. +24.4.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.reverse.iter.ops"> [lib.reverse.iter.ops]</a>. </p> <p><i>[ @@ -2590,314 +1917,163 @@ desirable to provide this feature in a different way. ]</i></p> <hr> -<a name="282"><h3>282. What types does numpunct grouping refer to?</h3></a><p> -<b>Section:</b> 22.2.2.2.2 <a href="lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#Review">Review</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 5 Dec 2000</p> -<p> -Paragraph 16 mistakenly singles out integral types for inserting -thousands_sep() characters. This conflicts with the syntax for floating -point numbers described under 22.2.3.1/2. -</p> -<p><b>Proposed resolution:</b></p> -<p>Change paragraph 16 from:</p> - -<blockquote> -For integral types, punct.thousands_sep() characters are inserted into -the sequence as determined by the value returned by punct.do_grouping() -using the method described in 22.2.3.1.2 <a href="lib-locales.html#lib.facet.numpunct.virtuals"> [lib.facet.numpunct.virtuals]</a>. -</blockquote> - -<p>To:</p> - -<blockquote> -For arithmetic types, punct.thousands_sep() characters are inserted into -the sequence as determined by the value returned by punct.do_grouping() -using the method described in 22.2.3.1.2 <a href="lib-locales.html#lib.facet.numpunct.virtuals"> [lib.facet.numpunct.virtuals]</a>. -</blockquote> - -<p><i>[ -Copenhagen: Opinions were divided about whether this is actually an -inconsistency, but at best it seems to have been unintentional. This -is only an issue for floating-point output: The standard is -unambiguous that implementations must parse thousands_sep characters -when performing floating-point. The standard is also unambiguous that -this requirement does not apply to the "C" locale. -]</i></p> - -<p><i>[ -A survey of existing practice is needed; it is believed that some -implementations do insert thousands_sep characters for floating-point -output and others fail to insert thousands_sep characters for -floating-point input even though this is unambiguously required by the -standard. -]</i></p> - -<p><i>[Post-Curaçao: the above proposed resolution is the consensus of -Howard, Bill, Pete, Benjamin, Nathan, Dietmar, Boris, and Martin.]</i></p> - -<hr> <a name="283"><h3>283. std::replace() requirement incorrect/insufficient</h3></a><p> -<b>Section:</b> 25.2.4 <a href="lib-algorithms.html#lib.alg.replace"> [lib.alg.replace]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 15 Dec 2000</p> +<b>Section:</b> 25.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.replace"> [lib.alg.replace]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 15 Dec 2000</p> <p> -The requirements in 25.2.4 <a href="lib-algorithms.html#lib.alg.replace"> [lib.alg.replace]</a>, p1 that <tt>T</tt> to be -<tt>Assignable</tt> (23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a>) is not necessary or -sufficient for either of the algorithms. The algorithms require that -<tt>std::iterator_traits<ForwardIterator>::value_type</tt> be -<tt>Assignable</tt> and that both -<tt>std::iterator_traits<ForwardIterator>::value_type</tt> and be -<tt>EqualityComparable</tt> (20.1.1 <a href="lib-utilities.html#lib.equalitycomparable"> [lib.equalitycomparable]</a>) with respect to -one another. +(revision of the further discussion) +There are a number of problems with the requires clauses for the +algorithms in 25.1 and 25.2. The requires clause of each algorithm +should describe the necessary and sufficient requirements on the inputs +to the algorithm such that the algorithm compiles and runs properly. +Many of the requires clauses fail to do this. Here is a summary of the kinds +of mistakes: </p> -<p> -<b>Further discussion, from Jeremy</b>: -</p> - -<p>There are a number of problems with the requires clauses for the -algorithms in 25.1 <a href="lib-algorithms.html#lib.alg.nonmodifying"> [lib.alg.nonmodifying]</a> and 25.2 <a href="lib-algorithms.html#lib.alg.modifying.operations"> [lib.alg.modifying.operations]</a>. The requires -clause of each algorithm should describe the necessary and sufficient -requirements on the inputs to the algorithm such that the algorithm -compiles and runs properly. Many of the requires clauses fail to do -this. Here is a summary of the kinds of mistakes:</p> - <ol> -<li> Use of EqualityComparable, which only puts requirements on a single - type, when in fact an equality operator is required between two - different types, typically either T and the iterators value_type - or between the value_type's of two different iterators.</li> - -<li> Use of Assignable for T when in fact what was needed is Assignable - for the value_type of the iterator, and convertability from T to the - value_type of the iterator. Or for output iterators, the requirement - should be that T is writable to the iterator (output iterators do - not have value types; see issue <a href="lwg-active.html#324">324</a>).</li> - -<li> Lack of a requires clause.</li> -</ol> - -<p>Here is the list of algorithms that contain mistakes:</p> -<ul> -<li>25.1.2 <a href="lib-algorithms.html#lib.alg.find"> [lib.alg.find]</a> -</li> -<li>25.1.3 <a href="lib-algorithms.html#lib.alg.find.end"> [lib.alg.find.end]</a> -</li> -<li>25.1.4 <a href="lib-algorithms.html#lib.alg.find.first.of"> [lib.alg.find.first.of]</a> -</li> -<li>25.1.6 <a href="lib-algorithms.html#lib.alg.count"> [lib.alg.count]</a> -</li> -<li>25.1.7 <a href="lib-algorithms.html#lib.mismatch"> [lib.mismatch]</a> -</li> -<li>25.1.8 <a href="lib-algorithms.html#lib.alg.equal"> [lib.alg.equal]</a> -</li> -<li>25.1.9 <a href="lib-algorithms.html#lib.alg.search"> [lib.alg.search]</a> -</li> -<li>25.2.4 <a href="lib-algorithms.html#lib.alg.replace"> [lib.alg.replace]</a> -</li> -<li>25.2.5 <a href="lib-algorithms.html#lib.alg.fill"> [lib.alg.fill]</a> +<li> +Use of EqualityComparable, which only puts requirements on a single +type, when in fact an equality operator is required between two +different types, typically either T and the iterator's value type +or between the value types of two different iterators. </li> -<li>25.2.7 <a href="lib-algorithms.html#lib.alg.remove"> [lib.alg.remove]</a> +<li> +Use of Assignable for T when in fact what was needed is Assignable +for the value_type of the iterator, and convertability from T to the +value_type of the iterator. Or for output iterators, the requirement +should be that T is writable to the iterator (output iterators do +not have value types). </li> -</ul> - -<p>Also, in the requirements for EqualityComparable, the requirement that -the operator be defined for const objects is lacking.</p> -<p><b>Proposed resolution:</b></p> -<p>20.1.1 <a href="lib-utilities.html#lib.equalitycomparable"> [lib.equalitycomparable]</a> Change p1 from</p> - -<blockquote> -In Table 28, T is a type to be supplied by a C++ program instantiating -a template, a, b, and c are values of type T. -</blockquote> - -<p>to</p> - -<blockquote> -In Table 28, T is a type to be supplied by a C++ program instantiating -a template, a, b, and c are values of type const T. -</blockquote> - -<p>25.1.2 <a href="lib-algorithms.html#lib.alg.find"> [lib.alg.find]</a> Change p1 from</p> - -<blockquote> -Requires: Type T is EqualityComparable (20.1.1). -</blockquote> - -<p>to </p> - -<blockquote> -Requires: There must be a equality operator defined that accepts type -std::iterator_traits<InputIterator>::reference for the left operand -and const T for the right operand. -</blockquote> - - -<p>25.1.3 <a href="lib-algorithms.html#lib.alg.find.end"> [lib.alg.find.end]</a> Add the following requires clause</p> - -<blockquote> -Requires: There must be an equality operator defined that accepts -type const std::iterator_traits<ForwardIterator1>::value_type for the -left operand and const -std::iterator_traits<ForwardIterator2>::value_type for the right -operand. -</blockquote> - -<p>25.1.4 <a href="lib-algorithms.html#lib.alg.find.first.of"> [lib.alg.find.first.of]</a> Add the following requires clause</p> +</ol> -<blockquote> -Requires: There must be an equality operator defined that accepts -type const std::iterator_traits<ForwardIterator1>::value_type for the -left operand and const -std::iterator_traits<ForwardIterator2>::value_type for the right -operand. -</blockquote> +<p> +Here is the list of algorithms that contain mistakes: +</p> +<ul> +<li>25.1.2 std::find</li> +<li>25.1.6 std::count</li> +<li>25.1.8 std::equal</li> +<li>25.1.9 std::search, std::search_n</li> +<li>25.2.4 std::replace, std::replace_copy</li> +<li>25.2.5 std::fill</li> +<li>25.2.7 std::remove, std::remove_copy</li> +</ul> -<p>25.1.5 <a href="lib-algorithms.html#lib.alg.adjacent.find"> [lib.alg.adjacent.find]</a> Add the following requires clause</p> +<p> +Also, in the requirements for EqualityComparable, the requirement that +the operator be defined for const objects is lacking. +</p> -<blockquote> -Requires: T must be EqualityComparable (20.1.1). -</blockquote> +<p><b>Proposed resolution:</b></p> -<p>25.1.6 <a href="lib-algorithms.html#lib.alg.count"> [lib.alg.count]</a> Change p1 from</p> +<p>20.1.1 Change p1 from</p> -<blockquote> -Requires: Type T is EqualityComparable (20.1.1). -</blockquote> +<p>In Table 28, <tt>T</tt> is a type to be supplied by a C++ program +instantiating a template, <tt>a</tt>, <tt>b</tt>, and <tt>c</tt> are +values of type <tt>T</tt>. +</p> <p>to</p> -<blockquote> -Requires: There must be a equality operator defined that accepts type -std::iterator_traits<InputIterator>::reference for the left operand -and const T for the right operand. -</blockquote> +<p> +In Table 28, <tt>T</tt> is a type to be supplied by a C++ program +instantiating a template, <tt>a</tt>, <tt>b</tt>, and <tt>c</tt> are +values of type <tt>const T</tt>. +</p> -<p>25.1.7 <a href="lib-algorithms.html#lib.mismatch"> [lib.mismatch]</a> Add the following requires clause</p> +<p>25 Between p8 and p9</p> -<blockquote> -Requires: There must be an equality operator defined that accepts type -std::iterator_traits<InputIterator1>::reference for the left operand -and std::iterator_traits<InputIterator2>::reference for the right operand. -</blockquote> +<p>Add the following sentence:</p> +<p>When the description of an algorithm gives an expression such as +<tt>*first == value</tt> for a condition, it is required that the expression +evaluate to either true or false in boolean contexts.</p> -<p>25.1.8 <a href="lib-algorithms.html#lib.alg.equal"> [lib.alg.equal]</a> Add the following requires clause</p> +<p>25.1.2 Change p1 by deleting the requires clause.</p> -<blockquote> -Requires: There must be an equality operator defined that accepts type -std::iterator_traits<InputIterator1>::reference for the left operand -and std::iterator_traits<InputIterator2>::reference for the right operand. -</blockquote> - -<p>25.1.9 <a href="lib-algorithms.html#lib.alg.search"> [lib.alg.search]</a> Add the following requires clause</p> +<p>25.1.6 Change p1 by deleting the requires clause.</p> -<blockquote> -Requires: There must be an equality operator defined that accepts -type const std::iterator_traits<ForwardIterator1>::value_type for -the left operand and const -std::iterator_traits<ForwardIterator2>::value_type for the right -operand. -</blockquote> +<p>25.1.9</p> -<p>Change change p4 from</p> +<p>Change p4 from</p> -<blockquote> -Requires: Type T is EqualityComparable (20.1.1), type Size is -convertible to integral type (4.7.12.3). -</blockquote> +<p>-4- Requires: Type <tt>T</tt> is <tt>EqualityComparable</tt> +(20.1.1), type Size is convertible to integral type (4.7.12.3). +</p> <p>to</p> -<blockquote> -Requires: There must be an equality operator defined that accepts -const std::iterator_traits<ForwardIterator>::value_type for the left -operand and const T for the right operand. The type Size is convertible to -integral type (4.7.12.3). -</blockquote> +<p>-4- Requires: The type <tt>Size</tt> is convertible to integral +type (4.7.12.3).</p> -<p>25.2.4 <a href="lib-algorithms.html#lib.alg.replace"> [lib.alg.replace]</a> Change p1 from</p> +<p>25.2.4 Change p1 from</p> -<blockquote> -Requires: Type T is Assignable (23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a>) (and, for replace(), -EqualityComparable (20.1.1 <a href="lib-utilities.html#lib.equalitycomparable"> [lib.equalitycomparable]</a>)). -</blockquote> +<p>-1- Requires: Type <tt>T</tt> is <tt>Assignable</tt> (23.1 ) (and, for <tt>replace()</tt>, <tt>EqualityComparable</tt> (20.1.1 )).</p> <p>to</p> -<blockquote> -Requires: Type std::iterator_traits<ForwardIterator>::value_type -is Assignable (23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a>) and the type const T is convertible to -std::iterator_traits<ForwardIterator>::value_type. For replace(), an -equality operator must be defined that accepts type -std::iterator_traits<ForwardIterator>::reference for the left operand -and const T for the right operand. -</blockquote> +<p>-1- Requires: The expression <tt>*first = new_value</tt> must be valid.</p> <p>and change p4 from</p> -<blockquote> -Requires: Type T is Assignable (23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a>) (and, for replace_copy(), -EqualityComparable (20.1.1 <a href="lib-utilities.html#lib.equalitycomparable"> [lib.equalitycomparable]</a>)). The ranges [first, last) and [result, -result + (last - first)) shall not overlap. -</blockquote> +<p>-4- Requires: Type <tt>T</tt> is <tt>Assignable</tt> (23.1) (and, +for <tt>replace_copy()</tt>, <tt>EqualityComparable</tt> +(20.1.1)). The ranges <tt>[first, last)</tt> and <tt>[result, result + +(last - first))</tt> shall not overlap.</p> <p>to</p> -<blockquote> -Requires: Both types const T and -std::iterator_traits<InputIterator>::reference are writable to the -OutputIterator type. For replace_copy() an equality operator must be -defined that accepts type -std::iterator_traits<InputIterator>::reference for the left operand -and const T for the right operand. The ranges [first, last) and [result, -result + (last - first)) shall not overlap. -</blockquote> +<p>-4- Requires: The results of the expressions <tt>*first</tt> and +<tt>new_value</tt> must be writable to the result output iterator. The +ranges <tt>[first, last)</tt> and <tt>[result, result + (last - +first))</tt> shall not overlap.</p> -<p>25.2.5 <a href="lib-algorithms.html#lib.alg.fill"> [lib.alg.fill]</a> Change p1 from</p> -<blockquote> -Requires: Type T is Assignable (23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> ). Size is convertible to an integral - type (3.9.1 <a href="basic.html#basic.fundamental"> [basic.fundamental]</a> ). -</blockquote> +<p>25.2.5 Change p1 from</p> + +<p>-1- Requires: Type <tt>T</tt> is <tt>Assignable</tt> (23.1). The +type <tt>Size</tt> is convertible to an integral type (4.7.12.3).</p> <p>to</p> -<blockquote> -Requires: Type const T is writable to the OutputIterator. Size is -convertible to an integral type (3.9.1 <a href="basic.html#basic.fundamental"> [basic.fundamental]</a> ). -</blockquote> +<p>-1- Requires: The expression <tt>value</tt> must be is writable to +the output iterator. The type <tt>Size</tt> is convertible to an +integral type (4.7.12.3).</p> +<p>25.2.7 Change p1 from</p> -<p>25.2.7 <a href="lib-algorithms.html#lib.alg.remove"> [lib.alg.remove]</a> Change p1 from</p> - -<blockquote> -Requires: Type T is EqualityComparable (20.1.1 <a href="lib-utilities.html#lib.equalitycomparable"> [lib.equalitycomparable]</a>). -</blockquote> +<p>-1- Requires: Type <tt>T</tt> is <tt>EqualityComparable</tt> (20.1.1).</p> <p>to</p> -<blockquote> -Requires: There must be an equality operator defined that accepts -type const std::iterator_traits<ForwardIterator>::value_type for the left -operand and const T for the right operand. The type -std::iterator_traits<ForwardIterator>::value_type must be Assignable -(23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a>). -</blockquote> - -<p><i>[Curaçao: Jeremy reports he has run the changes through his -automated test tools. At the request of the LWG, Jeremy will reword -the PR in terms of valid expressions rather than "equality -operator".]</i></p> +<p> +-1- Requires: The value type of the iterator must be +<tt>Assignable</tt> (23.1). +</p> +<p><b>Rationale:</b></p> +<p> +The general idea of the proposed solution is to remove the faulty +requires clauses and let the returns and effects clauses speak for +themselves. That is, the returns clauses contain expressions that must +be valid, and therefore already imply the correct requirements. In +addition, a sentence is added at the beginning of chapter 25 saying +that expressions given as conditions must evaluate to true or false in +a boolean context. An alternative would be to say that the type of +these condition expressions must be literally bool, but that would be +imposing a greater restriction that what the standard currently says +(which is convertible to bool). +</p> <hr> <a name="290"><h3>290. Requirements to for_each and its function object</h3></a><p> -<b>Section:</b> 25.1.1 <a href="lib-algorithms.html#lib.alg.foreach"> [lib.alg.foreach]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 03 Jan 2001</p> +<b>Section:</b> 25.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.foreach"> [lib.alg.foreach]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 03 Jan 2001</p> <p>The specification of the for_each algorithm does not have a -"Requires" section, which means that there are no +"Requires" section, which means that there are no restrictions imposed on the function object whatsoever. In essence it means that I can provide any function object with arbitrary side effects and I can still expect a predictable result. In particular I can expect that the function object is applied exactly last - first -times, which is promised in the "Complexity" section. +times, which is promised in the "Complexity" section. </p> <p>I don't see how any implementation can give such a guarantee @@ -2916,9 +2092,9 @@ understand that there are restrictions even if the description of the algorithm does not say so. </p> <p><b>Proposed resolution:</b></p> -<p>Add a "Requires" section to section 25.1.1 similar to those +<p>Add a "Requires" section to section 25.1.1 similar to those proposed for transform and the numeric algorithms (see issue -<a href="lwg-defects.html#242">242</a>): +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#242">242</a>): </p> <blockquote> @@ -2935,7 +2111,7 @@ blanket statement in Clause 25, not just a special requirement for <hr> <a name="291"><h3>291. Underspecification of set algorithms</h3></a><p> -<b>Section:</b> 25.3.5 <a href="lib-algorithms.html#lib.alg.set.operations"> [lib.alg.set.operations]</a> <b>Status:</b> <a href="lwg-active.html#Review">Review</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 03 Jan 2001</p> +<b>Section:</b> 25.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.set.operations"> [lib.alg.set.operations]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 03 Jan 2001</p> <p> The standard library contains four algorithms that compute set operations on sorted ranges: <tt>set_union</tt>, <tt>set_intersection</tt>, @@ -2948,7 +2124,7 @@ in the output range are sorted. <p> The ordinary mathematical definitions are generalized so that they apply to ranges containing multiple copies of a given element. Two -elements are considered to be "the same" if, according to an +elements are considered to be "the same" if, according to an ordering relation provided by the user, neither one is less than the other. So, for example, if one input range contains five copies of an element and another contains three, the output range of <tt>set_union</tt> @@ -2959,7 +2135,7 @@ will contain five copies, the output range of </p> <p> -Because two elements can be "the same" for the purposes +Because two elements can be "the same" for the purposes of these set algorithms, without being identical in other respects (consider, for example, strings under case-insensitive comparison), this raises a number of unanswered questions: @@ -2986,7 +2162,7 @@ same way. <p><b>Proposed resolution:</b></p> -<p>Add the following to the end of 25.3.5.2 <a href="lib-algorithms.html#lib.set.union"> [lib.set.union]</a> paragraph 5:</p> +<p>Add the following to the end of 25.3.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.set.union"> [lib.set.union]</a> paragraph 5:</p> <blockquote> If [first1, last1) contains <i>m</i> elements that are equivalent to each other and [first2, last2) contains <i>n</i> elements that are @@ -2996,7 +2172,7 @@ from [first1, last1), and the last max(<i>n-m</i>, 0) of them from [first2, last2), in that order. </blockquote> -<p>Add the following to the end of 25.3.5.3 <a href="lib-algorithms.html#lib.set.intersection"> [lib.set.intersection]</a> paragraph 5:</p> +<p>Add the following to the end of 25.3.5.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.set.intersection"> [lib.set.intersection]</a> paragraph 5:</p> <blockquote> If [first1, last1) contains <i>m</i> elements that are equivalent to each other and [first2, last2) contains <i>n</i> elements that are @@ -3004,7 +2180,7 @@ equivalent to them, the first min(<i>m</i>, <i>n</i>) of those elements from [first1, last1) are copied to the output range. </blockquote> -<p>Add a new paragraph, <b>Notes</b>, after 25.3.5.4 <a href="lib-algorithms.html#lib.set.difference"> [lib.set.difference]</a> +<p>Add a new paragraph, <b>Notes</b>, after 25.3.5.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.set.difference"> [lib.set.difference]</a> paragraph 4:</p> <blockquote> If [first1, last1) contains <i>m</i> elements that are equivalent to each @@ -3013,7 +2189,7 @@ equivalent to them, the last max(<i>m-n</i>, 0) elements from [first1, last1) are copied to the output range. </blockquote> -<p>Add a new paragraph, <b>Notes</b>, after 25.3.5.5 <a href="lib-algorithms.html#lib.set.symmetric.difference"> [lib.set.symmetric.difference]</a> +<p>Add a new paragraph, <b>Notes</b>, after 25.3.5.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.set.symmetric.difference"> [lib.set.symmetric.difference]</a> paragraph 4:</p> <blockquote> If [first1, last1) contains <i>m</i> elements that are equivalent to @@ -3024,21 +2200,26 @@ from [first1, last1) if <i>m</i> > <i>n</i>, and the last <i>n - m</i> of these elements from [first2, last2) if <i>m</i> < <i>n</i>. </blockquote> -<p><i>[Curaçao: Missing Rationale and missing status comments from -Redmond made discussion difficult. For union, doesn't the standard -already say this? Howard, others think maybe so. Several thought the -PR may be "too complicated".]</i></p> +<p><i>[Santa Cruz: it's believed that this language is clearer than + what's in the Standard. However, it's also believed that the + Standard may already make these guarantees (although not quite in + these words). Bill and Howard will check and see whether they think + that some or all of these changes may be redundant. If so, we may + close this issue as NAD.]</i></p> +<p><b>Rationale:</b></p> +<p>For simple cases, these descriptions are equivalent to what's + already in the Standard. For more complicated cases, they describe + the behavior of existing implementations.</p> <hr> <a name="294"><h3>294. User defined macros and standard headers</h3></a><p> -<b>Section:</b> 17.4.3.1.1 <a href="lib-intro.html#lib.macro.names"> [lib.macro.names]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> James Kanze <b>Date:</b> 11 Jan 2001</p> -<p>Paragraph 2 of 17.4.3.1.1 <a href="lib-intro.html#lib.macro.names"> [lib.macro.names]</a> reads: "A +<b>Section:</b> 17.4.3.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.macro.names"> [lib.macro.names]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> James Kanze <b>Date:</b> 11 Jan 2001</p> +<p>Paragraph 2 of 17.4.3.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.macro.names"> [lib.macro.names]</a> reads: "A translation unit that includes a header shall not contain any macros -that define names declared in that header." As I read this, it +that define names declared in that header." As I read this, it would mean that the following program is legal:</p> -<pre> - #define npos 3.14 +<pre> #define npos 3.14 #include <sstream> </pre> @@ -3049,31 +2230,31 @@ which <sstream> didn't include <string>.</p> <p>I think that this phrase was probably formulated before it was decided that a standard header may freely include other standard headers. The phrase would be perfectly appropriate for C, for -example. In light of 17.4.4.1 <a href="lib-intro.html#lib.res.on.headers"> [lib.res.on.headers]</a> paragraph 1, however, +example. In light of 17.4.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.res.on.headers"> [lib.res.on.headers]</a> paragraph 1, however, it isn't stringent enough.</p> <p><b>Proposed resolution:</b></p> -<p>In paragraph 2 of 17.4.3.1.1 <a href="lib-intro.html#lib.macro.names"> [lib.macro.names]</a>, change "A +<p>In paragraph 2 of 17.4.3.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.macro.names"> [lib.macro.names]</a>, change "A translation unit that includes a header shall not contain any macros -that define names declared in that header." to "A +that define names declared in that header." to "A translation unit that includes a header shall not contain any macros -that define names declared in any standard header."</p> +that define names declared in any standard header."</p> <p><i>[Copenhagen: the general idea is clearly correct, but there is -concern about making sure that the two paragraphs in 17.4.3.1.1 <a href="lib-intro.html#lib.macro.names"> [lib.macro.names]</a> remain consistent. Nathan will provide new +concern about making sure that the two paragraphs in 17.4.3.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.macro.names"> [lib.macro.names]</a> remain consistent. Nathan will provide new wording.]</i></p> <hr> <a name="299"><h3>299. Incorrect return types for iterator dereference</h3></a><p> -<b>Section:</b> 24.1.4 <a href="lib-iterators.html#lib.bidirectional.iterators"> [lib.bidirectional.iterators]</a>, 24.1.5 <a href="lib-iterators.html#lib.random.access.iterators"> [lib.random.access.iterators]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> John Potter <b>Date:</b> 22 Jan 2001</p> +<b>Section:</b> 24.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.bidirectional.iterators"> [lib.bidirectional.iterators]</a>, 24.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.random.access.iterators"> [lib.random.access.iterators]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> John Potter <b>Date:</b> 22 Jan 2001</p> <p> -In section 24.1.4 <a href="lib-iterators.html#lib.bidirectional.iterators"> [lib.bidirectional.iterators]</a>, +In section 24.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.bidirectional.iterators"> [lib.bidirectional.iterators]</a>, Table 75 gives the return type of *r-- as convertible to T. This is not consistent with Table 74 which gives the return type of *r++ as T&. *r++ = t is valid while *r-- = t is invalid. </p> <p> -In section 24.1.5 <a href="lib-iterators.html#lib.random.access.iterators"> [lib.random.access.iterators]</a>, +In section 24.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.random.access.iterators"> [lib.random.access.iterators]</a>, Table 76 gives the return type of a[n] as convertible to T. This is not consistent with the semantics of *(a + n) which returns T& by Table 74. *(a + n) = t is valid while a[n] = t is invalid. @@ -3084,8 +2265,8 @@ Discussion from the Copenhagen meeting: the first part is uncontroversial. The second part, operator[] for Random Access Iterators, requires more thought. There are reasonable arguments on both sides. Return by value from operator[] enables some potentially -useful iterators, e.g. a random access "iota iterator" (a.k.a -"counting iterator" or "int iterator"). There isn't any obvious way +useful iterators, e.g. a random access "iota iterator" (a.k.a +"counting iterator" or "int iterator"). There isn't any obvious way to do this with return-by-reference, since the reference would be to a temporary. On the other hand, <tt>reverse_iterator</tt> takes an arbitrary Random Access Iterator as template argument, and its @@ -3101,7 +2282,7 @@ Random Access Iterator requirements has been present from an early stage. In both the STL proposal adopted by the committee (N0527==94-0140) and the STL technical report (HPL-95-11 (R.1), by Stepanov and Lee), the Random Access Iterator requirements say that -operator[]'s return value is "convertible to T". In N0527 +operator[]'s return value is "convertible to T". In N0527 reverse_iterator's operator[] returns by value, but in HPL-95-11 (R.1), and in the STL implementation that HP released to the public, reverse_iterator's operator[] returns by reference. In 1995, the @@ -3112,226 +2293,64 @@ original intent for operator[] is unclear. <p> In the long term it may be desirable to add more fine-grained iterator requirements, so that access method and traversal strategy -can be decoupled. (See "Improved Iterator Categories and -Requirements", N1297 = 01-0011, by Jeremy Siek.) Any decisions +can be decoupled. (See "Improved Iterator Categories and +Requirements", N1297 = 01-0011, by Jeremy Siek.) Any decisions about issue 299 should keep this possibility in mind. </p> -<p><b>Proposed resolution:</b></p> -<p>In section 24.1.4 <a href="lib-iterators.html#lib.bidirectional.iterators"> [lib.bidirectional.iterators]</a>, change the return type in table -75 from "convertible to T" to T&.</p> - -<p>In section 24.1.5 <a href="lib-iterators.html#lib.random.access.iterators"> [lib.random.access.iterators]</a>, change the return type in table -76 from "convertible to T" to T&.</p> - -<p><i>[Curaçao: Jeremy volunteered to work on this issue.]</i></p> - -<hr> -<a name="300"><h3>300. list::merge() specification incomplete</h3></a><p> -<b>Section:</b> 23.2.2.4 <a href="lib-containers.html#lib.list.ops"> [lib.list.ops]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> John Pedretti <b>Date:</b> 23 Jan 2001</p> -<p> -The "Effects" clause for list::merge() (23.2.2.4, p23) -appears to be incomplete: it doesn't cover the case where the argument -list is identical to *this (i.e., this == &x). The requirement in the -note in p24 (below) is that x be empty after the merge which is surely -unintended in this case. -</p> -<p><b>Proposed resolution:</b></p> -<p>In 23.2.2.4 <a href="lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, replace paragraps 23-25 with:</p> -<blockquote> -<p> -23 Effects: if (&x == this) does nothing; otherwise, merges the two -sorted ranges [begin(), end()) and [x.begin(), x.end()). The result -is a range in which the elements will be sorted in non-decreasing -order according to the ordering defined by comp; that is, for every -iterator i in the range other than the first, the condition comp(*i, -*(i - 1)) will be false. -</p> - -<p> -24 Notes: Stable: if (&x != this), then for equivalent elements in the -two original ranges, the elements from the original range [begin(), -end()) always precede the elements from the original range [x.begin(), -x.end()). If (&x != this) the range [x.begin(), x.end()) is empty -after the merge. -</p> - -<p> -25 Complexity: At most size() + x.size() - 1 applications of comp if -(&x ! = this); otherwise, no applications of comp are performed. If -an exception is thrown other than by a comparison there are no -effects. -</p> - -</blockquote> - -<p><i>[Copenhagen: The original proposed resolution did not fix all of -the problems in 23.2.2.4 <a href="lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, p22-25. Three different -paragraphs (23, 24, 25) describe the effects of <tt>merge</tt>. -Changing p23, without changing the other two, appears to introduce -contradictions. Additionally, "merges the argument list into the -list" is excessively vague.]</i></p> - -<p><i>[Post-Curaçao: Robert Klarer provided new wording.]</i></p> - -<hr> -<a name="304"><h3>304. Must <tt>*a</tt> return an lvalue when <tt>a</tt> is an input iterator?</h3></a><p> -<b>Section:</b> 24.1 <a href="lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 5 Feb 2001</p> -<p> -We all "know" that input iterators are allowed to produce -values when dereferenced of which there is no other in-memory copy. +<p>Further discussion: I propose a compromise between John Potter's +resolution, which requires <tt>T&</tt> as the return type of +<tt>a[n]</tt>, and the current wording, which requires convertible to +<tt>T</tt>. The compromise is to keep the convertible to <tt>T</tt> +for the return type of the expression <tt>a[n]</tt>, but to also add +<tt>a[n] = t</tt> as a valid expression. This compromise "saves" the +common case uses of random access iterators, while at the same time +allowing iterators such as counting iterator and caching file +iterators to remain random access iterators (iterators where the +lifetime of the object returned by <tt>operator*()</tt> is tied to the +lifetime of the iterator). </p> <p> -But: Table 72, with a careful reading, seems to imply that this can only be -the case if the value_type has no members (e.g. is a built-in type). +Note that the compromise resolution necessitates a change to +<tt>reverse_iterator</tt>. It would need to use a proxy to support +<tt>a[n] = t</tt>. </p> -<p>The problem occurs in the following entry:</p> - -<pre> - a->m pre: (*a).m is well-defined - Equivalent to (*a).m -</pre> - <p> -<tt>*a.m</tt> can be well-defined if <tt>*a</tt> is not a reference -type, but since <tt>operator->()</tt> must return a pointer for -<tt>a->m</tt> to be well-formed, it needs something to return a -pointer <i>to</i>. This seems to indicate that <tt>*a</tt> must be -buffered somewhere to make a legal input iterator. +Note also there is one kind of mutable random access iterator that +will no longer meet the new requirements. Currently, iterators that +return an r-value from <tt>operator[]</tt> meet the requirements for a +mutable random access iterartor, even though the expression <tt>a[n] = +t</tt> will only modify a temporary that goes away. With this proposed +resolution, <tt>a[n] = t</tt> will be required to have the same +operational semantics as <tt>*(a + n) = t</tt>. </p> -<p>I don't think this was intentional.</p> <p><b>Proposed resolution:</b></p> -<p><i>[Copenhagen: the two obvious possibilities are to keep the -<tt>operator-></tt> requirement for Input Iterators, and put -in a non-normative note describing how it can be implemented with -proxies, or else moving the <tt>operator-></tt> requirement -from Input Iterator to Forward Iterator. If we do the former -we'll also have to change <tt>istreambuf_iterator</tt>, because -it has no <tt>operator-></tt>. A straw poll showed roughly equal -support for the two options.]</i></p> -<hr> -<a name="305"><h3>305. Default behavior of codecvt<wchar_t, char, mbstate_t>::length()</h3></a><p> -<b>Section:</b> 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 24 Jan 2001</p> -<p>22.2.1.5/3 introduces codecvt in part with:</p> - -<blockquote> - codecvt<wchar_t,char,mbstate_t> converts between the native - character sets for tiny and wide characters. Instantiations on - mbstate_t perform conversion between encodings known to the library - implementor. -</blockquote> - -<p>But 22.2.1.5.2/10 describes do_length in part with:</p> - -<blockquote> - ... codecvt<wchar_t, char, mbstate_t> ... return(s) the lesser of max and - (from_end-from). -</blockquote> <p> -The semantics of do_in and do_length are linked. What one does must -be consistent with what the other does. 22.2.1.5/3 leads me to -believe that the vendor is allowed to choose the algorithm that -codecvt<wchar_t,char,mbstate_t>::do_in performs so that it makes -his customers happy on a given platform. But 22.2.1.5.2/10 explicitly -says what codecvt<wchar_t,char,mbstate_t>::do_length must -return. And thus indirectly specifies the algorithm that -codecvt<wchar_t,char,mbstate_t>::do_in must perform. I believe -that this is not what was intended and is a defect. +In section 24.1.4 [lib.bidirectdional.iterators], change the return +type in table 75 from "convertible to <tt>T</tt>" to +<tt>T&</tt>. </p> -<p>Discussion from the -lib reflector: - -<br>This proposal would have the effect of making the semantics of -all of the virtual functions in <tt>codecvt<wchar_t, char, -mbstate_t></tt> implementation specified. Is that what we want, or -do we want to mandate specific behavior for the base class virtuals -and leave the implementation specified behavior for the codecvt_byname -derived class? The tradeoff is that former allows implementors to -write a base class that actually does something useful, while the -latter gives users a way to get known and specified---albeit -useless---behavior, and is consistent with the way the standard -handles other facets. It is not clear what the original intention -was.</p> - -<p> -Nathan has suggest a compromise: a character that is a widened version -of the characters in the basic execution character set must be -converted to a one-byte sequence, but there is no such requirement -for characters that are not part of the basic execution character set. -</p> -<p><b>Proposed resolution:</b></p> -<p> -Change 22.2.1.5.2/5 from: -</p> <p> -The instantiations required in Table 51 (lib.locale.category), namely -codecvt<wchar_t,char,mbstate_t> and -codecvt<char,char,mbstate_t>, store no characters. Stores no more -than (to_limit-to) destination elements. It always leaves the to_next -pointer pointing one beyond the last element successfully stored. +In section 24.1.5 [lib.random.access.iterators], change the +operational semantics for <tt>a[n]</tt> to " the r-value of +<tt>a[n]</tt> is equivalent to the r-value of <tt>*(a + +n)</tt>". Add a new row in the table for the expression <tt>a[n] = t</tt> +with a return type of convertible to <tt>T</tt> and operational semantics of +<tt>*(a + n) = t</tt>. </p> -<p> -to: -</p> -<p> -Stores no more than (to_limit-to) destination elements, and leaves the -to_next pointer pointing one beyond the last element successfully -stored. codecvt<char,char,mbstate_t> stores no characters. -</p> - -<p>Change 22.2.1.5.2/10 from:</p> - -<blockquote> --10- Returns: (from_next-from) where from_next is the largest value in -the range [from,from_end] such that the sequence of values in the -range [from,from_next) represents max or fewer valid complete -characters of type internT. The instantiations required in Table 51 -(21.1.1.1.1), namely codecvt<wchar_t, char, mbstate_t> and -codecvt<char, char, mbstate_t>, return the lesser of max and -(from_end-from). -</blockquote> - -<p>to:</p> - -<blockquote> --10- Returns: (from_next-from) where from_next is the largest value in -the range [from,from_end] such that the sequence of values in the range -[from,from_next) represents max or fewer valid complete characters of -type internT. The instantiation codecvt<char, char, mbstate_t> returns -the lesser of max and (from_end-from). -</blockquote> - -<p><i>[Redmond: Nathan suggested an alternative resolution: same as -above, but require that, in the default encoding, a character from the -basic execution character set would map to a single external -character. The straw poll was 8-1 in favor of the proposed -resolution.]</i></p> - -<p><b>Rationale:</b></p> -<p>The default encoding should be whatever users of a given platform -would expect to be the most natural. This varies from platform to -platform. In many cases there is a preexisting C library, and users -would expect the default encoding to be whatever C uses in the default -"C" locale. We could impose a guarantee like the one Nathan suggested -(a character from the basic execution character set must map to a -single external character), but this would rule out important -encodings that are in common use: it would rule out JIS, for -example, and it would rule out a fixed-width encoding of UCS-4.</p> - -<p><i>[Curaçao: fixed rationale typo at the request of Ichiro Koshida; -"shift-JIS" changed to "JIS".]</i></p> <hr> <a name="309"><h3>309. Does sentry catch exceptions?</h3></a><p> -<b>Section:</b> 27.6 <a href="lib-iostreams.html#lib.iostream.format"> [lib.iostream.format]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 19 Mar 2001</p> +<b>Section:</b> 27.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostream.format"> [lib.iostream.format]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 19 Mar 2001</p> <p> The descriptions of the constructors of basic_istream<>::sentry -(27.6.1.1.2 <a href="lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a>) and basic_ostream<>::sentry -(27.6.2.3 <a href="lib-iostreams.html#lib.ostream::sentry"> [lib.ostream::sentry]</a>) do not explain what the functions do in +(27.6.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a>) and basic_ostream<>::sentry +(27.6.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream::sentry"> [lib.ostream::sentry]</a>) do not explain what the functions do in case an exception is thrown while they execute. Some current implementations allow all exceptions to propagate, others catch them and set ios_base::badbit instead, still others catch some but let @@ -3342,16 +2361,16 @@ others propagate. The text also mentions that the functions may call setstate(failbit) (without actually saying on what object, but presumably the stream argument is meant). That may have been fine for -basic_istream<>::sentry prior to issue <a href="lwg-defects.html#195">195</a>, since +basic_istream<>::sentry prior to issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#195">195</a>, since the function performs an input operation which may fail. However, -issue <a href="lwg-defects.html#195">195</a> amends 27.6.1.1.2 <a href="lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a>, p2 to +issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#195">195</a> amends 27.6.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a>, p2 to clarify that the function should actually call setstate(failbit | eofbit), so the sentence in p3 is redundant or even somewhat contradictory. </p> <p> -The same sentence that appears in 27.6.2.3 <a href="lib-iostreams.html#lib.ostream::sentry"> [lib.ostream::sentry]</a>, p3 +The same sentence that appears in 27.6.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream::sentry"> [lib.ostream::sentry]</a>, p3 doesn't seem to be very meaningful for basic_istream<>::sentry which performs no input. It is actually rather misleading since it would appear to guide library implementers to calling @@ -3359,894 +2378,220 @@ setstate(failbit) when os.tie()->flush(), the only called function, throws an exception (typically, it's badbit that's set in response to such an event). </p> -<p><b>Proposed resolution:</b></p> -<p>Add the following paragraph immediately after -27.6.1.1.2 <a href="lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a>, p5</p> - -<blockquote> - <p> - If an exception is thrown during the preparation then ios::badbit - is turned on* in is's error state. - </p> - - <p> - [Footnote: This is done without causing an ios::failure to be thrown. - --- end footnote] - </p> - - <p> - If (is.exceptions() & ios_base::badbit)!= 0 then the exception is - rethrown. - </p> -</blockquote> - -<p>And strike the following sentence from 27.6.1.1.2 <a href="lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a>, p5</p> - -<blockquote> - During preparation, the constructor may call setstate(failbit) - (which may throw ios_base::failure (lib.iostate.flags)) -</blockquote> - -<p>Add the following paragraph immediately after -27.6.2.3 <a href="lib-iostreams.html#lib.ostream::sentry"> [lib.ostream::sentry]</a>, p3</p> - -<blockquote> - <p> - If an exception is thrown during the preparation then ios::badbit - is turned on* in os's error state. - </p> - - <p> - [Footnote: This is done without causing an ios::failure to be - thrown. --- end footnote] - </p> - - <p> - If (os.exceptions() & ios_base::badbit)!= 0 then the exception - is rethrown. - </p> -</blockquote> - -<p>And strike the following sentence from 27.6.2.3 <a href="lib-iostreams.html#lib.ostream::sentry"> [lib.ostream::sentry]</a>, p3</p> - -<blockquote> - During preparation, the constructor may call setstate(failbit) - (which may throw ios_base::failure (lib.iostate.flags)) -</blockquote> -<p>(Note that the removal of the two sentences means that the ctors -will not be able to report the failure of any implementation-dependent -operations referred to in footnotes 280 and 293, unless such -operations throw an exception.)</p> - -<p><i>[ -Copenhagen: It was agreed that there was an issue here, but there was -disagreement about the resolution. Some LWG members argued that a -sentry's constructor should not catch exceptions, because sentries -should only be used within (un)formatted input functions and that -exception handling is the responsibility of those functions, not of -the sentries. -]</i></p> - -<hr> -<a name="320"><h3>320. list::assign overspecified</h3></a><p> -<b>Section:</b> 23.2.2.1 <a href="lib-containers.html#lib.list.cons"> [lib.list.cons]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 17 May 2001</p> <p> -Section 23.2.2.1, paragraphs 6-8 specify that list assign (both forms) have -the "effects" of a call to erase followed by a call to insert. -</p> +<b>Additional comments from Martin, who isn't comfortable with the + current proposed resolution</b> (see c++std-lib-11530)</p> <p> -I would like to document that implementers have the freedom to implement -assign by other methods, as long as the end result is the same and the -exception guarantee is as good or better than the basic guarantee. +The istream::sentry ctor says nothing about how the function +deals with exemptions (27.6.1.1.2, p1 says that the class is +responsible for doing "exception safe"(*) prefix and suffix +operations but it doesn't explain what level of exception +safety the class promises to provide). The mockup example +of a "typical implementation of the sentry ctor" given in +27.6.1.1.2, p6, removed in ISO/IEC 14882:2003, doesn't show +exception handling, either. Since the ctor is not classified +as a formatted or unformatted input function, the text in +27.6.1.1, p1 through p4 does not apply. All this would seem +to suggest that the sentry ctor should not catch or in any +way handle exceptions thrown from any functions it may call. +Thus, the typical implementation of an istream extractor may +look something like [1]. </p> <p> -The motivation for this is to use T's assignment operator to recycle -existing nodes in the list instead of erasing them and reallocating -them with new values. It is also worth noting that, with careful -coding, most common cases of assign (everything but assignment with -true input iterators) can elevate the exception safety to strong if -T's assignment has a nothrow guarantee (with no extra memory cost). -Metrowerks does this. However I do not propose that this subtlety be -standardized. It is a QoI issue. </p> - -<p>Existing practise: -Metrowerks and SGI recycle nodes, Dinkumware and Rogue Wave don't. +The problem with [1] is that while it correctly sets ios::badbit +if an exception is thrown from one of the functions called from +the sentry ctor, if the sentry ctor reaches EOF while extracting +whitespace from a stream that has eofbit or failbit set in +exceptions(), it will cause an ios::failure to be thrown, which +will in turn cause the extractor to set ios::badbit. </p> -<p><b>Proposed resolution:</b></p> -<p>Change 23.2.2.1/7 from:</p> - -<blockquote> -<p>Effects:</p> - -<pre> - erase(begin(), end()); - insert(begin(), first, last); -</pre> -</blockquote> - -<p>to:</p> - -<blockquote> -<p>Effects: Replaces the contents of the list with the range [first, last).</p> -</blockquote> - -<p>In 23.1.1 <a href="lib-containers.html#lib.sequence.reqmts"> [lib.sequence.reqmts]</a>, in Table 67 (sequence requirements), -add two new rows:</p> -<pre> - a.assign(i,j) void pre: i,j are not iterators into a. - Replaces elements in a with a copy - of [i, j). - - a.assign(n,t) void pre: t is not a reference into a. - Replaces elements in a with n copies - of t. -</pre> - -<p>Change 23.2.2.1/8 from:</p> - -<blockquote> -<p>Effects:</p> -<pre> - erase(begin(), end()); - insert(begin(), n, t); -</pre> -</blockquote> -<p>to:</p> - -<blockquote> -<p>Effects: Replaces the contents of the list with n copies of t.</p> -</blockquote> - -<p><i>[Redmond: Proposed resolution was changed slightly. Previous -version made explicit statement about exception safety, which wasn't -consistent with the way exception safety is expressed elsewhere. -Also, the change in the sequence requirements is new. Without that -change, the proposed resolution would have required that assignment of -a subrange would have to work. That too would have been -overspecification; it would effectively mandate that assignment use a -temporary. Howard provided wording. -]</i></p> - -<p><i>[Curaçao: Made editorial improvement in wording; changed -"Replaces elements in a with copies of elements in [i, j)." -with "Replaces the elements of a with a copy of [i, j)." -Changes not deemed serious enough to requre rereview.]</i></p> - -<hr> -<a name="323"><h3>323. abs() overloads in different headers</h3></a><p> -<b>Section:</b> 26.5 <a href="lib-numerics.html#lib.c.math"> [lib.c.math]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 4 June 2001</p> -<p>Currently the standard mandates the following overloads of -abs():</p> - -<pre> - abs(long), abs(int) in <cstdlib> - - abs(float), abs(double), abs(long double) in <cmath> - - template<class T> T abs(const complex<T>&) in <complex> - - template<class T> valarray<T> abs(const valarray<T>&); in <valarray> -</pre> <p> -The problem is that having only some overloads visible of a function -that works on "implicitly inter-convertible" types is dangerous in -practice. The headers that get included at any point in a translation -unit can change unpredictably during program -development/maintenance. The wrong overload might be unintentionally -selected. +The only straightforward way to prevent this behavior is to +move the definition of the sentry object in the extractor +above the try block (as suggested by the example in 22.2.8, +p9 and also indirectly supported by 27.6.1.3, p1). See [2]. +But such an implementation will allow exceptions thrown from +functions called from the ctor to freely propagate to the +caller regardless of the setting of ios::badbit in the stream +object's exceptions(). </p> <p> -Currently, there is nothing that mandates the simultaneous visibility -of these overloads. Indeed, some vendors have begun fastidiously -reducing dependencies among their (public) headers as a QOI issue: it -helps people to write portable code by refusing to compile unless all -the correct headers are #included. -</p> - -<p>The same issue may exist for other functions in the library.</p> - -<p>Redmond: PJP reports that C99 adds two new kinds of abs: comples, -and int_max_abs.</p> - -<p>Related issue: <a href="lwg-closed.html#343">343</a>.</p> - -<p><b>Proposed resolution:</b></p> - -<p><i>[Redmond: General agreement that the current situation is -somewhat fragile. No consensus on whether it's more fragile than any -number of other things, or whether there's any good way to fix it. -Walter suggests that <tt>abs</tt> should be defined for all built-in -types in both <cmath> and <cstdlib>, but that no effort -should be made to put all overloads for class types in one place. -Beman suggests closing this issue as "NAD Future", and adding a -<all> header as an extension. The <all> header would -solve a more general problem: users who can't remember which names are -defined in which headers. (See issue <a href="lwg-closed.html#343">343</a>)]</i></p> - -<hr> -<a name="324"><h3>324. Do output iterators have value types?</h3></a><p> -<b>Section:</b> 24.1.2 <a href="lib-iterators.html#lib.output.iterators"> [lib.output.iterators]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 7 June 2001</p> - -<p>Table 73 suggests that output iterators have value types. It -requires the expression "*a = t". Additionally, although Table 73 -never lists "a = t" or "X(a) = t" in the "expressions" column, it -contains a note saying that "a = t" and "X(a) = t" have equivalent -(but nowhere specified!) semantics.</p> - -<p>According to 24.1/9, t is supposed to be "a value of value type -T":</p> - - <blockquote> - In the following sections, a and b denote values of X, n denotes a - value of the difference type Distance, u, tmp, and m denote - identifiers, r denotes a value of X&, t denotes a value of - value type T. - </blockquote> - -<p>Two other parts of the standard that are relevant to whether -output iterators have value types:</p> - -<ul> - <li>24.1/1 says "All iterators i support the expression *i, - resulting in a value of some class, enumeration, or built-in type - T, called the value type of the iterator".</li> - - <li> - 24.3.1/1, which says "In the case of an output iterator, the types - iterator_traits<Iterator>::difference_type - iterator_traits<Iterator>::value_type are both defined as void." - </li> -</ul> - -<p>The first of these passages suggests that "*i" is supposed to -return a useful value, which contradicts the note in 24.1.2/2 saying -that the only valid use of "*i" for output iterators is in an -expression of the form "*i = t". The second of these passages appears -to contradict Table 73, because it suggests that "*i"'s return value -should be void. The second passage is also broken in the case of a an -iterator type, like non-const pointers, that satisfies both the output -iterator requirements and the forward iterator requirements.</p> - -<p>What should the standard say about <tt>*i</tt>'s return value when -i is an output iterator, and what should it say about that t is in the -expression "*i = t"? Finally, should the standard say anything about -output iterators' pointer and reference types?</p> - -<p><b>Proposed resolution:</b></p> -<p>24.1 p1, change</p> - -<blockquote> -<p>All iterators <tt>i</tt> support the expression <tt>*i</tt>, resulting -in a value of some class, enumeration, or built-in type <tt>T</tt>, -called the value type of the iterator.</p> -</blockquote> - -<p>to</p> - -<blockquote> -<p>All input iterators <tt>i</tt> support the expression <tt>*i</tt>, -resulting in a value of some class, enumeration, or built-in type -<tt>T</tt>, called the value type of the iterator. All output -iterators support the expression <tt>*i = o</tt> where <tt>o</tt> is a -value of some type that is in the set of types that are <i>writable</i> to -the particular iterator type of <tt>i</tt>. +So since neither [1] nor [2] behaves as expected, the only +possible solution is to have the sentry ctor catch exceptions +thrown from called functions, set badbit, and propagate those +exceptions if badbit is also set in exceptions(). (Another +solution exists that deals with both kinds of sentries, but +the code is non-obvious and cumbersome -- see [3].) </p> -</blockquote> - -<p>24.1 p9, add</p> -<blockquote> <p> -<tt>o</tt> denotes a value of some type that is writable to the -output iterator. +Please note that, as the issue points out, current libraries +do not behave consistently, suggesting that implementors are +not quite clear on the exception handling in istream::sentry, +despite the fact that some LWG members might feel otherwise. +(As documented by the parenthetical comment here: +http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/2003/n1480.html#309) </p> -</blockquote> - -<p>Table 73, change</p> - -<blockquote> -<pre> -*a = t -</pre> -</blockquote> - -<p>to</p> - -<blockquote> -<pre> -*r = o -</pre> -</blockquote> - -<p>and change</p> - -<blockquote> -<pre> -*r++ = t -</pre> -</blockquote> - -<p>to</p> - -<blockquote> -<pre> -*r++ = o -</pre> -</blockquote> - -<p><i>[post-Redmond: Jeremy provided wording]</i></p> - -<p><b>Rationale:</b></p> -<p>The LWG considered two options: change all of the language that -seems to imply that output iterators have value types, thus making it -clear that output iterators have no value types, or else define value -types for output iterator consistently. The LWG chose the former -option, because it seems clear that output iterators were never -intended to have value types. This was a deliberate design decision, -and any language suggesting otherwise is simply a mistake.</p> - -<p>A future revision of the standard may wish to revisit this design -decision.</p> -<hr> -<a name="325"><h3>325. Misleading text in moneypunct<>::do_grouping</h3></a><p> -<b>Section:</b> 22.2.6.3.2 <a href="lib-locales.html#lib.locale.moneypunct.virtuals"> [lib.locale.moneypunct.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Jul 2001</p> -<p>The Returns clause in 22.2.6.3.2, p3 says about -moneypunct<charT>::do_grouping() -</p> - -<blockquote> - Returns: A pattern defined identically as the result of - numpunct<charT>::do_grouping().241) -</blockquote> - -<p>Footnote 241 then reads</p> - -<blockquote> - This is most commonly the value "\003" (not "3"). -</blockquote> <p> -The returns clause seems to imply that the two member functions must -return an identical value which in reality may or may not be true, -since the facets are usually implemented in terms of struct std::lconv -and return the value of the grouping and mon_grouping, respectively. -The footnote also implies that the member function of the moneypunct -facet (rather than the overridden virtual functions in moneypunct_byname) -most commonly return "\003", which contradicts the C standard which -specifies the value of "" for the (most common) C locale. +Also please note that those LWG members who in Copenhagen +felt that "a sentry's constructor should not catch exceptions, +because sentries should only be used within (un)formatted input +functions and that exception handling is the responsibility of +those functions, not of the sentries," as noted here +http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/papers/2001/n1310.html#309 +would in effect be either arguing for the behavior described +in [1] or for extractors implemented along the lines of [3]. </p> -<p><b>Proposed resolution:</b></p> -<p>Replace the text in Returns clause in 22.2.6.3.2, p3 with the following:</p> - -<blockquote> - Returns: A pattern defined identically as, but not necessarily - equal to, the result of numpunct<charT>::do_grouping().241) -</blockquote> - -<p>and replace the text in Footnote 241 with the following:</p> - -<blockquote> - To specify grouping by 3s the value is "\003", not "3". -</blockquote> -<p><b>Rationale:</b></p> <p> -The fundamental problem is that the description of the locale facet -virtuals serves two purposes: describing the behavior of the base -class, and describing the meaning of and constraints on the behavior -in arbitrary derived classes. The new wording makes that separation a -little bit clearer. The footnote (which is nonnormative) is not -supposed to say what the grouping is in the "C" locale or in any other -locale. It is just a reminder that the values are interpreted as small -integers, not ASCII characters. -</p> -<hr> -<a name="329"><h3>329. vector capacity, reserve and reallocation</h3></a><p> -<b>Section:</b> 23.2.4.2 <a href="lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a>, 23.2.4.3 <a href="lib-containers.html#lib.vector.modifiers"> [lib.vector.modifiers]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Anthony Williams <b>Date:</b> 13 Jul 2001</p> -<p> -There is an apparent contradiction about which circumstances can cause -a reallocation of a vector in Section 23.2.4.2 <a href="lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a> and -section 23.2.4.3 <a href="lib-containers.html#lib.vector.modifiers"> [lib.vector.modifiers]</a>. +The original proposed resolution (Revision 25 of the issues +list) clarifies the role of the sentry ctor WRT exception +handling by making it clear that extractors (both library +or user-defined) should be implemented along the lines of +[2] (as opposed to [1]) and that no exception thrown from +the callees should propagate out of either function unless +badbit is also set in exceptions(). </p> -<p>23.2.4.2p5 says:</p> -<blockquote> -Notes: Reallocation invalidates all the references, pointers, and iterators -referring to the elements in the sequence. It is guaranteed that no -reallocation takes place during insertions that happen after a call to -reserve() until the time when an insertion would make the size of the vector -greater than the size specified in the most recent call to reserve(). -</blockquote> - -<p>Which implies if I do</p> - -<pre> - std::vector<int> vec; - vec.reserve(23); - vec.reserve(0); - vec.insert(vec.end(),1); -</pre> - -<p>then the implementation may reallocate the vector for the insert, -as the size specified in the previous call to reserve was zero.</p> -<p>However, the previous paragraphs (23.2.4.2, p1-2) state:</p> -<blockquote> -<p> -(capacity) Returns: The total number of elements the vector -can hold without requiring reallocation -</p> -<p> -...After reserve(), capacity() is greater or equal to the -argument of reserve if reallocation happens; and equal to the previous value -of capacity() otherwise... -</p> -</blockquote> +<p>[1] Extractor that catches exceptions thrown from sentry:</p> -<p> -This implies that vec.capacity() is still 23, and so the insert() -should not require a reallocation, as vec.size() is 0. This is backed -up by 23.2.4.3p1: -</p> <blockquote> -(insert) Notes: Causes reallocation if the new size is greater than the old -capacity. -</blockquote> +<pre>struct S { long i; }; -<p> -Though this doesn't rule out reallocation if the new size is less -than the old capacity, I think the intent is clear. -</p> - -<p><b>Proposed resolution:</b></p> -<p>Change the wording of 23.2.4.2 <a href="lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a> paragraph 5 to:</p> - -<blockquote> -Notes: Reallocation invalidates all the references, pointers, and -iterators referring to the elements in the sequence. It is guaranteed -that no reallocation takes place during insertions that happen after a -call to reserve() until the time when an insertion would make the size -of the vector greater than the value of capacity(). -</blockquote> - -<p><i>[Redmond: original proposed resolution was modified slightly. In -the original, the guarantee was that there would be no reallocation -until the size would be greater than the value of capacity() after the -most recent call to reserve(). The LWG did not believe that the -"after the most recent call to reserve()" added any useful -information.]</i></p> - -<p><b>Rationale:</b></p> -<p>There was general agreement that, when reserve() is called twice in -succession and the argument to the second invocation is smaller than -the argument to the first, the intent was for the second invocation to -have no effect. Wording implying that such cases have an effect on -reallocation guarantees was inadvertant.</p> -<hr> -<a name="333"><h3>333. does endl imply synchronization with the device?</h3></a><p> -<b>Section:</b> 27.6.2.7 <a href="lib-iostreams.html#lib.ostream.manip"> [lib.ostream.manip]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> PremAnand M. Rao <b>Date:</b> 27 Aug 2001</p> -<p>A footnote in 27.6.2.7 <a href="lib-iostreams.html#lib.ostream.manip"> [lib.ostream.manip]</a> states:</p> -<blockquote> - [Footnote: The effect of executing cout << endl is to insert a - newline character in the output sequence controlled by cout, then - synchronize it with any external file with which it might be - associated. --- end foonote] -</blockquote> - -<p> -Does the term "file" here refer to the external device? -This leads to some implementation ambiguity on systems with fully -buffered files where a newline does not cause a flush to the device. -</p> - -<p> -Choosing to sync with the device leads to significant performance -penalties for each call to endl, while not sync-ing leads to -errors under special circumstances. -</p> - -<p> -I could not find any other statement that explicitly defined -the behavior one way or the other. -</p> -<p><b>Proposed resolution:</b></p> -<p>Remove footnote 300 from section 27.6.2.7 <a href="lib-iostreams.html#lib.ostream.manip"> [lib.ostream.manip]</a>.</p> -<p><b>Rationale:</b></p> -<p>We already have normative text saying what <tt>endl</tt> does: it -inserts a newline character and calls <tt>flush</tt>. This footnote -is at best redundant, at worst (as this issue says) misleading, -because it appears to make promises about what <tt>flush</tt> -does.</p> -<hr> -<a name="334"><h3>334. map::operator[] specification forces inefficient implementation</h3></a><p> -<b>Section:</b> 23.3.1.2 <a href="lib-containers.html#lib.map.access"> [lib.map.access]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Andrea Griffini <b>Date:</b> 02 Sep 2001</p> -<p> -The current standard describes map::operator[] using a -code example. That code example is however quite -inefficient because it requires several useless copies -of both the passed key_type value and of default -constructed mapped_type instances. -My opinion is that was not meant by the comitee to -require all those temporary copies. -</p> - -<p>Currently map::operator[] behaviour is specified as: </p> -<pre> - Returns: - (*((insert(make_pair(x, T()))).first)).second. -</pre> - -<p> -This specification however uses make_pair that is a -template function of which parameters in this case -will be deduced being of type const key_type& and -const T&. This will create a pair<key_type,T> that -isn't the correct type expected by map::insert so -another copy will be required using the template -conversion constructor available in pair to build -the required pair<const key_type,T> instance. -</p> - -<p>If we consider calling of key_type copy constructor -and mapped_type default constructor and copy -constructor as observable behaviour (as I think we -should) then the standard is in this place requiring -two copies of a key_type element plus a default -construction and two copy construction of a mapped_type -(supposing the addressed element is already present -in the map; otherwise at least another copy -construction for each type). -</p> - -<p>A simple (half) solution would be replacing the description with:</p> -<pre> - Returns: - (*((insert(value_type(x, T()))).first)).second. +istream& operator>> (istream &strm, S &s) +{ + ios::iostate err = ios::goodbit; + try { + const istream::sentry guard (strm, false); + if (guard) { + use_facet<num_get<char> >(strm.getloc ()) + .get (istreambuf_iterator<char>(strm), + istreambuf_iterator<char>(), + strm, err, s.i); + } + } + catch (...) { + bool rethrow; + try { + strm.setstate (ios::badbit); + rethrow = false; + } + catch (...) { + rethrow = true; + } + if (rethrow) + throw; + } + if (err) + strm.setstate (err); + return strm; +} </pre> - -<p>This will remove the wrong typed pair construction that -requires one extra copy of both key and value.</p> - -<p>However still the using of map::insert requires temporary -objects while the operation, from a logical point of view, -doesn't require any. </p> - -<p>I think that a better solution would be leaving free an -implementer to use a different approach than map::insert -that, because of its interface, forces default constructed -temporaries and copies in this case. -The best solution in my opinion would be just requiring -map::operator[] to return a reference to the mapped_type -part of the contained element creating a default element -with the specified key if no such an element is already -present in the container. Also a logarithmic complexity -requirement should be specified for the operation. -</p> - -<p> -This would allow library implementers to write alternative -implementations not using map::insert and reaching optimal -performance in both cases of the addressed element being -present or absent from the map (no temporaries at all and -just the creation of a new pair inside the container if -the element isn't present). -Some implementer has already taken this option but I think -that the current wording of the standard rules that as -non-conforming. -</p> - -<p><b>Proposed resolution:</b></p> - -<p> -Replace 23.3.1.2 <a href="lib-containers.html#lib.map.access"> [lib.map.access]</a> paragraph 1 with -</p> -<blockquote> -<p> --1- Effects: If there is no key equivalent to x in the map, inserts -value_type(x, T()) into the map. -</p> -<p> --2- Returns: A reference to the mapped_type corresponding to x in *this. -</p> -<p> --3- Complexity: logarithmic. -</p> </blockquote> -<p><i>[This is the second option mentioned above. Howard provided -wording. We may also wish to have a blanket statement somewhere in -clause 17 saying that we do not intend the semantics of sample code -fragments to be interpreted as specifing exactly how many copies are -made. See issue <a href="lwg-active.html#98">98</a> for a similar problem.]</i></p> - -<p><b>Rationale:</b></p> -<p> -This is the second solution described above; as noted, it is -consistent with existing practice. -</p> - -<p>Note that we now need to specify the complexity explicitly, because -we are no longer defining <tt>operator[]</tt> in terms of -<tt>insert</tt>.</p> -<hr> -<a name="336"><h3>336. Clause 17 lack of references to deprecated headers</h3></a><p> -<b>Section:</b> 17 <a href="lib-intro.html#lib.library"> [lib.library]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Detlef Vollmann <b>Date:</b> 05 Sep 2001</p> -<p>From c++std-edit-873:</p> - -<p>17.4.1.2 <a href="lib-intro.html#lib.headers"> [lib.headers]</a>, Table 11. In this table, the header -<strstream> is missing.</p> - -<p>This shows a general problem: The whole clause 17 refers quite -often to clauses 18 through 27, but D.7 is also a part of the standard -library (though a deprecated one).</p> - -<p><b>Proposed resolution:</b></p> -<p><i>[Redmond: The LWG agrees that <strstream> should be added -to table 11. A review is needed to determine whether there are any -other places in clause 17 where clause D material should be referred -to. Beman will review clause 17.]</i></p> - -<p><i>[Curaçao: Beman emailed wording to Matt, but not in time for the -pre-meeting mailing.]</i></p> - -<hr> -<a name="338"><h3>338. is whitespace allowed between `-' and a digit?</h3></a><p> -<b>Section:</b> 22.2 <a href="lib-locales.html#lib.locale.categories"> [lib.locale.categories]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 17 Sep 2001</p> -<p> -From Stage 2 processing in 22.2.2.1.2 <a href="lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a>, p8 and 9 (the -original text or the text corrected by the proposed resolution of -issue <a href="lwg-defects.html#221">221</a>) it seems clear that no whitespace is allowed -within a number, but 22.2.3.1 <a href="lib-locales.html#lib.locale.numpunct"> [lib.locale.numpunct]</a>, p2, which gives the -format for integer and floating point values, says that whitespace is -optional between a plusminus and a sign. -</p> - -<p> -The text needs to be clarified to either consistently allow or -disallow whitespace between a plusminus and a sign. It might be -worthwhile to consider the fact that the C library stdio facility does -not permit whitespace embedded in numbers and neither does the C or -C++ core language (the syntax of integer-literals is given in 2.13.1 <a href="lex.html#lex.icon"> [lex.icon]</a>, that of floating-point-literals in 2.13.3 <a href="lex.html#lex.fcon"> [lex.fcon]</a> of the C++ standard). -</p> -<p><b>Proposed resolution:</b></p> -<p>Change the first part of 22.2.3.1 <a href="lib-locales.html#lib.locale.numpunct"> [lib.locale.numpunct]</a> paragraph 2 from:</p> -<blockquote> -<p> -The syntax for number formats is as follows, where <tt>digit</tt> -represents the radix set specified by the <tt>fmtflags</tt> argument -value, <tt>whitespace</tt> is as determined by the facet -<tt>ctype<charT></tt> (22.2.1.1), and <tt>thousands-sep</tt> and -<tt>decimal-point</tt> are the results of corresponding -<tt>numpunct<charT></tt> members. Integer values have the -format: -</p> -<pre> - integer ::= [sign] units - sign ::= plusminus [whitespace] - plusminus ::= '+' | '-' - units ::= digits [thousands-sep units] - digits ::= digit [digits] -</pre> -</blockquote> -<p>to:</p> -<blockquote> -<p> -The syntax for number formats is as follows, where <tt>digit</tt> -represents the radix set specified by the <tt>fmtflags</tt> argument -value, and <tt>thousands-sep</tt> and <tt>decimal-point</tt> are the -results of corresponding <tt>numpunct<charT></tt> members. -Integer values have the format: -</p> -<pre> - integer ::= [sign] units - sign ::= plusminus - plusminus ::= '+' | '-' - units ::= digits [thousands-sep units] - digits ::= digit [digits] -</pre> -</blockquote> -<p><b>Rationale:</b></p> -<p>It's not clear whether the format described in 22.2.3.1 <a href="lib-locales.html#lib.locale.numpunct"> [lib.locale.numpunct]</a> paragraph 2 has any normative weight: nothing in the -standard says how, or whether, it's used. However, there's no reason -for it to differ gratuitously from the very specific description of -numeric processing in 22.2.2.1.2 <a href="lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a>. The proposed -resolution removes all mention of "whitespace" from that format.</p> -<hr> -<a name="339"><h3>339. definition of bitmask type restricted to clause 27</h3></a><p> -<b>Section:</b> 22.2.1 <a href="lib-locales.html#lib.category.ctype"> [lib.category.ctype]</a>, 17.3.2.1.2 <a href="lib-intro.html#lib.bitmask.types"> [lib.bitmask.types]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 17 September 2001</p> -<p> -The ctype_category::mask type is declared to be an enum in 22.2.1 <a href="lib-locales.html#lib.category.ctype"> [lib.category.ctype]</a> with p1 then stating that it is a bitmask type, most -likely referring to the definition of bitmask type in 17.3.2.1.2 <a href="lib-intro.html#lib.bitmask.types"> [lib.bitmask.types]</a>, p1. However, the said definition only applies to -clause 27, making the reference in 22.2.1 somewhat dubious. -</p> -<p><b>Proposed resolution:</b></p> -<p>Clarify 17.3.2.1.2, p1 by changing the current text from</p> - <blockquote> - Several types defined in clause 27 are bitmask types. Each bitmask type - can be implemented as an enumerated type that overloads certain operators, - as an integer type, or as a bitset (23.3.5 <a href="lib-containers.html#lib.template.bitset"> [lib.template.bitset]</a>). - </blockquote> -<p>to read</p> - <blockquote> - Several types defined in clauses lib.language.support through - lib.input.output and Annex D are bitmask types. Each bitmask type can - be implemented as an enumerated type that overloads certain operators, - as an integer type, or as a bitset (lib.template.bitset). - </blockquote> - -<p> -Additionally, change the definition in 22.2.1 to adopt the same -convention as in clause 27 by replacing the existing text with the -following (note, in particluar, the cross-reference to 17.3.2.1.2 in -22.2.1, p1): -</p> +<p>[2] Extractor that propagates exceptions thrown from sentry:</p> <blockquote> -<p>22.2.1 The ctype category [lib.category.ctype]</p> -<pre> -namespace std { - class ctype_base { - public: - typedef <b><i>T</i></b> mask; - - // numeric values are for exposition only. - static const mask space = 1 << 0; - static const mask print = 1 << 1; - static const mask cntrl = 1 << 2; - static const mask upper = 1 << 3; - static const mask lower = 1 << 4; - static const mask alpha = 1 << 5; - static const mask digit = 1 << 6; - static const mask punct = 1 << 7; - static const mask xdigit = 1 << 8; - static const mask alnum = alpha | digit; - static const mask graph = alnum | punct; - }; +<pre>istream& operator>> (istream &strm, S &s) +{ + istream::sentry guard (strm, false); + if (guard) { + ios::iostate err = ios::goodbit; + try { + use_facet<num_get<char> >(strm.getloc ()) + .get (istreambuf_iterator<char>(strm), + istreambuf_iterator<char>(), + strm, err, s.i); + } + catch (...) { + bool rethrow; + try { + strm.setstate (ios::badbit); + rethrow = false; + } + catch (...) { + rethrow = true; + } + if (rethrow) + throw; + } + if (err) + strm.setstate (err); + } + return strm; } </pre> - -<p>The type <tt>mask</tt> is a bitmask type (17.3.2.1.2 <a href="lib-intro.html#lib.bitmask.types"> [lib.bitmask.types]</a>).</p> </blockquote> -<p><i>[Curaçao: The LWG notes that T above should be bold-italics to be -consistent with the rest of the standard.]</i></p> - -<hr> -<a name="340"><h3>340. interpretation of <tt>has_facet<Facet>(loc)</tt> -</h3></a><p> -<b>Section:</b> 22.1.1.1.1 <a href="lib-locales.html#lib.locale.category"> [lib.locale.category]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2001</p> <p> -It's unclear whether 22.1.1.1.1, p3 says that -<tt>has_facet<Facet>(loc)</tt> returns true for any <tt>Facet</tt> -from Table 51 or whether it includes Table 52 as well: +[3] Extractor that catches exceptions thrown from sentry +but doesn't set badbit if the exception was thrown as a +result of a call to strm.clear(). </p> <blockquote> -For any locale <tt>loc</tt> either constructed, or returned by -locale::classic(), and any facet <tt>Facet</tt> that is a member of a -standard category, <tt>has_facet<Facet>(loc)</tt> is true. Each -locale member function which takes a <tt>locale::category</tt> -argument operates on the corresponding set of facets. -</blockquote> - -<p> -It seems that it comes down to which facets are considered to be members of a -standard category. Intuitively, I would classify all the facets in Table 52 as -members of their respective standard categories, but there are an unbounded set -of them... -</p> - -<p> -The paragraph implies that, for instance, <tt>has_facet<num_put<C, -OutputIterator> >(loc)</tt> must always return true. I don't think that's -possible. If it were, then <tt>use_facet<num_put<C, OutputIterator> ->(loc)</tt> would have to return a reference to a distinct object for each -valid specialization of <tt>num_put<C, OutputIteratory></tt>, which is -clearly impossible. -</p> - -<p> -On the other hand, if none of the facets in Table 52 is a member of a standard -category then none of the locale member functions that operate on entire -categories of facets will work properly. -</p> - -<p> -It seems that what p3 should mention that it's required (permitted?) -to hold only for specializations of <tt>Facet</tt> from Table 52 on -<tt>C</tt> from the set { <tt>char</tt>, <tt>wchar_t</tt> }, and -<tt>InputIterator</tt> and <tt>OutputIterator</tt> from the set of +<pre>istream& operator>> (istream &strm, S &s) { -{i,o}<tt>streambuf_iterator</tt><{<tt>char</tt>,<tt>wchar_t</tt>}<tt>></tt> -}. -</p> -<p><b>Proposed resolution:</b></p> -<p>In 22.1.1.1.1 <a href="lib-locales.html#lib.locale.category"> [lib.locale.category]</a>, paragraph 3, change -"that is a member of a standard category" to "shown in Table 51".</p> -<p><b>Rationale:</b></p> -<p>The facets in Table 52 are an unbounded set. Locales should not be -required to contain an infinite number of facets.</p> - -<p>It's not necessary to talk about which values of InputIterator and -OutputIterator must be supported. Table 51 already contains a -complete list of the ones we need.</p> -<hr> -<a name="341"><h3>341. Vector reallocation and swap</h3></a><p> -<b>Section:</b> 23.2.4.2 <a href="lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Anthony Williams <b>Date:</b> 27 Sep 2001</p> -<p>It is a common idiom to reduce the capacity of a vector by swapping it with -an empty one:</p> -<pre> - std::vector<SomeType> vec; - // fill vec with data - std::vector<SomeType>().swap(vec); - // vec is now empty, with minimal capacity -</pre> - -<p>However, the wording of 23.2.4.2 <a href="lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a>paragraph 5 prevents -the capacity of a vector being reduced, following a call to -reserve(). This invalidates the idiom, as swap() is thus prevented -from reducing the capacity. The proposed wording for issue <a href="lwg-active.html#329">329</a> does not affect this. Consequently, the example above -requires the temporary to be expanded to cater for the contents of -vec, and the contents be copied across. This is a linear-time -operation.</p> - -<p>However, the container requirements state that swap must have constant -complexity (23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> note to table 65).</p> - -<p>This is an important issue, as reallocation affects the validity of -references and iterators.</p> - -<p>If the wording of 23.2.4.2p5 is taken to be the desired intent, then -references and iterators remain valid after a call to swap, if they refer to -an element before the new end() of the vector into which they originally -pointed, in which case they refer to the element at the same index position. -Iterators and references that referred to an element whose index position -was beyond the new end of the vector are invalidated.</p> - -<p>If the note to table 65 is taken as the desired intent, then there are two -possibilities with regard to iterators and references:</p> + const ios::iostate state = strm.rdstate (); + const ios::iostate except = strm.exceptions (); + ios::iostate err = std::ios::goodbit; + bool thrown = true; + try { + const istream::sentry guard (strm, false); + thrown = false; + if (guard) { + use_facet<num_get<char> >(strm.getloc ()) + .get (istreambuf_iterator<char>(strm), + istreambuf_iterator<char>(), + strm, err, s.i); + } + } + catch (...) { + if (thrown && state & except) + throw; + try { + strm.setstate (ios::badbit); + thrown = false; + } + catch (...) { + thrown = true; + } + if (thrown) + throw; + } + if (err) + strm.setstate (err); -<ol> -<li>All Iterators and references into both vectors are invalidated.</li> -<li>Iterators and references into either vector remain valid, and remain -pointing to the same element. Consequently iterators and references that -referred to one vector now refer to the other, and vice-versa.</li> -</ol> -<p><b>Proposed resolution:</b></p> -<p>Add a new paragraph after 23.2.4.2 <a href="lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a> paragraph 5:</p> -<blockquote> -<pre> - void swap(vector<T,Allocator>& x); + return strm; +} </pre> -<p> -<b>Effects:</b> Exchanges the contents and capacity() of <tt>*this</tt> -with that of <tt>x</tt>.</p> -<p> -<b>Complexity:</b> Constant time.</p> </blockquote> -<p><i>[This solves the problem reported for this issue. We may also -have a problem with a circular definition of swap() for other -containers.]</i></p> +<p><b>Proposed resolution:</b></p> +<p>Remove the last sentence of 27.6.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a> p5 (but not + the footnote, which should be moved to the preceding sentence).</p> +<p>Remove the last sentence of 27.6.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream::sentry"> [lib.ostream::sentry]</a> p3 (but not + the footnote, which should be moved to the preceding sentence).</p> <p><b>Rationale:</b></p> -<p> -swap should be constant time. The clear intent is that it should just -do pointer twiddling, and that it should exchange all properties of -the two vectors, including their reallocation guarantees. -</p> +<p>The LWG feels that no clarification of EH policy is necessary: the + standard is precise about which operations sentry's constructor + performs, and about which of those operations can throw. However, the + sentence at the end should be removed because it's redundant.</p> <hr> <a name="342"><h3>342. seek and eofbit</h3></a><p> -<b>Section:</b> 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 09 Oct 201</p> +<b>Section:</b> 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 09 Oct 201</p> <p>I think we have a defect.</p> -<p>According to lwg issue <a href="lwg-defects.html#60">60</a> which is now a dr, the -description of seekg in 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> paragraph 38 now looks +<p>According to lwg issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#60">60</a> which is now a dr, the +description of seekg in 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> paragraph 38 now looks like:</p> <blockquote> @@ -4254,10 +2599,10 @@ Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1), except that it does not count the number of characters extracted and does not affect the value returned by subsequent calls to gcount(). After constructing a sentry object, if fail() != true, -executes rdbuf()­>pubseekpos( pos). +executes rdbuf()>pubseekpos( pos). </blockquote> -<p>And according to lwg issue <a href="lwg-defects.html#243">243</a> which is also now a dr, +<p>And according to lwg issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#243">243</a> which is also now a dr, 27.6.1.3, paragraph 1 looks like:</p> <blockquote> @@ -4298,11 +2643,11 @@ should be respected. <p><b>Further discussion from Redmond:</b></p> <p>PJP: It doesn't seem quite right to say that <tt>seekg</tt> is -"unformatted". That makes specific claims about sentry that +"unformatted". That makes specific claims about sentry that aren't quite appropriate for seeking, which has less fragile failure modes than actual input. If we do really mean that it's unformatted input, it should behave the same way as other unformatted input. On -the other hand, "principle of least surprise" is that seeking from EOF +the other hand, "principle of least surprise" is that seeking from EOF ought to be OK.</p> <p>Dietmar: nothing should depend on eofbit. Eofbit should only be @@ -4311,16 +2656,23 @@ examined by the user to determine why something failed.</p> <p><i>[Taken from c++std-lib-8873, c++std-lib-8874, c++std-lib-8876]</i></p> <p><b>Proposed resolution:</b></p> -<p><i>[Howard will do a survey to find out if there are any other -places where we have a problem, where the difference between -<tt>fail()</tt> and <tt>!good()</tt> is important.]</i></p> + +<p><i>[Santa Cruz: On the one hand, it would clearly be silly to seek + to a non-EOF position without resetting eofbit. On the other hand, + having seek clear eofbit explicitly would set a major precedent: + there is currently <i>no</i> place where any of the flags are reset + without the user explicitly asking for them to be. This is the tip + of a general problem, that the various flags are stickier than many + users might expect. Bill, Gaby, and Howard will discuss this issue + and propose a resolution.]</i></p> + <hr> <a name="347"><h3>347. locale::category and bitmask requirements</h3></a><p> -<b>Section:</b> 22.1.1.1.1 <a href="lib-locales.html#lib.locale.category"> [lib.locale.category]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> P.J. Plauger, Nathan Myers <b>Date:</b> 23 Oct 2001</p> +<b>Section:</b> 22.1.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.category"> [lib.locale.category]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> P.J. Plauger, Nathan Myers <b>Date:</b> 23 Oct 2001</p> <p> -In 22.1.1.1.1 <a href="lib-locales.html#lib.locale.category"> [lib.locale.category]</a> paragraph 1, the category members +In 22.1.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.category"> [lib.locale.category]</a> paragraph 1, the category members are described as bitmask elements. In fact, the bitmask requirements -in 17.3.2.1.2 <a href="lib-intro.html#lib.bitmask.types"> [lib.bitmask.types]</a> don't seem quite right: <tt>none</tt> +in 17.3.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.bitmask.types"> [lib.bitmask.types]</a> don't seem quite right: <tt>none</tt> and <tt>all</tt> are bitmask constants, not bitmask elements.</p> <p>In particular, the requirements for <tt>none</tt> interact poorly @@ -4334,17 +2686,14 @@ category arguments. Option 2 changes the category type so that this requirement is implementable, by allowing <tt>none</tt> to be some value such as 0x1000 instead of 0.</p> -<p>Nathan writes: "I believe my proposed resolution [Option 2] merely +<p>Nathan writes: "I believe my proposed resolution [Option 2] merely re-expresses the status quo more clearly, without introducing any changes beyond resolving the DR.</p> <p><b>Proposed resolution:</b></p> -<p> -<b>Option 1:</b> <br> -Replace the first two paragraphs of 22.1.1.1 <a href="lib-locales.html#lib.locale.types"> [lib.locale.types]</a> with:</p> +<p>Replace the first two paragraphs of 22.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.types"> [lib.locale.types]</a> with:</p> <blockquote> -<pre> - typedef int category; +<pre> typedef int category; </pre> <p>Valid category values include the <tt>locale</tt> member bitmask @@ -4354,8 +2703,7 @@ represents a single locale category. In addition, <tt>locale</tt> member bitmask constant <tt>none</tt> is defined as zero and represents no category. And locale member bitmask constant <tt>all</tt> is defined such that the expression</p> -<pre> - (collate | ctype | monetary | numeric | time | messages | all) == all +<pre> (collate | ctype | monetary | numeric | time | messages | all) == all </pre> <p> is <tt>true</tt>, and represents the union of all categories. Further @@ -4373,10 +2721,22 @@ in turn, identifies a set of locale facets, including at least those shown in Table 51: </p> </blockquote> +<p><i>[Curaçao: need input from locale experts.]</i></p> + +<p><b>Rationale:</b></p> + +<p>The LWG considered, and rejected, an alternate proposal (described + as "Option 2" in the discussion). The main reason for rejecting it + was that library implementors were concerened about implementation + difficult, given that getting a C++ library to work smoothly with a + separately written C library is already a delicate business. Some + library implementers were also concerned about the issue of adding + extra locale categories.</p> +<blockquote> <p> <b>Option 2:</b> <br> -Replace the first paragraph of 22.1.1.1 <a href="lib-locales.html#lib.locale.types"> [lib.locale.types]</a> with:</p> +Replace the first paragraph of 22.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.types"> [lib.locale.types]</a> with:</p> <blockquote> <p> Valid category values include the enumerated values. In addition, the @@ -4395,145 +2755,10 @@ those categories found in <tt>cat1</tt> but not found in <tt>cat2</tt>. of the other enumerated values; implementations may add extra categories.] </p> </blockquote> - -<p><i>[Curaçao: need input from locale experts.]</i></p> - -<hr> -<a name="348"><h3>348. Minor issue with std::pair operator<</h3></a><p> -<b>Section:</b> 20.2.2 <a href="lib-utilities.html#lib.pairs"> [lib.pairs]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 23 Oct 2001</p> -<p> -The current wording of 20.2.2 [lib.pairs] p6 precludes the use of -operator< on any pair type which contains a pointer. -</p> -<p><b>Proposed resolution:</b></p> -<p>In 20.2.2 <a href="lib-utilities.html#lib.pairs"> [lib.pairs]</a> paragraph 6, replace:</p> -<pre> - Returns: x.first < y.first || (!(y.first < x.first) && x.second < - y.second). -</pre> -<p>With:</p> -<pre> - Returns: std::less<T1>()( x.first, y.first ) || - (!std::less<T1>()( y.first, x.first) && - std::less<T2>()( x.second, y.second ) ) -</pre> - -<p><i>[Curaçao: LWG leaning toward NAD. In favor of the PR is -that it removes a trap for users. Concerns: 1) will break some -small amount of existing code (which define less and operator < -with different behavior), 2) don't have any indication of rationale -for current design (and unwilling to change without knowing -rationale), 3) consistency; pairs of ptrs would behave differenly from -individual pointers.]</i></p> - -<hr> -<a name="349"><h3>349. Minor typographical error in ostream_iterator</h3></a><p> -<b>Section:</b> 24.5.2 <a href="lib-iterators.html#lib.ostream.iterator"> [lib.ostream.iterator]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 24 Oct 2001</p> -<p>24.5.2 [lib.ostream.iterator] states:</p> -<pre> - [...] - - private: - // basic_ostream<charT,traits>* out_stream; exposition only - // const char* delim; exposition only -</pre> - -<p>Whilst it's clearly marked "exposition only", I suspect 'delim' -should be of type 'const charT*'.</p> -<p><b>Proposed resolution:</b></p> -<p> -In 24.5.2 <a href="lib-iterators.html#lib.ostream.iterator"> [lib.ostream.iterator]</a>, replace <tt>const char* delim</tt> with -<tt>const charT* delim</tt>. -</p> -<hr> -<a name="350"><h3>350. allocator<>::address</h3></a><p> -<b>Section:</b> 20.4.1.1 <a href="lib-utilities.html#lib.allocator.members"> [lib.allocator.members]</a>, 20.1.5 <a href="lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a>, 17.4.1.1 <a href="lib-intro.html#lib.contents"> [lib.contents]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 25 Oct 2001</p> -<p>See c++std-lib-9006 and c++std-lib-9007. This issue is taken -verbatim from -9007.</p> - -<p> -The core language feature allowing definition of operator&() applied -to any non-builtin type makes that operator often unsafe to use in -implementing libraries, including the Standard Library. The result -is that many library facilities fail for legal user code, such as -the fragment</p> -<pre> - class A { private: A* operator&(); }; - std::vector<A> aa; - - class B { }; - B* operator&(B&) { return 0; } - std::vector<B> ba; -</pre> - -<p> -In particular, the requirements table for Allocator (Table 32) specifies -no semantics at all for member address(), and allocator<>::address is -defined in terms of unadorned operator &. -</p> - -<p><i>[Curaçao: The LWG believes both examples are ill-formed. -The contained type is required to be CopyConstructible (20.1.3), and -that includes the requirement that &t return the usual types and -values. Since the CopyConstructible requirements appear to have been -written to deal with the concerns of this issue, the LWG feels it is -NAD unless someone can come up with a well-formed example exhibiting a -problem.]</i></p> - -<p><b>Proposed resolution:</b></p> -<p> -In 20.4.1.1, Change the definition of allocator<>::address from:</p> -<blockquote> - Returns: &x </blockquote> - -<p>to:</p> - -<p> - Returns: The value that the built in operator&(x) would return if not - overloaded. -</p> - -<p> -In 20.1.5, Table 32, add to the Notes column of the a.address(r) and -a.address(s) lines, respectively: -</p> - -<pre> - allocator<T>::address(r) - allocator<T>::address(s) -</pre> - -<p>In addition, in clause 17.4.1.1, add a statement:</p> - -<blockquote> - The Standard Library does not apply operator& to any type for which - operator& may be overloaded. -</blockquote> - -<p><i>[Curaçao: If the issues isn't NAD, suggest changing "if not -overloaded" to "ignoring all overloads".]</i></p> - -<p><b>Rationale:</b></p> -<p>The obvious implementations for std::allocator<>::address are</p> -<pre> - T* reinterpret_cast<T*>(&static_cast<char&>(o)); -</pre> - -<p>and</p> - -<pre> - T const* reinterpret_cast<T const*>(&static_cast<char const&>(o)); -</pre> - -<p> -but to define them formally in terms of reinterpret_cast<> seems -to introduce semantic difficulties best avoided. Using a.address() -should not introduce unspecified or implementation-defined semantics -into a user program.</p> <hr> <a name="352"><h3>352. missing fpos requirements</h3></a><p> -<b>Section:</b> 21.1.2 <a href="lib-strings.html#lib.char.traits.typedefs"> [lib.char.traits.typedefs]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 2 Dec 2001</p> +<b>Section:</b> 21.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.char.traits.typedefs"> [lib.char.traits.typedefs]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 2 Dec 2001</p> <p> <i>(1)</i> There are no requirements on the <tt>stateT</tt> template parameter of @@ -4566,101 +2791,34 @@ Modify 21.1.2, p4 from (23.1, p4), CopyConstructible (20.1.3), and DefaultConstructible (20.1.4) types. </p> -<p> -Add to the definition of the fpos class template the following member: -</p> -<pre> - typedef stateT state_type; -</pre> -<p> -and add to 27.4.3.1 a paragraph with the following text: -</p> -<pre> - typedef stateT state_type; -</pre> -<p> - Requires: <tt>state_type</tt> shall meet the requirements of - Assignable (23.1, p4), CopyConstructible (20.1.3), and - DefaultConstructible (20.1.4) types. -</p> - -<p><i>[Curaçao: The LWG feels this is two issues, as indicated -above. The first is a defect; more I/O experts need to review -the PR. The second is questionable; who would use it? Unless -motivation is provided, the second should be considered NAD.]</i></p> - -<hr> -<a name="354"><h3>354. Associative container lower/upper bound requirements</h3></a><p> -<b>Section:</b> 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Hans Aberg <b>Date:</b> 17 Dec 2001</p> -<p> -Discussions in the thread "Associative container lower/upper bound -requirements" on comp.std.c++ suggests that there is a defect in the -C++ standard, Table 69 of section 23.1.2, "Associative containers", -[lib.associative.reqmts]. It currently says:</p> - -<blockquote> -<p> -a.find(k): returns an iterator pointing to an element with the key equivalent to -k, or a.end() if such an element is not found. -</p> - -<p> -a.lower_bound(k): returns an iterator pointing to the first element with -key not less than k. -</p> - -<p> -a.upper_bound(k): returns an iterator pointing to the first element with -key greater than k. -</p> -</blockquote> - -<p> -We have "or a.end() if such an element is not found" for -<tt>find</tt>, but not for <tt>upper_bound</tt> or -<tt>lower_bound</tt>. As the text stands, one would be forced to -insert a new element into the container and return an iterator to that -in case the sought iterator does not exist, which does not seem to be -the intention (and not possible with the "const" versions). -</p> -<p><b>Proposed resolution:</b></p> - -<p>Change Table 69 of section 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> indicated entries -to:</p> - -<blockquote> -<p> -a.lower_bound(k): returns an iterator pointing to the first element with -key not less than k, or a.end() if such an element is not found. -</p> - -<p> -a.upper_bound(k): returns an iterator pointing to the first element with -key greater than k, or a.end() if such an element is not found. -</p> -</blockquote> - -<p><i>[Curaçao: LWG reviewed PR.]</i></p> +<p><b>Rationale:</b></p> +<p>The LWG feels this is two issues, as indicated above. The first is +a defect---std::basic_fstream is unimplementable without these +additional requirements---and the proposed resolution fixes it. The +second is questionable; who would use that typedef? The class +template fpos is used only in a very few places, all of which know the +state type already. Unless motivation is provided, the second should +be considered NAD.</p> <hr> <a name="355"><h3>355. Operational semantics for a.back()</h3></a><p> -<b>Section:</b> 23.1.1 <a href="lib-containers.html#lib.sequence.reqmts"> [lib.sequence.reqmts]</a> <b>Status:</b> <a href="lwg-active.html#Review">Review</a> <b>Submitter:</b> Yaroslav Mironov <b>Date:</b> 23 Jan 2002</p> +<b>Section:</b> 23.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.sequence.reqmts"> [lib.sequence.reqmts]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Yaroslav Mironov <b>Date:</b> 23 Jan 2002</p> -<p>Table 68 "Optional Sequence Operations" in 23.1.1/12 -specifies operational semantics for "a.back()" as -"*--a.end()", which may be ill-formed <i>[because calling +<p>Table 68 "Optional Sequence Operations" in 23.1.1/12 +specifies operational semantics for "a.back()" as +"*--a.end()", which may be ill-formed <i>[because calling operator-- on a temporary (the return) of a built-in type is ill-formed]</i>, provided a.end() returns a simple pointer rvalue (this is almost always the case for std::vector::end(), for example). Thus, the specification is not only incorrect, it -demonstrates a dangerous construct: "--a.end()" may +demonstrates a dangerous construct: "--a.end()" may successfully compile and run as intended, but after changing the type of the container or the mode of compilation it may produce compile-time error. </p> <p><b>Proposed resolution:</b></p> -<p>Change the specification in table 68 "Optional Sequence -Operations" in 23.1.1/12 for "a.back()" from</p> +<p>Change the specification in table 68 "Optional Sequence +Operations" in 23.1.1/12 for "a.back()" from</p> <blockquote> @@ -4670,10 +2828,10 @@ Operations" in 23.1.1/12 for "a.back()" from</p> <p>to</p> <blockquote> - <p>*a.rbegin()</p> + { iterator tmp = a.end(); --tmp; *tmp; } </blockquote> -<p>and the specification for "a.pop_back()" from</p> +<p>and the specification for "a.pop_back()" from</p> <blockquote> a.erase(--a.end()) @@ -4682,29 +2840,40 @@ a.erase(--a.end()) <p>to</p> <blockquote> - <p>a.erase(rbegin())</p> + { iterator tmp = a.end(); --tmp; a.erase(tmp); } </blockquote> -<p><i>[Curaçao: LWG changed PR from "{ X::iterator tmp = -a.end(); return *--tmp; }" to "*a.rbegin()", and from -"{ X::iterator tmp = a.end(); a.erase(--tmp); }" to -"a.erase(rbegin())".]</i></p> +<p><i>[Curaçao: LWG changed PR from "{ X::iterator tmp = +a.end(); return *--tmp; }" to "*a.rbegin()", and from +"{ X::iterator tmp = a.end(); a.erase(--tmp); }" to +"a.erase(rbegin())".]</i></p> -<p><i>[There is a second possible defect; table 68 "Optional -Sequence Operations" in the "Operational Semantics" -column uses operations present only in the "Reversible -Container" requirements, yet there is no stated dependency +<p><i>[There is a second possible defect; table 68 "Optional +Sequence Operations" in the "Operational Semantics" +column uses operations present only in the "Reversible +Container" requirements, yet there is no stated dependency between these separate requirements tables. Ask in Santa Cruz if the LWG would like a new issue opened.]</i></p> +<p><i>[Santa Cruz: the proposed resolution is even worse than what's in + the current standard: erase is undefined for reverse iterator. If + we're going to make the change, we need to define a temporary and + use operator--. Additionally, we don't know how prevalent this is: + do we need to make this change in more than one place? Martin has + volunteered to review the standard and see if this problem occurs + elsewhere.]</i></p> + +<p><i>[Oxford: Matt provided new wording to address the concerns raised + in Santa Cruz. It does not appear that this problem appears + anywhere else in clauses 23 or 24.]</i></p> + <hr> <a name="356"><h3>356. Meaning of ctype_base::mask enumerators</h3></a><p> -<b>Section:</b> 22.2.1 <a href="lib-locales.html#lib.category.ctype"> [lib.category.ctype]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 23 Jan 2002</p> +<b>Section:</b> 22.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.category.ctype"> [lib.category.ctype]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 23 Jan 2002</p> <p>What should the following program print?</p> -<pre> - #include <locale> +<pre> #include <locale> #include <iostream> class my_ctype : public std::ctype<char> @@ -4724,15 +2893,15 @@ LWG would like a new issue opened.]</i></p> int main() { my_ctype ct; - std::cout << "isspace: " << ct.is(std::ctype_base::space, '_') << " " - << "isalpha: " << ct.is(std::ctype_base::alpha, '_') << std::endl; + std::cout << "isspace: " << ct.is(std::ctype_base::space, '_') << " " + << "isalpha: " << ct.is(std::ctype_base::alpha, '_') << std::endl; } </pre> <p>The goal is to create a facet where '_' is treated as whitespace.</p> -<p>On gcc 3.0, this program prints "isspace: 1 isalpha: 0". On -Microsoft C++ it prints "isspace: 1 isalpha: 1".</p> +<p>On gcc 3.0, this program prints "isspace: 1 isalpha: 0". On +Microsoft C++ it prints "isspace: 1 isalpha: 1".</p> <p> I believe that both implementations are legal, and the standard does not @@ -4743,8 +2912,8 @@ protected interface portably.</p> The above program assumes that ctype_base::mask enumerators like <tt>space</tt> and <tt>print</tt> are disjoint, and that the way to say that a character is both a space and a printing character is to or -those two enumerators together. This is suggested by the "exposition -only" values in 22.2.1 <a href="lib-locales.html#lib.category.ctype"> [lib.category.ctype]</a>, but it is nowhere specified in +those two enumerators together. This is suggested by the "exposition +only" values in 22.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.category.ctype"> [lib.category.ctype]</a>, but it is nowhere specified in normative text. An alternative interpretation is that the more specific categories subsume the less specific. The above program gives the results it does on the Microsoft compiler because, on that @@ -4769,12 +2938,56 @@ lib-9224, lib-9226, lib-9229, lib-9270, lib-9272, lib-9273, lib-9274, lib-9277, lib-9279. </p> -<p>Issue <a href="lwg-active.html#339">339</a> is related, but not identical. The -proposed resolution if issue <a href="lwg-active.html#339">339</a> says that +<p>Issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#339">339</a> is related, but not identical. The +proposed resolution if issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#339">339</a> says that ctype_base::mask must be a bitmask type. It does not say that the ctype_base::mask elements are bitmask elements, so it doesn't directly affect this issue.</p> +<p>More comments from Benjamin Kosnik, who believes that +that C99 compatibility essentially requires what we're +calling option 1 below.</p> + +<blockquote> +<pre>I think the C99 standard is clear, that isspace -> !isalpha. +-------- + +#include <locale> +#include <iostream> + +class my_ctype : public std::ctype<char> +{ +private: + typedef std::ctype<char> base; + mask my_table[base::table_size]; + +public: + my_ctype(std::size_t refs = 0) : base(my_table, false, refs) + { + std::copy(base::classic_table(), base::classic_table() + base::table_size, + my_table); + mask both = base::print | base::space; + my_table[static_cast<mask>('_')] = both; + } +}; + +int main() +{ + using namespace std; + my_ctype ct; + cout << "isspace: " << ct.is(ctype_base::space, '_') << endl; + cout << "isprint: " << ct.is(ctype_base::print, '_') << endl; + + // ISO C99, isalpha iff upper | lower set, and !space. + // 7.5, p 193 + // -> looks like g++ behavior is correct. + // 356 -> bitmask elements are required for ctype_base + // 339 -> bitmask type required for mask + cout << "isalpha: " << ct.is(ctype_base::alpha, '_') << endl; +} +</pre> +</blockquote> + <p><b>Proposed resolution:</b></p> <p>Informally, we have three choices:</p> <ol> @@ -4791,99 +3004,18 @@ program is not portable.</li> of portability. Either one will require some implementations to change.</p> -<hr> -<a name="357"><h3>357. <cmath> float functions cannot return HUGE_VAL</h3></a><p> -<b>Section:</b> 26.5 <a href="lib-numerics.html#lib.c.math"> [lib.c.math]</a> <b>Status:</b> <a href="lwg-active.html#Open">Open</a> <b>Submitter:</b> Ray Lischner <b>Date:</b> 26 Feb 2002</p> -<p> -The float versions of the math functions have no meaningful value to return -for a range error. The long double versions have a value they can return, -but it isn't necessarily the most reasonable value. -</p> - -<p> -Section 26.5 [lib.c.math], paragraph 5, says that C++ "adds float and long -double overloaded versions of these functions, with the same semantics," -referring to the math functions from the C90 standard. -</p> - -<p> -The C90 standard, in section 7.5.1, paragraph 3, says that functions return -"the value of the macro HUGE_VAL" when they encounter a range error. -Section 7.5, paragraph 2, defines HUGE_VAL as a macro that "expands to a -positive double expression, not necessarily representable as a float." -</p> - -<p> -Therefore, the float versions of the math functions have no way to -signal a range error. <i>[Curaçao: The LWG notes that this isn't -strictly correct, since errno is set.]</i> The semantics require that they -return HUGE_VAL, but they cannot because HUGE_VAL might not be -representable as a float. -</p> - -<p> -The problem with long double functions is less severe because HUGE_VAL is -representable as a long double. On the other hand, it might not be a "huge" -long double value, and might fall well within the range of normal return -values for a long double function. Therefore, it does not make sense for a -long double function to return a double (HUGE_VAL) for a range error. -</p> -<p><b>Proposed resolution:</b></p> -<p>Curaçao: C99 was faced with a similar problem, which they fixed by -adding HUGE_VALF and HUGE_VALL in addition to HUGE_VAL.</p> - -<p>C++ must also fix, but it should be done in the context of the -general C99 based changes to C++, not via DR. Thus the LWG in Curaçao -felt the resolution should be NAD, FUTURE, but the issue is being held -open for one more meeting to ensure LWG members not present during the -discussion concur.</p> -<hr> -<a name="358"><h3>358. interpreting <tt>thousands_sep</tt> after a <tt>decimal_point</tt> -</h3></a><p> -<b>Section:</b> 22.2.2.1.2 <a href="lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 12 Mar 2002</p> -<p> -I don't think <tt>thousands_sep</tt> is being treated correctly after -decimal_point has been seen. Since grouping applies only to the -integral part of the number, the first such occurrence should, IMO, -terminate Stage 2. (If it does not terminate it, then 22.2.2.1.2, p12 -and 22.2.3.1.2, p3 need to explain how <tt>thousands_sep</tt> is to be -interpreted in the fractional part of a number.) -</p> - -<p> -The easiest change I can think of that resolves this issue would be -something like below. -</p> -<p><b>Proposed resolution:</b></p> -<p> -Change the first sentence of 22.2.2.1.2, p9 from -</p> - -<blockquote> - If discard is true then the position of the character is - remembered, but the character is otherwise ignored. If it is not - discarded, then a check is made to determine if c is allowed as - the next character of an input field of the conversion specifier - returned by stage 1. If so it is accumulated. -</blockquote> - -<p>to</p> - -<blockquote> - If <tt>discard</tt> is true, then if <tt>'.'</tt> has not yet been - accumulated, then the position of the character is remembered, but - the character is otherwise ignored. Otherwise, if <tt>'.'</tt> has - already been accumulated, the character is discarded and Stage 2 - terminates. ... -</blockquote> +<p><i>[ +More discussion is needed. Nobody likes option 3. Options 1 and 2 +are both controversial, 2 perhaps less so. Benjamin thinks that +option 1 is required for C99 compatibility. +]</i></p> <hr> <a name="359"><h3>359. num_put<>::do_put (..., bool) undocumented</h3></a><p> -<b>Section:</b> 22.2.2.2.1 <a href="lib-locales.html#lib.facet.num.put.members"> [lib.facet.num.put.members]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 12 Mar 2002</p> +<b>Section:</b> 22.2.2.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.put.members"> [lib.facet.num.put.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 12 Mar 2002</p> <p>22.2.2.2.1, p1:</p> - <pre> - iter_type put (iter_type out, ios_base& str, char_type fill, + <pre> iter_type put (iter_type out, ios_base& str, char_type fill, bool val) const; ... @@ -4894,8 +3026,7 @@ Change the first sentence of 22.2.2.1.2, p9 from however, 22.2.2.2.2, p23:</p> <blockquote> -<pre> -iter_type put (iter_type out, ios_base& str, char_type fill, +<pre>iter_type put (iter_type out, ios_base& str, char_type fill, bool val) const; </pre> @@ -4903,8 +3034,7 @@ iter_type put (iter_type out, ios_base& str, char_type fill, Effects: If (str.flags() & ios_base::boolalpha) == 0 then do out = do_put(out, str, fill, (int)val) Otherwise do -<pre> - string_type s = +<pre> string_type s = val ? use_facet<ctype<charT> >(loc).truename() : use_facet<ctype<charT> >(loc).falsename(); </pre> @@ -4920,7 +3050,7 @@ should read <tt>do_put()</tt>, and not <tt>put()</tt>? <p> Note also that there is no <b>Returns</b> clause for this function, which should probably be corrected, just as should the second occurrence -of <i>"out."</i> in the text. +of <i>"out."</i> in the text. </p> <p> @@ -4928,8 +3058,11 @@ I think the least invasive change to fix it would be something like the following: </p> <p><b>Proposed resolution:</b></p> +<p>In 22.2.2.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a>, just above paragraph 1, remove + the <tt>bool</tt> overload.</p> + <p> -In 22.2.2.2.2, p23, make the following changes +In 22.2.2.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a>, p23, make the following changes </p> <blockquote> @@ -4947,10 +3080,9 @@ In 22.2.2.2.2, p23, make the following changes <blockquote> 23 <b>Returns</b>: If <tt>(str.flags() & ios_base::boolalpha) == 0</tt> then - <tt>do_put (out, str, fill, (int)val)</tt> + <tt>do_put (out, str, fill, (long)val)</tt> Otherwise the function obtains a string <tt>s</tt> as if by -<pre> - string_type s = +<pre> string_type s = val ? use_facet<ctype<charT> >(loc).truename() : use_facet<ctype<charT> >(loc).falsename(); </pre> @@ -4959,88 +3091,22 @@ In 22.2.2.2.2, p23, make the following changes and returns <tt>out</tt>. </blockquote> -<hr> -<a name="360"><h3>360. locale mandates inefficient implementation</h3></a><p> -<b>Section:</b> 22.1.1 <a href="lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 12 Mar 2002</p> -<p> -22.1.1, p7 (copied below) allows iostream formatters and extractors -to make assumptions about the values returned from facet members. -However, such assumptions are apparently not guaranteed to hold -in other cases (e.g., when the facet members are being called directly -rather than as a result of iostream calls, or between successive -calls to the same iostream functions with no interevening calls to -<tt>imbue()</tt>, or even when the facet member functions are called -from other member functions of other facets). This restriction -prevents locale from being implemented efficiently. -</p> -<p><b>Proposed resolution:</b></p> -<p>Change the first sentence in 22.1.1, p7 from</p> -<blockquote> - In successive calls to a locale facet member function during - a call to an iostream inserter or extractor or a streambuf member - function, the returned result shall be identical. [Note: This - implies that such results may safely be reused without calling - the locale facet member function again, and that member functions - of iostream classes cannot safely call <tt>imbue()</tt> - themselves, except as specified elsewhere. --end note] -</blockquote> - -<p>to</p> - -<blockquote> - In successive calls to a locale facet member function on a facet - object installed in the same locale, the returned result shall be - identical. ... -</blockquote> - -<hr> -<a name="361"><h3>361. num_get<>::do_get (..., void*&) checks grouping</h3></a><p> -<b>Section:</b> 22.2.2.2.2 <a href="lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 12 Mar 2002</p> -<p> -22.2.2.2.2, p12 specifies that <tt>thousands_sep</tt> is to be inserted only -for integral types (issue 282 suggests that this should be done for -all arithmetic types). -</p> - -<p> -22.2.2.1.2, p12 requires that grouping be checked for all extractors -including that for <tt>void*</tt>. -</p> - -<p> -I don't think that's right. <tt>void*</tt> values should not be checked for -grouping, should they? (Although if they should, then <tt>num_put</tt> needs -to write them out, otherwise their extraction will fail.) -</p> -<p><b>Proposed resolution:</b></p> +<p><b>Rationale:</b></p> <p> -Change the first sentence of 22.2.2.2.2, p12 from +This fixes a couple of obvious typos, and also fixes what appears to +be a requirement of gratuitous inefficiency. </p> -<blockquote> - Digit grouping is checked. That is, the positions of discarded - separators is examined for consistency with - use_facet<numpunct<charT> >(loc).grouping(). - If they are not consistent then ios_base::failbit is assigned - to err. -</blockquote> - -<p>to</p> -<blockquote> - Except for conversions to void*, digit grouping is checked... -</blockquote> - <hr> <a name="362"><h3>362. bind1st/bind2nd type safety</h3></a><p> -<b>Section:</b> 20.3.6.2 <a href="lib-utilities.html#lib.bind.1st"> [lib.bind.1st]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Andrew Demkin <b>Date:</b> 26 Apr 2002</p> +<b>Section:</b> 20.3.6.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.bind.1st"> [lib.bind.1st]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Andrew Demkin <b>Date:</b> 26 Apr 2002</p> <p> -The definition of bind1st() (20.3.6.2 <a href="lib-utilities.html#lib.bind.1st"> [lib.bind.1st]</a>) can result in +The definition of bind1st() (20.3.6.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.bind.1st"> [lib.bind.1st]</a>) can result in the construction of an unsafe binding between incompatible pointer types. For example, given a function whose first parameter type is 'pointer to T', it's possible without error to bind an argument of type 'pointer to U' when U does not derive from T: </p> -<pre> - foo(T*, int); +<pre> foo(T*, int); struct T {}; struct U {}; @@ -5058,25 +3124,23 @@ The definition of bind1st() includes a functional-style conversion to map its argument to the expected argument type of the bound function (see below): </p> -<pre> - typename Operation::first_argument_type(x) +<pre> typename Operation::first_argument_type(x) </pre> <p> -A functional-style conversion (5.2.3 <a href="expr.html#expr.type.conv"> [expr.type.conv]</a>) is defined to be -semantically equivalent to an explicit cast expression (5.4 <a href="expr.html#expr.cast"> [expr.cast]</a>), which may (according to 5.4, paragraph 5) be interpreted +A functional-style conversion (5.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/expr.html#expr.type.conv"> [expr.type.conv]</a>) is defined to be +semantically equivalent to an explicit cast expression (5.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/expr.html#expr.cast"> [expr.cast]</a>), which may (according to 5.4, paragraph 5) be interpreted as a reinterpret_cast, thus masking the error. </p> -<p>The problem and proposed change also apply to 20.3.6.4 <a href="lib-utilities.html#lib.bind.2nd"> [lib.bind.2nd]</a>.</p> +<p>The problem and proposed change also apply to 20.3.6.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.bind.2nd"> [lib.bind.2nd]</a>.</p> <p><b>Proposed resolution:</b></p> <p> The simplest and most localized change to prevent such errors is to require bind1st() use a static_cast expression rather than the functional-style conversion; that is, have bind1st() return: </p> -<pre> - binder1st<Operation>( op, +<pre> binder1st<Operation>( op, static_cast<typename Operation::first_argument_type>(x)). </pre> @@ -5094,292 +3158,177 @@ unifying the conversion rules for user defined types and built-in types, which can be especially important for generic template programming. </p> -<hr> -<a name="363"><h3>363. Missing exception specification in 27.4.2.1.1</h3></a><p> -<b>Section:</b> 27.4.2.1.1 <a href="lib-iostreams.html#lib.ios::failure"> [lib.ios::failure]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Walter Brown <b>Date:</b> 20 May 2002</p> -<p> -The destructor of ios_base::failure should have an empty throw -specification, because the destructor of its base class, exception, is -declared in this way. -</p> -<p><b>Proposed resolution:</b></p> -<p>Change the destructor to</p> -<pre> - virtual ~failure() throw(); -</pre> -<hr> -<a name="364"><h3>364. Inconsistent wording in 27.5.2.4.2</h3></a><p> -<b>Section:</b> 27.5.2.4.2 <a href="lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Walter Brown <b>Date:</b> 10 May 2002</p> -<p> -27.5.2.4.2 <a href="lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a> paragraph 1 is inconsistent with the Effects -clause for seekoff. -</p> -<p><b>Proposed resolution:</b></p> -<p> -Make this paragraph, the Effects clause for setbuf, consistent in wording -with the Effects clause for seekoff in paragraph 3 by amending paragraph 1 -to indicate the purpose of setbuf: -</p> - -<p>Original text:</p> - -<blockquote> -1 Effects: Performs an operation that is defined separately for each -class derived from basic_streambuf in this clause (27.7.1.3, 27.8.1.4). -</blockquote> - -<p>Proposed text:</p> - -<blockquote> -1 Effects: Influences stream buffering in a way that is defined separately -for each class derived from basic_streambuf in this clause -(27.7.1.3, 27.8.1.4). -</blockquote> +<p><i>[Santa Cruz: it's clear that a function-style cast is + wrong. Maybe a static cast would be better, or maybe no cast at + all. Jeremy will check with the original author of this part + of the Standard and will see what the original intent was.]</i></p> <hr> <a name="365"><h3>365. Lack of const-qualification in clause 27</h3></a><p> -<b>Section:</b> 27 <a href="lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Walter Brown <b>Date:</b> 10 May 2002</p> +<b>Section:</b> 27 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Walter Brown, Marc Paterno <b>Date:</b> 10 May 2002</p> <p> -None of the following member functions are declared const, but we -believe each should be. See document N1360 for details and rationale. +Some stream and streambuf member functions are declared non-const, +even thought they appear only to report information rather than to +change an object's logical state. They should be declared const. See +document N1360 for details and rationale. </p> -<p><b>Proposed resolution:</b></p> -<p>In 27.5.2 and 27.5.2.2.3</p> -<p>Replace</p> -<pre> - streamsize in_avail(); -</pre> -<p>with</p> -<pre> - streamsize in_avail() const; -</pre> - -<p>In 27.5.2 and 27.5.2.4.3, and 27.8.1.1 and 27.8.1.4</p> -<p>Replace</p> -<pre> - virtual streamsize showmanyc(); -</pre> -<p>with</p> -<pre> - virtual streamsize showmanyc() const; -</pre> - -<p>In 27.6.1.1 and 27.6.1.3</p> -<p>Replace</p> -<pre> - pos_type tellg(); -</pre> -<p>with</p> -<pre> - pos_type tellg() const; -</pre> - -<p>This requires additional change, because paragraph 37 describes the -return value in terms of calls to non-const member functions. Either of -the two following solutions would allow tellg to be declared const.</p> - -<p>Option 1: Implementers may cast away const-ness, to allow calling the -non-const rdbuf.</p> -<p>In paragraph 37, replace:</p> -<pre> - .... rdbuf() - ->pubseekoff(0, cur, in). -</pre> -<p>by</p> -<pre> - .... const_cast<basic_istream<charT, traits>*>(this)->rdbuf() - ->pubseekoff(0, cur, in). -</pre> - -<p>Option 2: Provide const member functions to do the job. The proposals in -a later section (specifically, the modifications concerning rdbuf -throughout the iostream library) meet most of this need; we would also -need the following addition to basic_streambuf:</p> -<blockquote> -<pre> -basic_streambuf<charT,traits>::pos_type -basic_streambuf<charT,traits>::position(ios_base::openmode mode = - ios_base::in|ios_base::out) - const; -</pre> -<p>Effects: same as calling basic_streambuf::pubseekoff(0, ios base::cur, mode)</p> -</blockquote> - -<p>In 27.6.2.1 and 27.6.2.4</p> -<p>Replace</p> -<pre> - pos_type tellp(); -</pre> -<p>with</p> -<pre> - pos_type tell() const; -</pre> +<p>The list of member functions under discussion: <tt>in_avail</tt>, +<tt>showmanyc</tt>, <tt>tellg</tt>, <tt>tellp</tt>, <tt>is_open</tt>.</p> -<p>This requires additional change; see the discussion for tellg() above.</p> +<p>Related issue: <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#73">73</a> +</p> +<p><b>Proposed resolution:</b></p> <p>In 27.8.1.5, 27.8.1.7, 27.8.1.8, 27.8.1.10, 27.8.1.11, and 27.8.1.13</p> <p>Replace</p> -<pre> - bool is_open(); +<pre> bool is_open(); </pre> <p>with</p> -<pre> - bool is_open() const; +<pre> bool is_open() const; </pre> +<p><b>Rationale:</b></p> +<p>Of the changes proposed in N1360, the only one that is safe is +changing the filestreams' is_open to const. The LWG believed that +this was NAD the first time it considered this issue (issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#73">73</a>), but now thinks otherwise. The corresponding streambuf +member function, after all,is already const.</p> + +<p>The other proposed changes are less safe, because some streambuf +functions that appear merely to report a value do actually perform +mutating operations. It's not even clear that they should be +considered "logically const", because streambuf has two interfaces, a +public one and a protected one. These functions may, and often do, +change the state as exposed by the protected interface, even if the +state exposed by the public interface is unchanged.</p> + +<p>Note that implementers can make this change in a binary compatible +way by providing both overloads; this would be a conforming extension.</p> + <hr> <a name="366"><h3>366. Excessive const-qualification</h3></a><p> -<b>Section:</b> 27 <a href="lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Walter Brown <b>Date:</b> 10 May 2002</p> +<b>Section:</b> 27 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Walter Brown, Marc Paterno <b>Date:</b> 10 May 2002</p> <p> The following member functions are declared const, yet return non-const pointers. We believe they are should be changed, because they allow code that may surprise the user. See document N1360 for details and rationale. </p> + +<p><i>[Santa Cruz: the real issue is that we've got const member +functions that return pointers to non-const, and N1360 proposes +replacing them by overloaded pairs. There isn't a consensus about +whether this is a real issue, since we've never said what our +constness policy is for iostreams. N1360 relies on a distinction +between physical constness and logical constness; that distinction, or +those terms, does not appear in the standard.]</i></p> + <p><b>Proposed resolution:</b></p> <p>In 27.4.4 and 27.4.4.2</p> <p>Replace</p> -<pre> - basic_ostream<charT,traits>* tie() const; +<pre> basic_ostream<charT,traits>* tie() const; </pre> <p>with</p> -<pre> - basic_ostream<charT,traits>* tie(); +<pre> basic_ostream<charT,traits>* tie(); const basic_ostream<charT,traits>* tie() const; </pre> <p>and replace</p> -<pre> - basic_streambuf<charT,traits>* rdbuf() const; +<pre> basic_streambuf<charT,traits>* rdbuf() const; </pre> <p>with</p> -<pre> - basic_streambuf<charT,traits>* rdbuf(); +<pre> basic_streambuf<charT,traits>* rdbuf(); const basic_streambuf<charT,traits>* rdbuf() const; </pre> <p>In 27.5.2 and 27.5.2.3.1</p> <p>Replace</p> -<pre> - char_type* eback() const; +<pre> char_type* eback() const; </pre> <p>with</p> -<pre> - char_type* eback(); +<pre> char_type* eback(); const char_type* eback() const; </pre> <p>Replace</p> -<pre> - char_type gptr() const; +<pre> char_type gptr() const; </pre> <p>with</p> -<pre> - char_type* gptr(); +<pre> char_type* gptr(); const char_type* gptr() const; </pre> <p>Replace</p> -<pre> - char_type* egptr() const; +<pre> char_type* egptr() const; </pre> <p>with</p> -<pre> - char_type* egptr(); +<pre> char_type* egptr(); const char_type* egptr() const; </pre> <p>In 27.5.2 and 27.5.2.3.2</p> <p>Replace</p> -<pre> - char_type* pbase() const; +<pre> char_type* pbase() const; </pre> <p>with</p> -<pre> - char_type* pbase(); +<pre> char_type* pbase(); const char_type* pbase() const; </pre> <p>Replace</p> -<pre> - char_type* pptr() const; +<pre> char_type* pptr() const; </pre> <p>with</p> -<pre> - char_type* pptr(); +<pre> char_type* pptr(); const char_type* pptr() const; </pre> <p>Replace</p> -<pre> - char_type* epptr() const; +<pre> char_type* epptr() const; </pre> <p>with</p> -<pre> - char_type* epptr(); +<pre> char_type* epptr(); const char_type* epptr() const; </pre> <p>In 27.7.2, 27.7.2.2, 27.7.3 27.7.3.2, 27.7.4, and 27.7.6</p> <p>Replace</p> -<pre> - basic_stringbuf<charT,traits,Allocator>* rdbuf() const; +<pre> basic_stringbuf<charT,traits,Allocator>* rdbuf() const; </pre> <p>with</p> -<pre> - basic_stringbuf<charT,traits,Allocator>* rdbuf(); +<pre> basic_stringbuf<charT,traits,Allocator>* rdbuf(); const basic_stringbuf<charT,traits,Allocator>* rdbuf() const; </pre> <p>In 27.8.1.5, 27.8.1.7, 27.8.1.8, 27.8.1.10, 27.8.1.11, and 27.8.1.13</p> <p>Replace</p> -<pre> - basic_filebuf<charT,traits>* rdbuf() const; +<pre> basic_filebuf<charT,traits>* rdbuf() const; </pre> <p>with</p> -<pre> - basic_filebuf<charT,traits>* rdbuf(); +<pre> basic_filebuf<charT,traits>* rdbuf(); const basic_filebuf<charT,traits>* rdbuf() const; </pre> <hr> -<a name="367"><h3>367. remove_copy/remove_copy_if and Input Iterators</h3></a><p> -<b>Section:</b> 25.2.7 <a href="lib-algorithms.html#lib.alg.remove"> [lib.alg.remove]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Anthony Williams <b>Date:</b> 13 May 2002</p> -<p> -remove_copy and remove_copy_if (25.2.7 <a href="lib-algorithms.html#lib.alg.remove"> [lib.alg.remove]</a>) permit their -input range to be marked with Input Iterators. However, since two -operations are required against the elements to copy (comparison and -assigment), when the input range uses Input Iterators, a temporary -copy must be taken to avoid dereferencing the iterator twice. This -therefore requires the value type of the InputIterator to be -CopyConstructible. If the iterators are at least Forward Iterators, -then the iterator can be dereferenced twice, or a reference to the -result maintained, so the temporary is not required. -</p> -<p><b>Proposed resolution:</b></p> -<p> -Add "If InputIterator does not meet the requirements of forward -iterator, then the value type of InputIterator must be copy -constructible. Otherwise copy constructible is not required." to -25.2.7 <a href="lib-algorithms.html#lib.alg.remove"> [lib.alg.remove]</a> paragraph 6. -</p> -<hr> -<a name="368"><h3>368. basic_string::replace has two "Throws" paragraphs</h3></a><p> -<b>Section:</b> 21.3.5.6 <a href="lib-strings.html#lib.string::replace"> [lib.string::replace]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 3 Jun 2002</p> +<a name="368"><h3>368. basic_string::replace has two "Throws" paragraphs</h3></a><p> +<b>Section:</b> 21.3.5.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::replace"> [lib.string::replace]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 3 Jun 2002</p> <p> -21.3.5.6 <a href="lib-strings.html#lib.string::replace"> [lib.string::replace]</a> basic_string::replace, second -signature, given in paragraph 1, has two "Throws" paragraphs (3 and +21.3.5.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::replace"> [lib.string::replace]</a> basic_string::replace, second +signature, given in paragraph 1, has two "Throws" paragraphs (3 and 5). </p> <p> -In addition, the second "Throws" paragraph (5) includes specification -(beginning with "Otherwise, the function replaces ...") that should be -part of the "Effects" paragraph. +In addition, the second "Throws" paragraph (5) includes specification +(beginning with "Otherwise, the function replaces ...") that should be +part of the "Effects" paragraph. </p> <p><b>Proposed resolution:</b></p> +<p><i>[This is a typo that escalated. It's clear that what's in the + Standard is wrong. It's less clear what the fix ought to be. + Someone who understands string replace well needs to work on + this.]</i></p> <hr> <a name="369"><h3>369. io stream objects and static ctors</h3></a><p> -<b>Section:</b> 27.3 <a href="lib-iostreams.html#lib.iostream.objects"> [lib.iostream.objects]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Ruslan Abdikeev <b>Date:</b> 8 Jul 2002</p> +<b>Section:</b> 27.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostream.objects"> [lib.iostream.objects]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Ruslan Abdikeev <b>Date:</b> 8 Jul 2002</p> <p> Is it safe to use standard iostream objects from constructors of static objects? Are standard iostream objects constructed and are @@ -5408,11 +3357,11 @@ iostream objects from constructors of static objects. be discussed below:</p> <blockquote> - "The [standard iostream] objects are constructed, and their + "The [standard iostream] objects are constructed, and their associations are established at some time prior to or during first time an object of class basic_ios<charT,traits>::Init is constructed, and in any case before the body of main - begins execution." (27.3/2 [lib.iostream.objects]) + begins execution." (27.3/2 [lib.iostream.objects]) </blockquote> <p> @@ -5424,9 +3373,9 @@ to initialize standard iostream objects earlier than required. and unsupported claim:</p> <blockquote> - "Constructors and destructors for static objects can access these + "Constructors and destructors for static objects can access these [standard iostream] objects to read input from stdin or write output - to stdout or stderr." (27.3/2 footnote 265 [lib.iostream.objects]) + to stdout or stderr." (27.3/2 footnote 265 [lib.iostream.objects]) </blockquote> <p> @@ -5445,54 +3394,36 @@ mention of an _instance_ of ios_base::Init in Standard. </p> <p><b>Proposed resolution:</b></p> <p> -At the end of header <iostream> synopsis in 27.3 <a href="lib-iostreams.html#lib.iostream.objects"> [lib.iostream.objects]</a> +At the end of header <iostream> synopsis in 27.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostream.objects"> [lib.iostream.objects]</a> </p> -<pre> - namespace std +<pre> namespace std { ... extern istream cin; ... </pre> <p>add the following lines</p> -<pre> - namespace +<pre> namespace { ios_base::Init <some_implementation_defined_name>; } } </pre> -<hr> -<a name="370"><h3>370. Minor error in basic_istream::get</h3></a><p> -<b>Section:</b> 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Ray Lischner <b>Date:</b> 15 Jul 2002</p> -<p>Defect report for description of basic_istream::get (section 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>), paragraph 15. The description for the get function -with the following signature:</p> - -<pre> - basic_istream<charT,traits>& get(basic_streambuf<char_type,traits>& - sb); -</pre> -<p>is incorrect. It reads</p> - -<blockquote> - Effects: Calls get(s,n,widen('\n')) -</blockquote> +<p><i>[Santa Cruz: The LWG is leaning toward NAD. There isn't any +normative wording saying that the Init scheme will be used, but that +is probably intentional. Implementers use dirty tricks for iostream +initialization, and doing it portably is somewhere between difficult +and impossible. Too much constraint in this area is dangerous, and if +we are to make any changes it would probably be more appropriate +forthem to be nonnormative. Martin will try to come up with clearer +wording that expreses this intent.]</i></p> -<p>which I believe should be:</p> -<blockquote> - Effects: Calls get(sb,widen('\n')) -</blockquote> -<p><b>Proposed resolution:</b></p> -<p>Change the <b>Effects</b> paragraph to:</p> -<blockquote> - Effects: Calls get(sb,widen('\n')) -</blockquote> <hr> <a name="371"><h3>371. Stability of multiset and multimap member functions</h3></a><p> -<b>Section:</b> 23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Frank Compagner <b>Date:</b> 20 Jul 2002</p> +<b>Section:</b> 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Frank Compagner <b>Date:</b> 20 Jul 2002</p> <p> The requirements for multiset and multimap containers (23.1 [lib.containers.requirements], 23.1.2 [lib.associative.reqmnts], @@ -5509,8 +3440,7 @@ following 'idiom' that removes elements based on a certain predicate function. </p> -<pre> - multimap<int, int> m; +<pre> multimap<int, int> m; multimap<int, int>::iterator i = m.begin(); while (i != m.end()) { if (pred(i)) @@ -5545,77 +3475,18 @@ be hard to track down by users. This would also make the need for an erase_if() member function that much greater. </p> -<p>This issue is somewhat related to LWG issue <a href="lwg-closed.html#130">130</a>.</p> -<p><b>Proposed resolution:</b></p> -<hr> -<a name="372"><h3>372. Inconsistent description of stdlib exceptions</h3></a><p> -<b>Section:</b> 17.4.4.8 <a href="lib-intro.html#lib.res.on.exception.handling"> [lib.res.on.exception.handling]</a>, 18.6.1 <a href="lib-support.html#lib.exception"> [lib.exception]</a>, <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Randy Maddox <b>Date:</b> 22 Jul 2002</p> - -<p>Paragraph 3 under clause 17.4.4.8 <a href="lib-intro.html#lib.res.on.exception.handling"> [lib.res.on.exception.handling]</a>, Restrictions on -Exception Handling, states that "Any other functions defined in the -C++ Standard Library that do not have an exception-specification may -throw implementation-defined exceptions unless otherwise specified." -This statement is followed by a reference to footnote 178 at the -bottom of that page which states, apparently in reference to the C++ -Standard Library, that "Library implementations are encouraged (but -not required) to report errors by throwing exceptions from (or derived -from) the standard exceptions."</p> - -<p>These statements appear to be in direct contradiction to clause -18.6.1 <a href="lib-support.html#lib.exception"> [lib.exception]</a>, which states "The class exception defines the -base class for the types of objects thrown as exceptions by the C++ -Standard library components ...".</p> - -<p>Is this inconsistent?</p> +<p>This issue is somewhat related to LWG issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#130">130</a>.</p> -<p><b>Proposed resolution:</b></p> -<hr> -<a name="373"><h3>373. Are basic_istream and basic_ostream to use (exceptions()&badbit) != 0 ?</h3></a><p> -<b>Section:</b> 27.6.1.2.1 <a href="lib-iostreams.html#lib.istream.formatted.reqmts"> [lib.istream.formatted.reqmts]</a>, 27.6.2.5.1 <a href="lib-iostreams.html#lib.ostream.formatted.reqmts"> [lib.ostream.formatted.reqmts]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Keith Baker <b>Date:</b> 23 Jul 2002</p> +<p><i>[Santa Cruz: More people need to look at this. Much user code + may assume stability. On the other hand, it seems drastic to add a + new requirement now.]</i></p> -<p> -In 27.6.1.2.1 <a href="lib-iostreams.html#lib.istream.formatted.reqmts"> [lib.istream.formatted.reqmts]</a> and 27.6.2.5.1 <a href="lib-iostreams.html#lib.ostream.formatted.reqmts"> [lib.ostream.formatted.reqmts]</a> -(exception()&badbit) != 0 is used in testing for rethrow, yet -exception() is the constructor to class std::exception in 18.6.1 <a href="lib-support.html#lib.exception"> [lib.exception]</a> that has no return type. Should member function -exceptions() found in 27.4.4 <a href="lib-iostreams.html#lib.ios"> [lib.ios]</a> be used instead? -</p> - -<p><b>Proposed resolution:</b></p> -<p> -</p> -<hr> -<a name="374"><h3>374. moneypunct::frac_digits returns int not unsigned</h3></a><p> -<b>Section:</b> 22.2.6.3.1 <a href="lib-locales.html#lib.locale.moneypunct.members"> [lib.locale.moneypunct.members]</a>, 22.2.6.3.2 <a href="lib-locales.html#lib.locale.moneypunct.virtuals"> [lib.locale.moneypunct.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Ray Lischner <b>Date:</b> 8 Aug 2002</p> -<p> -In section 22.2.6.3.1 <a href="lib-locales.html#lib.locale.moneypunct.members"> [lib.locale.moneypunct.members]</a>, frac_digits() returns type -"int". This implies that frac_digits() might return a negative value, -but a negative value is nonsensical. It should return "unsigned". -</p> - -<p> -Similarly, in section 22.2.6.3.2 <a href="lib-locales.html#lib.locale.moneypunct.virtuals"> [lib.locale.moneypunct.virtuals]</a>, do_frac_digits() -should return "unsigned". -</p> - -<p><b>Proposed resolution:</b></p> -<hr> -<a name="375"><h3>375. basic_ios should be ios_base in 27.7.1.3</h3></a><p> -<b>Section:</b> 27.7.1.3 <a href="lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Ray Lischner <b>Date:</b> 14 Aug 2002</p> -<p> -In Section 27.7.1.3 <a href="lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a>: Table 90, Table 91, and paragraph -14 all contain references to "basic_ios::" which should be -"ios_base::". -</p> <p><b>Proposed resolution:</b></p> -<p> -Change all references to "basic_ios" in Table 90, Table 91, and -paragraph 14 to "ios_base". -</p> <hr> <a name="376"><h3>376. basic_streambuf semantics</h3></a><p> -<b>Section:</b> 27.7.1.3 <a href="lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Ray Lischner <b>Date:</b> 14 Aug 2002</p> +<b>Section:</b> 27.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Ray Lischner <b>Date:</b> 14 Aug 2002</p> <p> -In Section 27.7.1.3 <a href="lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a>, Table 90, the implication is that +In Section 27.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a>, Table 90, the implication is that the four conditions should be mutually exclusive, but they are not. The first two cases, as written, are subcases of the third. I think it would be clearer if the conditions were rewritten as follows: @@ -5648,35 +3519,24 @@ are true, but case 3 is false, e.g., seekoff(0, ios_base::cur, ios_base::in | ios_base::out) </blockquote> -<p><b>Proposed resolution:</b></p> -<hr> -<a name="377"><h3>377. basic_string::insert and length_error</h3></a><p> -<b>Section:</b> 21.3.5.4 <a href="lib-strings.html#lib.string::insert"> [lib.string::insert]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Ray Lischner <b>Date:</b> 16 Aug 2002</p> -<p> -Section 21.3.5.4 <a href="lib-strings.html#lib.string::insert"> [lib.string::insert]</a>, paragraph 4, contains the following, -"Then throws length_error if size() >= npos - rlen." -</p> +<p><i>[Santa Cruz: The ambiguity seems real. We need to do a survey of +implementations before we decide on a solution.]</i></p> -<p> -Related to DR 83, this sentence should probably be removed. -</p> <p><b>Proposed resolution:</b></p> <hr> <a name="378"><h3>378. locale immutability and locale::operator=()</h3></a><p> -<b>Section:</b> 22.1.1 <a href="lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 6 Sep 2002</p> +<b>Section:</b> 22.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 6 Sep 2002</p> <p> I think there is a problem with 22.1.1, p6 which says that </p> -<pre> - -6- An instance of locale is immutable; once a facet reference +<pre> -6- An instance of locale is immutable; once a facet reference is obtained from it, that reference remains usable as long as the locale value itself exists. </pre> <p> and 22.1.1.2, p4: </p> -<pre> - const locale& operator=(const locale& other) throw(); +<pre> const locale& operator=(const locale& other) throw(); -4- Effects: Creates a copy of other, replacing the current value. </pre> @@ -5685,10 +3545,9 @@ How can a reference to a facet obtained from a locale object remain valid after an assignment that clearly must replace all the facets in the locale object? Imagine a program such as this </p> -<pre> - std::locale loc ("de_DE"); +<pre> std::locale loc ("de_DE"); const std::ctype<char> &r0 = std::use_facet<std::ctype<char> >(loc); - loc = std::locale ("en_US"); + loc = std::locale ("en_US"); const std::ctype<char> &r1 = std::use_facet<std::ctype<char> >(loc); </pre> <p> @@ -5697,23 +3556,26 @@ out of scope? </p> <p><b>Proposed resolution:</b></p> <p> -Suggest to replace 22.1.1 <a href="lib-locales.html#lib.locale"> [lib.locale]</a>, p6 with +Suggest to replace 22.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale"> [lib.locale]</a>, p6 with </p> -<pre> - -6- Unless assigned a new value, locale objects are immutable; +<pre> -6- Unless assigned a new value, locale objects are immutable; once a facet reference is obtained from it, that reference remains usable as long as the locale object itself exists or until the locale object is assigned the value of another, distinct locale object. </pre> + +<p><i>[Santa Cruz: Dietmar agrees with this general direction, but is +uncomfortable about the proposed wording. He and Martin will try to +come up with better wording.]</i></p> + <hr> <a name="379"><h3>379. nonsensical ctype::do_widen() requirement</h3></a><p> -<b>Section:</b> 22.2.1.1.2 <a href="lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 6 Sep 2002</p> +<b>Section:</b> 22.2.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 6 Sep 2002</p> <p> The last sentence in 22.2.1.1.2, p11 below doesn't seem to make sense. </p> -<pre> - charT do_widen (char c) const; +<pre> charT do_widen (char c) const; -11- Effects: Applies the simplest reasonable transformation from a char value or sequence of char values to the corresponding @@ -5726,8 +3588,7 @@ The last sentence in 22.2.1.1.2, p11 below doesn't seem to make sense. <p> Shouldn't the last sentence instead read </p> -<pre> - For any named ctype category with a ctype<char> facet ctc +<pre> For any named ctype category with a ctype<char> facet ctc and valid ctype_base::mask value M (ctc.is(M, c) || !is(M, do_widen(c))) is true. </pre> @@ -5738,98 +3599,18 @@ footnote 224.) </p> <p><b>Proposed resolution:</b></p> <p> -Replace the last sentence of 22.2.1.1.2 <a href="lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a>, p11 with the +Replace the last sentence of 22.2.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a>, p11 with the following text: </p> -<pre> - For any named ctype category with a ctype<char> facet ctc +<pre> For any named ctype category with a ctype<char> facet ctc and valid ctype_base::mask value M (ctc.is(M, c) || !is(M, do_widen(c))) is true. </pre> -<hr> -<a name="380"><h3>380. typos in codecvt tables 53 and 54</h3></a><p> -<b>Section:</b> 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 6 Sep 2002</p> -<p> -Tables 53 and 54 in 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> are both titled "convert -result values," when surely "do_in/do_out result values" must have -been intended for Table 53 and "do_unshift result values" for Table -54. -</p> -<p> -Table 54, row 3 says that the meaning of partial is "more characters -needed to be supplied to complete termination." The function is not -supplied any characters, it is given a buffer which it fills with -characters or, more precisely, destination elements (i.e., an escape -sequence). So partial means that space for more than (to_limit - to) -destination elements was needed to terminate a sequence given the -value of state. -</p> -<p><b>Proposed resolution:</b></p> -<p> -Change the title of Table 53 to "do_in/do_out result values" and -the title of Table 54 to "do_unshift result values." -</p> -<p> -Change the text in Table 54, row 3, under the heading Meaning to -"space for more than (to_limit - to) destination elements was -needed to terminate a sequence given the value of state." -</p> -<hr> -<a name="381"><h3>381. detection of invalid mbstate_t in codecvt</h3></a><p> -<b>Section:</b> 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 6 Sep 2002</p> -<p> -All but one codecvt member functions that take a state_type argument -list as one of their preconditions that the state_type argument have -a valid value. However, according to 22.2.1.5.2, p6, -codecvt::do_unshift() is the only codecvt member that is supposed to -return error if the state_type object is invalid. -</p> - -<p> -It seems to me that the treatment of state_type by all codecvt member -functions should be the same and the current requirements should be -changed. Since the detection of invalid state_type values may be -difficult in general or computationally expensive in some specific -cases, I propose the following: -</p> -<p><b>Proposed resolution:</b></p> -<p> -Add a new paragraph before 22.2.1.5.2, p5, and after the function -declaration below -</p> -<pre> - result do_unshift(stateT& state, - externT* to, externT* to_limit, externT*& to_next) const; -</pre> -<p> -as follows: -</p> -<pre> - Requires: (to <= to_end) well defined and true; state initialized, - if at the beginning of a sequence, or else equal to the result of - converting the preceding characters in the sequence. -</pre> -<p> -and change the text in Table 54, row 4, under the heading Meaning -from -</p> -<pre> - state has invalid value -</pre> -<p> -to -</p> -<pre> - an unspecified error has occurred -</pre> -<p> -The return value of error should allow implementers to detect and -report invalid state values but shouldn't require it, hence the -word "unspecified" in the new wording. -</p> +<p><b>Rationale:</b></p> +<p>The LWG believes this is just a typo, and that this is the correct fix.</p> <hr> <a name="382"><h3>382. codecvt do_in/out result</h3></a><p> -<b>Section:</b> 22.2.1.5 <a href="lib-locales.html#lib.locale.codecvt"> [lib.locale.codecvt]</a> <b>Status:</b> <a href="lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 30 Aug 2002</p> +<b>Section:</b> 22.2.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt"> [lib.locale.codecvt]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 30 Aug 2002</p> <p> It seems that the descriptions of codecvt do_in() and do_out() leave sufficient room for interpretation so that two implementations of @@ -5854,32 +3635,32 @@ the following seems less than adequately specified: <ol> <li> - 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, p2 says this about the effects of the + 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, p2 says this about the effects of the function: ...Stops if it encounters a character it cannot convert... This assumes that there *is* a character to convert. What happens when there is a sequence that doesn't form a valid source character, such as an unassigned or invalid UNICODE character, or a sequence that cannot possibly form a character - (e.g., the sequence "\xc0\xff" in UTF-8)? + (e.g., the sequence "\xc0\xff" in UTF-8)? </li> <li> Table 53 says that the function returns codecvt_base::ok - to indicate that the function(s) "completed the conversion." - Suppose that the source sequence is "\xc0\x80" in UTF-8, + to indicate that the function(s) "completed the conversion." + Suppose that the source sequence is "\xc0\x80" in UTF-8, with from pointing to '\xc0' and (from_end==from + 1). It is not clear whether the return value should be ok or partial (see below). </li> <li> Table 53 says that the function returns codecvt_base::partial - if "not all source characters converted." With the from pointers + if "not all source characters converted." With the from pointers set up the same way as above, it is not clear whether the return value should be partial or ok (see above). </li> <li> Table 53, in the row describing the meaning of error mistakenly - refers to a "from_type" character, without the symbol from_type - having been defined. Most likely, the word "source" character + refers to a "from_type" character, without the symbol from_type + having been defined. Most likely, the word "source" character is intended, although that is not sufficient. The functions may also fail when they encounter an invalid source sequence that cannot possibly form a valid source character (e.g., as @@ -5887,21 +3668,21 @@ the following seems less than adequately specified: </li> </ol> <p> -Finally, the conditions described at the end of 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, p4 don't seem to be possible: +Finally, the conditions described at the end of 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, p4 don't seem to be possible: </p> <blockquote> - "A return value of partial, if (from_next == from_end), + "A return value of partial, if (from_next == from_end), indicates that either the destination sequence has not absorbed all the available destination elements, or that additional source elements are needed before another - destination element can be produced." + destination element can be produced." </blockquote> <p> If the value is partial, it's not clear to me that (from_next ==from_end) could ever hold if there isn't enough room in the destination buffer. In order for (from_next==from_end) to hold, all characters in that range must have been successfully -converted (according to 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, p2) and since there are no +converted (according to 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, p2) and since there are no further source characters to convert, no more room in the destination buffer can be needed. </p> @@ -5909,8 +3690,8 @@ destination buffer can be needed. It's also not clear to me that (from_next==from_end) could ever hold if additional source elements are needed to produce another destination character (not element as incorrectly stated in the -text). partial is returned if "not all source characters have -been converted" according to Table 53, which also implies that +text). partial is returned if "not all source characters have +been converted" according to Table 53, which also implies that (from_next==from) does NOT hold. </p> <p> @@ -5919,7 +3700,7 @@ Could it be that the intended qualifying condition was actually to read </p> <blockquote> - "A return value of partial, if (from_next != from_end),..." + "A return value of partial, if (from_next != from_end),..." </blockquote> <p> which would make perfect sense, since, as far as I understand it, @@ -5931,11 +3712,10 @@ To address these issues, I propose that paragraphs 2, 3, and 4 be rewritten as follows. The proposal incorporates the accepted resolution of lwg issue 19. </p> -<pre> --2- Effects: Converts characters in the range of source elements +<pre>-2- Effects: Converts characters in the range of source elements [from, from_end), placing the results in sequential positions - starting at destination to. Converts no more than (from_end­from) - source elements, and stores no more than (to_limit­to) + starting at destination to. Converts no more than (from_end from) + source elements, and stores no more than (to_limit to) destination elements. Stops if it encounters a sequence of source elements it cannot @@ -5983,6 +3763,2134 @@ resolution of lwg issue 19. source elements are needed before another destination character can be produced. </pre> + +<p><i>[Santa Cruz: The LWG agrees that this is an important issue and +that this general direction is probably correct. Dietmar, Howard, +PJP, and Matt will review this wording.]</i></p> + +<hr> +<a name="384"><h3>384. equal_range has unimplementable runtime complexity</h3></a><p> +<b>Section:</b> 25.3.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.equal.range"> [lib.equal.range]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Hans Bos <b>Date:</b> 18 Oct 2002</p> +<p> +Section 25.3.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.equal.range"> [lib.equal.range]</a> +states that at most 2 * log(last - first) + 1 +comparisons are allowed for equal_range. +</p> + +<p>It is not possible to implement equal_range with these constraints.</p> + +<p>In a range of one element as in:</p> +<pre> int x = 1; + equal_range(&x, &x + 1, 1) +</pre> + +<p>it is easy to see that at least 2 comparison operations are needed.</p> + +<p>For this case at most 2 * log(1) + 1 = 1 comparison is allowed.</p> + +<p>I have checked a few libraries and they all use the same (nonconforming) +algorithm for equal_range that has a complexity of</p> +<pre> 2* log(distance(first, last)) + 2. +</pre> +<p>I guess this is the algorithm that the standard assumes for equal_range.</p> + +<p> +It is easy to see that 2 * log(distance) + 2 comparisons are enough +since equal range can be implemented with lower_bound and upper_bound +(both log(distance) + 1). +</p> + +<p> +I think it is better to require something like 2log(distance) + O(1) (or +even logarithmic as multiset::equal_range). +Then an implementation has more room to optimize for certain cases (e.g. +have log(distance) characteristics when at most match is found in the range +but 2log(distance) + 4 for the worst case). +</p> + +<p><i>[Santa Cruz: The issue is real, but of greater scope than just +equal_range: it affects all of the binary search algorithms. What is +the complexity supposed to be for ranges of 0 or 1 elements? What +base are we using for the logarithm? Are these bounds supposed to be +exact, or asymptotic? (If the latter, of course, then none of the +other questions matter.)]</i></p> + +<p><b>Proposed resolution:</b></p> +<hr> +<a name="385"><h3>385. Does call by value imply the CopyConstructible requirement?</h3></a><p> +<b>Section:</b> 17 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.library"> [lib.library]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 23 Oct 2002</p> +<p> +Many function templates have parameters that are passed by value; +a typical example is <tt>find_if</tt>'s <i>pred</i> parameter in +25.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.find"> [lib.alg.find]</a>. Are the corresponding template parameters +(<tt>Predicate</tt> in this case) implicitly required to be +CopyConstructible, or does that need to be spelled out explicitly? +</p> + +<p> +This isn't quite as silly a question as it might seem to be at first +sight. If you call <tt>find_if</tt> in such a way that template +argument deduction applies, then of course you'll get call by value +and you need to provide a copy constructor. If you explicitly provide +the template arguments, however, you can force call by reference by +writing something like <tt>find_if<my_iterator, +my_predicate&></tt>. The question is whether implementation +are required to accept this, or whether this is ill-formed because +my_predicate& is not CopyConstructible. +</p> + +<p> +The scope of this problem, if it is a problem, is unknown. Function +object arguments to generic algorithms in clauses 25 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a> +and 26 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.numerics"> [lib.numerics]</a> are obvious examples. A review of the whole +library is necessary. +</p> +<p><b>Proposed resolution:</b></p> +<p><i>[ +This is really two issues. First, predicates are typically passed by +value but we don't say they must be Copy Constructible. They should +be. Second: is specialization allowed to transform value arguments +into references? References aren't copy constructible, so this should +not be allowed. +]</i></p> +<hr> +<a name="386"><h3>386. Reverse iterator's operator[] has impossible return type</h3></a><p> +<b>Section:</b> 24.4.1.3.11 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.reverse.iter.opindex"> [lib.reverse.iter.opindex]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 23 Oct 2002</p> +<p>In 24.4.1.3.11 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.reverse.iter.opindex"> [lib.reverse.iter.opindex]</a>, <tt>reverse_iterator<>::operator[]</tt> +is specified as having a return type of <tt>reverse_iterator::reference</tt>, +which is the same as <tt>iterator_traits<Iterator>::reference</tt>. +(Where <tt>Iterator</tt> is the underlying iterator type.)</p> + +<p>The trouble is that <tt>Iterator</tt>'s own operator[] doesn't + necessarily have a return type + of <tt>iterator_traits<Iterator>::reference</tt>. Its + return type is merely required to be convertible + to <tt>Iterator</tt>'s value type. The return type specified for + reverse_iterator's operator[] would thus appear to be impossible.</p> + +<p>Related issue: <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#299">299</a>. Jeremy will work on this.</p> +<p><b>Proposed resolution:</b></p> +<p><i>[ +Comments from Dave Abrahams: IMO we should resolve 386 by just saying + that the return type of reverse_iterator's operator[] is + unspecified, allowing the random access iterator requirements to + impose an appropriate return type. If we accept 299's proposed + resolution (and I think we should), the return type will be + readable and writable, which is about as good as we can do. +]</i></p> +<hr> +<a name="387"><h3>387. std::complex over-encapsulated</h3></a><p> +<b>Section:</b> 26.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.numbers"> [lib.complex.numbers]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Gabriel Dos Reis <b>Date:</b> 8 Nov 2002</p> +<p> +The absence of explicit description of std::complex<T> layout +makes it imposible to reuse existing software developed in traditional +languages like Fortran or C with unambigous and commonly accepted +layout assumptions. There ought to be a way for practitioners to +predict with confidence the layout of std::complex<T> whenever T +is a numerical datatype. The absence of ways to access individual +parts of a std::complex<T> object as lvalues unduly promotes +severe pessimizations. For example, the only way to change, +independently, the real and imaginary parts is to write something like +</p> + +<pre>complex<T> z; +// ... +// set the real part to r +z = complex<T>(r, z.imag()); +// ... +// set the imaginary part to i +z = complex<T>(z.real(), i); +</pre> + +<p> +At this point, it seems appropriate to recall that a complex number +is, in effect, just a pair of numbers with no particular invariant to +maintain. Existing practice in numerical computations has it that a +complex number datatype is usually represented by Cartesian +coordinates. Therefore the over-encapsulation put in the specification +of std::complex<> is not justified. +</p> + +<p><b>Proposed resolution:</b></p> +<p>Add the following requirements to 26.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.numbers"> [lib.complex.numbers]</a> as 26.2/4:</p> +<blockquote> +<p>If z is an lvalue expression of type cv std::complex<T> then</p> + +<ul> +<li>the expression reinterpret_cast<cv T(&)[2]>(z) +is well-formed; and</li> +<li>reinterpret_cast<cvT(&)[2]>(z)[0]designates the +real part of z; and</li> +<li>reinterpret_cast<cvT(&)[2]>(z)[1]designates the +imaginary part of z.</li> +</ul> + +<p> +Moreover, if a is an expression of pointer type cv complex<T>* +and the expression a[i] is well-defined for an integer expression +i then: +</p> + +<ul> +<li>reinterpret_cast<cvT*>(a)[2+i] designates the real +part of a[i]; and</li> +<li>reinterpret_cast<cv T*>(a)[2+i+1] designates the +imaginary part of a[i].</li> +</ul> +</blockquote> + +<p>In the header synopsis in 26.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.synopsis"> [lib.complex.synopsis]</a>, replace</p> +<pre> template<class T> T real(const complex<T>&); + template<class T> T imag(const complex<T>&); +</pre> + +<p>with</p> + +<pre> template<class T> const T& real(const complex<T>&); + template<class T> T& real( complex<T>&); + template<class T> const T& imag(const complex<T>&); + template<class T> T& imag( complex<T>&); +</pre> + +<p>In 26.2.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.value.ops"> [lib.complex.value.ops]</a> paragraph 1, change</p> +<pre> template<class T> T real(const complex<T>&); +</pre> +<p>to</p> +<pre> template<class T> const T& real(const complex<T>&); + template<class T> T& real( complex<T>&); +</pre> +<p>and change the <b>Returns</b> clause to "<b>Returns:</b> The real +part of <i>x</i> +</p>. + +<p>In 26.2.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.value.ops"> [lib.complex.value.ops]</a> paragraph 2, change</p> +<pre> template<class T> T imag(const complex<T>&); +</pre> +<p>to</p> +<pre> template<class T> const T& imag(const complex<T>&); + template<class T> T& imag( complex<T>&); +</pre> +<p>and change the <b>Returns</b> clause to "<b>Returns:</b> The imaginary +part of <i>x</i> +</p>. + + +<p><b>Rationale:</b></p> +<p>The LWG believes that C99 compatibility would be enough +justification for this change even without other considerations. All +existing implementations already have the layout proposed here.</p> +<hr> +<a name="389"><h3>389. Const overload of valarray::operator[] returns by value</h3></a><p> +<b>Section:</b> 26.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.valarray"> [lib.template.valarray]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Gabriel Dos Reis <b>Date:</b> 8 Nov 2002</p> +<p>Consider the following program:</p> +<pre> #include <iostream> + #include <ostream> + #include <vector> + #include <valarray> + #include <algorithm> + #include <iterator> + template<typename Array> + void print(const Array& a) + { + using namespace std; + typedef typename Array::value_type T; + copy(&a[0], &a[0] + a.size(), + ostream_iterator<T>(std::cout, " ")); + } + template<typename T, unsigned N> + unsigned size(T(&)[N]) { return N; } + int main() + { + double array[] = { 0.89, 9.3, 7, 6.23 }; + std::vector<double> v(array, array + size(array)); + std::valarray<double> w(array, size(array)); + print(v); // #1 + std::cout << std::endl; + print(w); // #2 + std::cout << std::endl; + } +</pre> + +<p>While the call numbered #1 succeeds, the call numbered #2 fails +because the const version of the member function +valarray<T>::operator[](size_t) returns a value instead of a +const-reference. That seems to be so for no apparent reason, no +benefit. Not only does that defeats users' expectation but it also +does hinder existing software (written either in C or Fortran) +integration within programs written in C++. There is no reason why +subscripting an expression of type valarray<T> that is const-qualified +should not return a const T&.</p> +<p><b>Proposed resolution:</b></p> +<p>In the class synopsis in 26.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.valarray"> [lib.template.valarray]</a>, and in +26.3.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.valarray.access"> [lib.valarray.access]</a> just above paragraph 1, change</p> +<pre> T operator[](size_t const;) +</pre> +<p>to</p> +<pre> const T& operator[](size_t const;) +</pre> + +<p><b>Rationale:</b></p> +<p>Return by value seems to serve no purpose. Valaray was explicitly +designed to have a specified layout so that it could easily be +integrated with libraries in other languages, and return by value +defeats that purpose. It is believed that this change will have no +impact on allowable optimizations.</p> +<hr> +<a name="391"><h3>391. non-member functions specified as const</h3></a><p> +<b>Section:</b> 22.1.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.conversions"> [lib.conversions]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> James Kanze <b>Date:</b> 10 Dec 2002</p> +<p> +The specifications of toupper and tolower both specify the functions as +const, althought they are not member functions, and are not specified as +const in the header file synopsis in section 22.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locales"> [lib.locales]</a>. +</p> +<p><b>Proposed resolution:</b></p> +<p>In 22.1.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.conversions"> [lib.conversions]</a>, remove <tt>const</tt> from the function + declarations of std::toupper and std::tolower</p> +<p><b>Rationale:</b></p> +<p>Fixes an obvious typo</p> +<hr> +<a name="394"><h3>394. behavior of formatted output on failure</h3></a><p> +<b>Section:</b> 27.6.2.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.formatted"> [lib.ostream.formatted]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 27 Dec 2002</p> +<p> +There is a contradiction in Formatted output about what bit is +supposed to be set if the formatting fails. On sentence says it's +badbit and another that it's failbit. +</p> +<p> +27.6.2.5.1, p1 says in the Common Requirements on Formatted output +functions: +</p><pre> ... If the generation fails, then the formatted output function + does setstate(ios::failbit), which might throw an exception. +</pre> +<p></p> +<p> +27.6.2.5.2, p1 goes on to say this about Arithmetic Inserters: +</p> +<p> + ... The formatting conversion occurs as if it performed the + following code fragment: +</p> +<p> +</p><pre> bool failed = + use_facet<num_put<charT,ostreambuf_iterator<charT,traits> + > > + (getloc()).put(*this, *this, fill(), val). failed(); + + ... If failed is true then does setstate(badbit) ... +</pre> +<p></p> +<p> +The original intent of the text, according to Jerry Schwarz (see +c++std-lib-10500), is captured in the following paragraph: +</p> +<p> +In general "badbit" should mean that the stream is unusable because +of some underlying failure, such as disk full or socket closure; +"failbit" should mean that the requested formatting wasn't possible +because of some inconsistency such as negative widths. So typically +if you clear badbit and try to output something else you'll fail +again, but if you clear failbit and try to output something else +you'll succeed. +</p> +<p> +In the case of the arithmetic inserters, since num_put cannot +report failure by any means other than exceptions (in response +to which the stream must set badbit, which prevents the kind of +recoverable error reporting mentioned above), the only other +detectable failure is if the iterator returned from num_put +returns true from failed(). +</p> +<p> +Since that can only happen (at least with the required iostream +specializations) under such conditions as the underlying failure +referred to above (e.g., disk full), setting badbit would seem +to be the appropriate response (indeed, it is required in +27.6.2.5.2, p1). It follows that failbit can never be directly +set by the arithmetic (it can only be set by the sentry object +under some unspecified conditions). +</p> +<p> +The situation is different for other formatted output functions +which can fail as a result of the streambuf functions failing +(they may do so by means other than exceptions), and which are +then required to set failbit. +</p> +<p> +The contradiction, then, is that ostream::operator<<(int) will +set badbit if the disk is full, while operator<<(ostream&, +char) will set failbit under the same conditions. To make the behavior +consistent, the Common requirements sections for the Formatted output +functions should be changed as proposed below. +</p> +<p><b>Proposed resolution:</b></p> +<p> +In paragraph one of section 27.6.2.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.formatted"> [lib.ostream.formatted]</a>, delete the +sentence beginning with "If the generation fails". +</p> +<p><b>Rationale:</b></p> +<p> +There isn't any contradiction here. <tt>put</tt> returns a streambuf iterator. +<tt>failed()</tt> is a member function of the streambuf iterator. If +it's set then that's a streambuf error, not a conversion error. +</p> + +<p> +The real problem isn't that there's a contradiction, but that the "If +the generation fails" part makes little sense. "Generation" isn't +clearly defined. It's not clear what it means for generation to +fail, or even whether it can fail. The intention is probably that +generaion meant formatting, as opposed to character insertion, and +that this sentence was intended as analogous to character parsing. +</p> + +<p>A more precise definition would be that we set failbit if the facet + reports failure. However, the mechanism for the facet reporting + failure is that it sets failbit! Saying that we set failbit if the + facet sets failbit would be silly, so the best thing to say is + nothing.</p> + +<hr> +<a name="395"><h3>395. inconsistencies in the definitions of rand() and random_shuffle()</h3></a><p> +<b>Section:</b> 26.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.c.math"> [lib.c.math]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Review">Review</a> <b>Submitter:</b> James Kanze <b>Date:</b> 3 Jan 2003</p> +<p> +In 26.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.c.math"> [lib.c.math]</a>, the C++ standard refers to the C standard for the +definition of rand(); in the C standard, it is written that "The +implementation shall behave as if no library function calls the rand +function." +</p> + +<p> +In 25.2.11 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.random.shuffle"> [lib.alg.random.shuffle]</a>, there is no specification as to +how the two parameter version of the function generates its random +value. I believe that all current implementations in fact call rand() +(in contradiction with the requirement avove); if an implementation does +not call rand(), there is the question of how whatever random generator +it does use is seeded. Something is missing. +</p> + +<p><b>Proposed resolution:</b></p> +<p> +In [lib.c.math], add a paragraph specifying that the C definition of +rand shal be modified to say that "Unless otherwise specified, the +implementation shall behave as if no library function calls the rand +function." +</p> + +<p> +In [lib.alg.random.shuffle], add a sentence to the effect that "In +the two argument form of the function, the underlying source of +random numbers is implementation defined. [Note: in particular, an +implementation is permitted to use <tt>rand</tt>.] +</p> +<p><b>Rationale:</b></p> +<p>The original proposed resolution proposed requiring the + two-argument from of <tt>random_shuffle</tt> to + use <tt>rand</tt>. We don't want to do that, because some existing + implementations already use something else: gcc + uses <tt>lrand48</tt>, for example. Using <tt>rand</tt> presents a + problem if the number of elements in the sequence is greater than + RAND_MAX.</p> +<hr> +<a name="396"><h3>396. what are characters zero and one</h3></a><p> +<b>Section:</b> 23.3.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.bitset.cons"> [lib.bitset.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 5 Jan 2003</p> + <p> +23.3.5.1, p6 [lib.bitset.cons] talks about a generic character +having the value of 0 or 1 but there is no definition of what +that means for charT other than char and wchar_t. And even for +those two types, the values 0 and 1 are not actually what is +intended -- the values '0' and '1' are. This, along with the +converse problem in the description of to_string() in 23.3.5.2, +p33, looks like a defect remotely related to DR 303. + </p> + <p> +http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#303 + </p> + <pre>23.3.5.1: + -6- An element of the constructed string has value zero if the + corresponding character in str, beginning at position pos, + is 0. Otherwise, the element has the value one. + </pre> + <pre>23.3.5.2: + -33- Effects: Constructs a string object of the appropriate + type and initializes it to a string of length N characters. + Each character is determined by the value of its + corresponding bit position in *this. Character position N + ?- 1 corresponds to bit position zero. Subsequent decreasing + character positions correspond to increasing bit positions. + Bit value zero becomes the character 0, bit value one becomes + the character 1. + </pre> + <p> +Also note the typo in 23.3.5.1, p6: the object under construction +is a bitset, not a string. + </p> + <p><b>Proposed resolution:</b></p> +<p>Change the constructor's function declaration immediately before +23.3.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.bitset.cons"> [lib.bitset.cons]</a> p3 to:</p> +<pre> template <class charT, class traits, class Allocator> + explicit + bitset(const basic_string<charT, traits, Allocator>& str, + typename basic_string<charT, traits, Allocator>::size_type pos = 0, + typename basic_string<charT, traits, Allocator>::size_type n = + basic_string<charT, traits, Allocator>::npos, + charT zero = charT('0')); +</pre> +<p>Change the first two sentences of 23.3.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.bitset.cons"> [lib.bitset.cons]</a> p6 to: "An +element of the constructed string has value 0 if the corresponding +character in <i>str</i>, beginning at position <i>pos</i>, +is <i>zero</i>. Otherwise, the element has the value 1.</p> + +<p>Change the declaration of the <tt>to_string</tt> member function + immediately before 23.3.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.bitset.members"> [lib.bitset.members]</a> p33 to:</p> +<pre> template <class charT, class traits, class Allocator> + basic_string<charT, traits, Allocator> + to_string(charT zero = charT('0'), charT one = charT('1')) const; +</pre> +<p>Change the last sentence of 23.3.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.bitset.members"> [lib.bitset.members]</a> p33 to: "Bit + value 0 becomes the character <tt><i>zero</i></tt>, bit value 1 becomes the + character <tt><i>one</i></tt>.</p> +<p>Change 23.3.5.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.bitset.operators"> [lib.bitset.operators]</a> p8 to:</p> +<p> +<b>Returns</b>:</p> +<pre> os << x.template to_string<charT,traits,allocator<charT> >( + use_facet<ctype<charT> >(<i>os</i>.getloc()).widen('0'), + use_facet<ctype<charT> >(<i>os</i>.getloc()).widen('1')); +</pre> +<p><b>Rationale:</b></p> +<p>There is a real problem here: we need the character values of '0' + and '1', and we have no way to get them since strings don't have + imbued locales. In principle the "right" solution would be to + provide an extra object, either a ctype facet or a full locale, + which would be used to widen '0' and '1'. However, there was some + discomfort about using such a heavyweight mechanism. The proposed + resolution allows those users who care about this issue to get it + right.</p> +<p>We fix the inserter to use the new arguments. Note that we already + fixed the analogous problem with the extractor in issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#303">303</a>.</p> + +<hr> +<a name="397"><h3>397. ostream::sentry dtor throws exceptions</h3></a><p> +<b>Section:</b> 27.6.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream::sentry"> [lib.ostream::sentry]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 5 Jan 2003</p> + <p> +17.4.4.8, p3 prohibits library dtors from throwing exceptions. + </p> + <p> +27.6.2.3, p4 says this about the ostream::sentry dtor: + </p> + <pre> -4- If ((os.flags() & ios_base::unitbuf) && !uncaught_exception()) + is true, calls os.flush(). + </pre> + <p> +27.6.2.6, p7 that describes ostream::flush() says: + </p> + <pre> -7- If rdbuf() is not a null pointer, calls rdbuf()->pubsync(). + If that function returns ?-1 calls setstate(badbit) (which + may throw ios_base::failure (27.4.4.3)). + </pre> + <p> +That seems like a defect, since both pubsync() and setstate() can +throw an exception. + </p> + <p><b>Proposed resolution:</b></p> +<p><i>[ +The contradiction is real. Clause 17 says destructors may never +throw exceptions, and clause 27 specifies a destructor that does +throw. In principle we might change either one. We're leaning +toward changing clause 17: putting in an "unless otherwise specified" +clause, and then putting in a footnote saying the sentry destructor +is the only one that can throw. PJP suggests specifying that +sentry::~sentry() should internally catch any exceptions it might cause. +]</i></p> +<hr> +<a name="398"><h3>398. effects of end-of-file on unformatted input functions</h3></a><p> +<b>Section:</b> 27.6.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream::sentry"> [lib.ostream::sentry]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Open">Open</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 5 Jan 2003</p> + <p> +While reviewing unformatted input member functions of istream +for their behavior when they encounter end-of-file during input +I found that the requirements vary, sometimes unexpectedly, and +in more than one case even contradict established practice (GNU +libstdc++ 3.2, IBM VAC++ 6.0, STLPort 4.5, SunPro 5.3, HP aCC +5.38, Rogue Wave libstd 3.1, and Classic Iostreams). + </p> + <p> +The following unformatted input member functions set eofbit if they +encounter an end-of-file (this is the expected behavior, and also +the behavior of all major implementations): + </p> + <p> + </p><pre> basic_istream<charT, traits>& + get (char_type*, streamsize, char_type); + </pre> + <p></p> + <p> + Also sets failbit if it fails to extract any characters. + </p> + <p> + </p><pre> basic_istream<charT, traits>& + get (char_type*, streamsize); + </pre> + <p></p> + <p> + Also sets failbit if it fails to extract any characters. + </p> + <p> + </p><pre> basic_istream<charT, traits>& + getline (char_type*, streamsize, char_type); + </pre> + <p></p> + <p> + Also sets failbit if it fails to extract any characters. + </p> + <p> + </p><pre> basic_istream<charT, traits>& + getline (char_type*, streamsize); + </pre> + <p></p> + <p> + Also sets failbit if it fails to extract any characters. + </p> + <p> + </p><pre> basic_istream<charT, traits>& + ignore (int, int_type); + </pre> + <p></p> + <p> + </p><pre> basic_istream<charT, traits>& + read (char_type*, streamsize); + </pre> + <p></p> + <p> + Also sets failbit if it encounters end-of-file. + </p> + <p> + </p><pre> streamsize readsome (char_type*, streamsize); + </pre> + <p></p> + + <p> +The following unformated input member functions set failbit but +not eofbit if they encounter an end-of-file (I find this odd +since the functions make it impossible to distinguish a general +failure from a failure due to end-of-file; the requirement is +also in conflict with all major implementation which set both +eofbit and failbit): + </p> + <p> + </p><pre> int_type get(); + </pre> + <p></p> + <p> + </p><pre> basic_istream<charT, traits>& + get (char_type&); + </pre> + <p></p> + <p> +These functions only set failbit of they extract no characters, +otherwise they don't set any bits, even on failure (I find this +inconsistency quite unexpected; the requirement is also in +conflict with all major implementations which set eofbit +whenever they encounter end-of-file): + </p> + <p> + </p><pre> basic_istream<charT, traits>& + get (basic_streambuf<charT, traits>&, char_type); + </pre> + <p></p> + <p> + </p><pre> basic_istream<charT, traits>& + get (basic_streambuf<charT, traits>&); + </pre> + <p></p> + <p> +This function sets no bits (all implementations except for +STLport and Classic Iostreams set eofbit when they encounter +end-of-file): + </p> + <p> + </p><pre> int_type peek (); + </pre> + <p></p> + <p><b>Proposed resolution:</b></p> +<p>Informally, what we want is a global statement of intent saying + that eofbit gets set if we trip across EOF, and then we can take + away the specific wording for individual functions. A full review + is necessary. The wording currently in the standard is a mishmash, + and changing it on an individual basis wouldn't make things better. + Dietmar will do this work.</p> +<hr> +<a name="400"><h3>400. redundant type cast in lib.allocator.members</h3></a><p> +<b>Section:</b> 20.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.members"> [lib.allocator.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#Ready">Ready</a> <b>Submitter:</b> Markus Mauhart <b>Date:</b> 27 Feb 2003</p> +<p> +20.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.members"> [lib.allocator.members]</a> allocator members, contains +the following 3 lines: +</p> + +<pre> 12 Returns: new((void *) p) T( val) + void destroy(pointer p); + 13 Returns: ((T*) p)->~T() +</pre> + +<p> +The type cast "(T*) p" in the last line is redundant cause +we know that std::allocator<T>::pointer is a typedef for T*. +</p> +<p><b>Proposed resolution:</b></p> +<p> +Replace "((T*) p)" with "p". +</p> +<p><b>Rationale:</b></p> +<p>Just a typo, this is really editorial.</p> +<hr> +<a name="401"><h3>401. incorrect type casts in table 32 in lib.allocator.requirements</h3></a><p> +<b>Section:</b> 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Markus Mauhart <b>Date:</b> 27 Feb 2003</p> +<p> +I think that in par2 of 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> the last two +lines of table 32 contain two incorrect type casts. The lines are ... +</p> + +<pre> a.construct(p,t) Effect: new((void*)p) T(t) + a.destroy(p) Effect: ((T*)p)?->~T() +</pre> + +<p> +.... with the prerequisits coming from the preceding two paragraphs, especially +from table 31: +</p> + +<pre> alloc<T> a ;// an allocator for T + alloc<T>::pointer p ;// random access iterator + // (may be different from T*) + alloc<T>::reference r = *p;// T& + T const& t ; +</pre> + +<p> +For that two type casts ("(void*)p" and "(T*)p") to be well-formed +this would require then conversions to T* and void* for all +alloc<T>::pointer, so it would implicitely introduce extra +requirements for alloc<T>::pointer, additionally to the only +current requirement (being a random access iterator). +</p> +<p><b>Proposed resolution:</b></p> +<p> +"(void*)p" should be replaced with "(void*)&*p" and that +"((T*)p)?->" should be replaced with "(*p)." or with +"(&*p)->". +</p> + +<p> +Note: Actually I would prefer to replace "((T*)p)?->dtor_name" with +"p?->dtor_name", but AFAICS this is not possible cause of an omission +in 13.5.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/over.html#over.ref"> [over.ref]</a> (for which I have filed another DR on 29.11.2002). +</p> +<hr> +<a name="402"><h3>402. wrong new expression in [some_]allocator::construct</h3></a><p> +<b>Section:</b> 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a>, 20.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.members"> [lib.allocator.members]</a>, <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Markus Mauhart <b>Date:</b> 27 Feb 2003</p> +<p> +This applies to the new expression that is contained in both par12 of +20.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.members"> [lib.allocator.members]</a> and in par2 (table 32) of 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a>. +I think this new expression is wrong, involving unintended side +effects. +</p> + + +<p>20.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.members"> [lib.allocator.members]</a> contains the following 3 lines:</p> + +<pre> 11 Returns: the largest value N for which the call allocate(N,0) might succeed. + void construct(pointer p, const_reference val); + 12 Returns: new((void *) p) T( val) +</pre> + + +<p>20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> in table 32 has the following line:</p> +<pre> a.construct(p,t) Effect: new((void*)p) T(t) +</pre> + +<p> +.... with the prerequisits coming from the preceding two paragraphs, +especially from table 31: +</p> + +<pre> alloc<T> a ;// an allocator for T + alloc<T>::pointer p ;// random access iterator + // (may be different from T*) + alloc<T>::reference r = *p;// T& + T const& t ; +</pre> + +<p> +Cause of using "new" but not "::new", any existing "T::operator new" +function will hide the global placement new function. When there is no +"T::operator new" with adequate signature, +every_alloc<T>::construct(..) is ill-formed, and most +std::container<T,every_alloc<T>> use it; a workaround +would be adding placement new and delete functions with adequate +signature and semantic to class T, but class T might come from another +party. Maybe even worse is the case when T has placement new and +delete functions with adequate signature but with "unknown" semantic: +I dont like to speculate about it, but whoever implements +any_container<T,any_alloc> and wants to use construct(..) +probably must think about it. +</p> +<p><b>Proposed resolution:</b></p> +<p> +Therefore I think that "new" should be replaced with "::new" in both +cases. +</p> +<hr> +<a name="403"><h3>403. basic_string::swap should not throw exceptions</h3></a><p> +<b>Section:</b> 21.3.5.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::swap"> [lib.string::swap]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 25 Mar 2003</p> + +<p> +std::basic_string, 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a> paragraph 2 says that +basic_string "conforms to the requirements of a Sequence, as specified +in (23.1.1)." The sequence requirements specified in (23.1.1) to not +include any prohibition on swap members throwing exceptions. +</p> + +<p> +Section 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> paragraph 10 does limit conditions under +which exceptions may be thrown, but applies only to "all container +types defined in this clause" and so excludes basic_string::swap +because it is defined elsewhere. +</p> + +<p> +Eric Niebler points out that 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a> paragraph 5 explicitly +permits basic_string::swap to invalidates iterators, which is +disallowed by 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> paragraph 10. Thus the standard would +be contradictory if it were read or extended to read as having +basic_string meet 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> paragraph 10 requirements. +</p> + +<p> +Yet several LWG members have expressed the belief that the original +intent was that basic_string::swap should not throw exceptions as +specified by 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> paragraph 10, and that the standard is +unclear on this issue. The complexity of basic_string::swap is +specified as "constant time", indicating the intent was to avoid +copying (which could cause a bad_alloc or other exception). An +important use of swap is to ensure that exceptions are not thrown in +exception-safe code. +</p> + +<p> +Note: There remains long standing concern over whether or not it is +possible to reasonably meet the 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> paragraph 10 swap +requirements when allocators are unequal. The specification of +basic_string::swap exception requirements is in no way intended to +address, prejudice, or otherwise impact that concern. +</p> + + + + + +<p><b>Proposed resolution:</b></p> +<p> +In 21.3.5.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::swap"> [lib.string::swap]</a>, add a throws clause: +</p> + +<p> +Throws: Shall not throw exceptions. +</p> +<hr> +<a name="404"><h3>404. May a replacement allocation function be declared inline?</h3></a><p> +<b>Section:</b> 17.4.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.replacement.functions"> [lib.replacement.functions]</a>, 18.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete"> [lib.new.delete]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 24 Apr 2003</p> +<p> +The eight basic dynamic memory allocation functions (single-object +and array versions of ::operator new and ::operator delete, in the +ordinary and nothrow forms) are replaceable. A C++ program may +provide an alternative definition for any of them, which will be used +in preference to the implementation's definition. +</p> + +<p> +Three different parts of the standard mention requirements on +replacement functions: 17.4.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.replacement.functions"> [lib.replacement.functions]</a>, 18.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete.single"> [lib.new.delete.single]</a> +and 18.4.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete.array"> [lib.new.delete.array]</a>, and 3.7.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/basic.html#basic.stc.dynamic"> [basic.stc.dynamic]</a>. +</p> + +<p>None of these three places say whether a replacement function may + be declared inline. 18.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete.single"> [lib.new.delete.single]</a> paragraph 2 specifies a + signature for the replacement function, but that's not enough: + the <tt>inline</tt> specifier is not part of a function's signature. + One might also reason from 7.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/dcl.html#dcl.fct.spec"> [dcl.fct.spec]</a> paragraph 2, which + requires that "an inline function shall be defined in every + translation unit in which it is used," but this may not be quite + specific enough either. We should either explicitly allow or + explicitly forbid inline replacement memory allocation + functions.</p> +<p><b>Proposed resolution:</b></p> +<p> +Add a new sentence to the end of 17.4.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.replacement.functions"> [lib.replacement.functions]</a> paragraph 3: +"The program's definitions shall not be specified as <tt>inline</tt>." +</p> +<p><b>Rationale:</b></p> +<p> +The fact that <tt>inline</tt> isn't mentioned appears to have been +nothing more than an oversight. Existing implementations do not +permit inline functions as replacement memory allocation functions. +Providing this functionality would be difficult in some cases, and is +believed to be of limited value. +</p> +<hr> +<a name="405"><h3>405. qsort and POD</h3></a><p> +<b>Section:</b> 25.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.c.library"> [lib.alg.c.library]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Ray Lischner <b>Date:</b> 08 Apr 2003</p> +<p> +Section 25.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.c.library"> [lib.alg.c.library]</a> describes bsearch and qsort, from the C +standard library. Paragraph 4 does not list any restrictions on qsort, +but it should limit the base parameter to point to POD. Presumably, +qsort sorts the array by copying bytes, which requires POD. +</p> +<p><b>Proposed resolution:</b></p> +<hr> +<a name="406"><h3>406. vector::insert(s) exception safety</h3></a><p> +<b>Section:</b> 23.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 27 Apr 2003</p> +<p> +There is a possible defect in the standard: the standard text was +never intended to prevent arbitrary ForwardIterators, whose operations +may throw exceptions, from being passed, and it also wasn't intended +to require a temporary buffer in the case where ForwardIterators were +passed (and I think most implementations don't use one). As is, the +standard appears to impose requirements that aren't met by any +existing implementation. +</p> +<p><b>Proposed resolution:</b></p> +<p>Replace 23.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a> paragraph 1 with:</p> +<blockquote> + 1 Notes: Causes reallocation if the new size is greater than the + old capacity. If no reallocation happens, all the iterators and + references before the insertion point remain valid. If an exception + is thrown other than by the copy constructor or assignment operator + of T (or, if first and last satisfy the forward iterator + requirements, an operation on first or last) there are no effects. +</blockquote> +<hr> +<a name="407"><h3>407. Can singular iterators be destroyed?</h3></a><p> +<b>Section:</b> 24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 3 June 2003</p> +<p> +Clause 24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a>, paragraph 5, says that the only expression +that is defined for a singular iterator is "an assignment of a +non-singular value to an iterator that holds a singular value". This +means that destroying a singular iterator (e.g. letting an automatic +variable go out of scope) is technically undefined behavior. This +seems overly strict, and probably unintentional. +</p> +<p><b>Proposed resolution:</b></p> +<p> +Change the sentence in question to "... the only exceptions are +destroying an iterator that holds a singular value, or the assignment +of a non-singular value to an iterator that holds a singular value." +</p> +<hr> +<a name="408"><h3>408. Is vector<reverse_iterator<char*> > forbidden?</h3></a><p> +<b>Section:</b> 24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 3 June 2003</p> +<p> +I've been discussing iterator semantics with Dave Abrahams, and a +surprise has popped up. I don't think this has been discussed before. +</p> + +<p> +24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> says that the only operation that can be performed on "singular" +iterator values is to assign a non-singular value to them. (It +doesn't say they can be destroyed, and that's probably a defect.) +Some implementations have taken this to imply that there is no need +to initialize the data member of a reverse_iterator<> in the default +constructor. As a result, code like +</p> +<blockquote> + std::vector<std::reverse_iterator<char*> > v(7); + v.reserve(1000); +</blockquote> +<p> +invokes undefined behavior, because it must default-initialize the +vector elements, and then copy them to other storage. Of course many +other vector operations on these adapters are also left undefined, +and which those are is not reliably deducible from the standard. +</p> + +<p> +I don't think that 24.1 was meant to make standard-library iterator +types unsafe. Rather, it was meant to restrict what operations may +be performed by functions which take general user- and standard +iterators as arguments, so that raw pointers would qualify as +iterators. However, this is not clear in the text, others have come +to the opposite conclusion. +</p> + +<p> +One question is whether the standard iterator adaptors have defined +copy semantics. Another is whether they have defined destructor +semantics: is +</p> +<blockquote> + { std::vector<std::reverse_iterator<char*> > v(7); } +</blockquote> +<p> +undefined too? +</p> + +<p> +Note this is not a question of whether algorithms are allowed to +rely on copy semantics for arbitrary iterators, just whether the +types we actually supply support those operations. I believe the +resolution must be expressed in terms of the semantics of the +adapter's argument type. It should make clear that, e.g., the +reverse_iterator<T> constructor is actually required to execute +T(), and so copying is defined if the result of T() is copyable. +</p> + +<p> +Issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#235">235</a>, which defines reverse_iterator's default +constructor more precisely, has some relevance to this issue. +However, it is not the whole story. +</p> + +<p> +The issue was whether +</p> +<blockquote> + reverse_iterator() { } +</blockquote> +<p> +is allowed, vs. +</p> +<blockquote> + reverse_iterator() : current() { } +</blockquote> + +<p> +The difference is when T is char*, where the first leaves the member +uninitialized, and possibly equal to an existing pointer value, or +(on some targets) may result in a hardware trap when copied. +</p> + +<p> +8.5 paragraph 5 seems to make clear that the second is required to +satisfy DR <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#235">235</a>, at least for non-class Iterator argument +types. +</p> + +<p> +But that only takes care of reverse_iterator, and doesn't establish +a policy for all iterators. (The reverse iterator adapter was just +an example.) In particular, does my function +</p> +<blockquote> + template <typename Iterator> + void f() { std::vector<Iterator> v(7); } +</blockquote> +<p> +evoke undefined behavior for some conforming iterator definitions? +I think it does, now, because vector<> will destroy those singular +iterator values, and that's explicitly disallowed. +</p> + +<p> +24.1 shouldn't give blanket permission to copy all singular iterators, +because then pointers wouldn't qualify as iterators. However, it +should allow copying of that subset of singular iterator values that +are default-initialized, and it should explicitly allow destroying any +iterator value, singular or not, default-initialized or not. +</p> + +<p>Related issue: <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#407">407</a> +</p> +<p><b>Proposed resolution:</b></p> +<hr> +<a name="409"><h3>409. Closing an fstream should clear error state</h3></a><p> +<b>Section:</b> 27.8.1.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ifstream.members"> [lib.ifstream.members]</a>, 27.8.1.10 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ofstream.members"> [lib.ofstream.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 3 June 2003</p> +<p> +A strict reading of 27.8.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.fstreams"> [lib.fstreams]</a> shows that opening or +closing a basic_[io]fstream does not affect the error bits. This +means, for example, that if you read through a file up to EOF, and +then close the stream and reopen it at the beginning of the file, +the EOF bit in the stream's error state is still set. This is +counterintuitive. +</p> +<p> +The LWG considered this issue once before, as issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#22">22</a>, +and put in a footnote to clarify that the strict reading was indeed +correct. We did that because we believed the standard was +unambiguous and consistent, and that we should not make architectural +changes in a TC. Now that we're working on a new revision of the +language, those considerations no longer apply. +</p> +<p><b>Proposed resolution:</b></p> +<hr> +<a name="410"><h3>410. Missing semantics for stack and queue comparison operators</h3></a><p> +<b>Section:</b> 23.2.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.queue"> [lib.queue]</a>, 23.2.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.stack"> [lib.stack]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Hans Bos <b>Date:</b> 7 Jun 2003</p> +<p> +Sections 23.2.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.queue"> [lib.queue]</a> and 23.2.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.stack"> [lib.stack]</a> list +comparison operators (==, !=, <, <=, >, =>) for queue and +stack. Only the semantics for queue::operator== (23.2.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.queue"> [lib.queue]</a> par2) and queue::operator< (23.2.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.queue"> [lib.queue]</a> +par3) are defined. +</p> +<p><b>Proposed resolution:</b></p> +<hr> +<a name="411"><h3>411. Wrong names of set member functions</h3></a><p> +<b>Section:</b> 25.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.set.operations"> [lib.alg.set.operations]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Daniel Frey <b>Date:</b> 9 Jul 2003</p> +<p> +25.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.set.operations"> [lib.alg.set.operations]</a> paragraph 1 reads: +"The semantics of the set operations are generalized to multisets in a +standard way by defining union() to contain the maximum number of +occurrences of every element, intersection() to contain the minimum, and +so on." +</p> + +<p> +This is wrong. The name of the functions are set_union() and +set_intersection(), not union() and intersection(). +</p> +<p><b>Proposed resolution:</b></p> +<p>Change that sentence to use the correct names.</p> +<hr> +<a name="412"><h3>412. Typo in 27.4.4.3</h3></a><p> +<b>Section:</b> 27.4.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostate.flags"> [lib.iostate.flags]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 10 Jul 2003</p> +<p> +The Effects clause in 27.4.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostate.flags"> [lib.iostate.flags]</a> paragraph 5 says that the +function only throws if the respective bits are already set prior to +the function call. That's obviously not the intent. The typo ought to +be corrected and the text reworded as: "If (<i>state</i> & +exceptions()) == 0, returns. ..." +</p> +<p><b>Proposed resolution:</b></p> +<p> +In 27.4.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostate.flags"> [lib.iostate.flags]</a> paragraph 5, replace "If (rdstate() & +exceptions()) == 0" with "If (<i>state</i> & exceptions()) == 0". +</p> +<hr> +<a name="414"><h3>414. Which iterators are invalidated by v.erase()?</h3></a><p> +<b>Section:</b> 23.2.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.modifiers"> [lib.vector.modifiers]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 19 Aug 2003</p> +<p> +Consider the following code fragment: +</p> +<blockquote> +<pre>int A[8] = { 1,3,5,7,9,8,4,2 }; +std::vector<int> v(A, A+8); + +std::vector<int>::iterator i1 = v.begin() + 3; +std::vector<int>::iterator i2 = v.begin() + 4; +v.erase(i1); +</pre> +</blockquote> + +<p> +Which iterators are invalidated by <tt>v.erase(i1)</tt>: i1, i2, +both, or neither? +</p> + +<p> +On all existing implementations that I know of, the status of i1 and +i2 is the same: both of them will be iterators that point to some +elements of the vector (albeit not the same elements they did +before). You won't get a crash if you use them. Depending on +exactly what you mean by "invalidate", you might say that neither one +has been invalidated because they still point to <i>something</i>, +or you might say that both have been invalidated because in both +cases the elements they point to have been changed out from under the +iterator. +</p> + +<p> +The standard doesn't say either of those things. It says that erase +invalidates all iterators and references "after the point of the +erase". This doesn't include i1, since it's at the point of the +erase instead of after it. I can't think of any sensible definition +of invalidation by which one can say that i2 is invalidated by i1 +isn't. +</p> + +<p> +(This issue is important if you try to reason about iterator validity +based only on the guarantees in the standard, rather than reasoning +from typical implementation techniques. Strict debugging modes, +which some programmers find useful, do not use typical implementation +techniques.) +</p> +<p><b>Proposed resolution:</b></p> +<p> +In 23.2.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.modifiers"> [lib.vector.modifiers]</a> paragraph 3, change "Invalidates all the +iterators and references after the point of the erase" to +"Invalidates iterators and references at or after the point of the +erase". +</p> +<p><b>Rationale:</b></p> +<p>I believe this was essentially a typographical error, and that it + was taken for granted that erasing an element invalidates iterators + that point to it. The effects clause in question treats iterators + and references in parallel, and it would seem counterintuitive to + say that a reference to an erased value remains valid.</p> +<hr> +<a name="415"><h3>415. behavior of std::ws</h3></a><p> +<b>Section:</b> 27.6.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.manip"> [lib.istream.manip]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + + +According to 27.6.1.4, the ws() manipulator is not required to construct +the sentry object. The manipulator is also not a member function so the +text in 27.6.1, p1 through 4 that describes the exception policy for +istream member functions does not apply. That seems inconsistent with +the rest of extractors and all the other input functions (i.e., ws will +not cause a tied stream to be flushed before extraction, it doesn't check +the stream's exceptions or catch exceptions thrown during input, and it +doesn't affect the stream's gcount). + + </p> + <p><b>Proposed resolution:</b></p> + <p> + + +I propose that the manipulator be required to behave like an unformatted +member function. It should not behave as a formatted member function since +those set failbit in the sentry ctor according to DR195(*) and ws is explicitly +forbidden from doing that (sure, it could clear the bit, but why bother?) + +(*) http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#195 + </p> + <hr> +<a name="416"><h3>416. definitions of XXX_MIN and XXX_MAX macros in climits</h3></a><p> +<b>Section:</b> 18.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.c.limits"> [lib.c.limits]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +Given two overloads of the function foo(), one taking an argument of type +int and the other taking a long, which one will the call foo(LONG_MAX) +resolve to? The expected answer should be foo(long), but whether that +is true depends on the #defintion of the LONG_MAX macro, specifically +its type. This issue is about the fact that the type of these macros +is not actually required to be the same as the the type each respective +limit. +<br> + +Section 18.2.2 of the C++ Standard does not specify the exact types of +the XXX_MIN and XXX_MAX macros #defined in the <climits> and <limits.h> +headers such as INT_MAX and LONG_MAX and instead defers to the C standard. +<br> + +Section 5.2.4.2.1, p1 of the C standard specifies that "The values [of +these constants] shall be replaced by constant expressions suitable for use +in #if preprocessing directives. Moreover, except for CHAR_BIT and MB_LEN_MAX, +the following shall be replaced by expressions that have the same type as +would an expression that is an object of the corresponding type converted +according to the integer promotions." +<br> + +The "corresponding type converted according to the integer promotions" for +LONG_MAX is, according to 6.4.4.1, p5 of the C standard, the type of long +converted to the first of the following set of types that can represent it: +int, long int, long long int. So on an implementation where (sizeof(long) +== sizeof(int)) this type is actually int, while on an implementation where +(sizeof(long) > sizeof(int)) holds this type will be long. +<br> + +This is not an issue in C since the type of the macro cannot be detected +by any conforming C program, but it presents a portability problem in C++ +where the actual type is easily detectable by overload resolution. + + </p> + <p><b>Proposed resolution:</b></p> + <p> + +Specify the exact type of each XXX_MIN and XXX_MAX constant #defined in +the header <climits>. Note that it is not possible to #define these macros +so that they are usable in preprocessor arithmetic expressions, having +any type other than char, int, unsigned int, long, and unsigned long. +This means that the type of SHRT_MIN, for instance, has to be either +int ot long in C++. + </p> + <hr> +<a name="417"><h3>417. what does ctype::do_widen() return on failure</h3></a><p> +<b>Section:</b> 22.2.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +The Effects and Returns clauses of the do_widen() member function of +the ctype facet fail to specify the behavior of the function on failure. +That the function may not be able to simply cast the narrow character +argument to the type of the result since doing so may yield the wrong value +for some wchar_t encodings. Popular implementations of ctype<wchar_t> that +use mbtowc() and UTF-8 as the native encoding (e.g., GNU glibc) will fail +when the argument's MSB is set. There is no way for the the rest of locale +and iostream to reliably detect this failure. + + </p> + <p><b>Proposed resolution:</b></p> + <p> + +A partial solution might be to specify that ctype<wchar_t>::do_widen(char) +must return WEOF to indicate a failure. + </p> + <hr> +<a name="418"><h3>418. exceptions thrown during iostream cleanup</h3></a><p> +<b>Section:</b> 27.4.2.1.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios::Init"> [lib.ios::Init]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +The dtor of the ios_base::Init object is supposed to call flush() on the +6 standard iostream objects cout, cerr, clog, wcout, wcerr, and wclog. +This call may cause an exception to be thrown. +<br> + +17.4.4.8, p3 prohibits all library destructors from throwing exceptions. +<br> + +The question is: What should this dtor do if one or more of these calls +to flush() ends up throwing an exception? This can happen quite easily +if one of the facets installed in the locale imbued in the iostream +object throws. + + </p> + <p><b>Proposed resolution:</b></p> + <p> + +I'm not sure what the best approach is in this case -- ignore the exception +and proceed with the cleanup (required by the clause that prohibits library +dtors from throwing), abort right there and then, or allow the exception to +propagate (and allow an unfriendly termination of the program). + </p> + <hr> +<a name="419"><h3>419. istream extractors not setting failbit if eofbit is already set</h3></a><p> +<b>Section:</b> 27.6.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +27.6.1.1.2, p2 says that istream::sentry ctor prepares for input if is.good() +is true. p4 then goes on to say that the ctor sets the sentry::ok_ member to +true if the stream state is good after any preparation. 27.6.1.2.1, p1 then +says that a formatted input function endeavors to obtain the requested input +if the sentry's operator bool() returns true. + +Given these requirements, no formatted extractor should ever set failbit if +the initial stream rdstate() == eofbit. That is contrary to the behavior of +all implementations I tested. The program below prints out + +eof = 1, fail = 0 +eof = 1, fail = 1 + +on all of them. + </p> +<pre> +#include <sstream> +#include <cstdio> + +int main() +{ + std::istringstream strm ("1"); + + int i = 0; + + strm >> i; + + std::printf ("eof = %d, fail = %d\n", + !!strm.eof (), !!strm.fail ()); + + strm >> i; + + std::printf ("eof = %d, fail = %d\n", + !!strm.eof (), !!strm.fail ()); +} + +</pre> + <p> +<br> + +Comments from Jerry Schwarz (c++std-lib-11373): +<br> + +Jerry Schwarz wrote: +<br> + +I don't know where (if anywhere) it says it in the standard, but the +formatted extractors are supposed to set failbit if they don't extract +any characters. If they didn't then simple loops like +<br> + +while (cin >> x); +<br> + +would loop forever. +<br> + +Further comments from Martin Sebor: +<br> + +The question is which part of the extraction should prevent this from happening +by setting failbit when eofbit is already set. It could either be the sentry +object or the extractor. It seems that most implementations have chosen to +set failbit in the sentry [...] so that's the text that will need to be +corrected. + + </p> + <p><b>Proposed resolution:</b></p> + <p> + +A possible change might go in the Effects clause of the sentry ctor in +27.6.1.1.2, p1. At the end of the paragraph, i.e., after the text beginning +with +<br> + +Effects: If is.good() is true, ... +<br> + +add +<br> + +Otherwise, if (is.rdstate() == ios_base::eofbit) is true, +the function calls is.setstate(failbit) (which may throw +ios_base::failure). +<br> + +Another possible wording is +<br> + +Otherwise, if is.eof() is true, the function calls +is.setstate(ios_base::failbit) (which may throw +ios_base::failure). +<br> + +The difference between the two is that when failbit is set in is.exceptions(), +the first option will cause ios_base::failure to be thrown only during the +first call to the sentry ctor, while the second option will cause +ios_base::failure to be thrown each time the sentry ctor is invoked. I think +I like the first alternative better (i.e., there's no reason to call +setstate(failbit) if the bit is already known to be set). +<br> + +The change does not address the possibility of just badbit being set. +Should it? I.e., should the sentry ctor set failbit if (only) badbit is set? +<br> + +I haven't done a full survey of all the input functions to make sure the +change doesn't break something else. A second pair eyes would be helpful. +<br> + +Survey posted in c++std-lib-11409: +<br> + +Below is a survey of a number of popular implementations, including +classic iostreams. Three different sets of behavior exist (case 2 +is the same as case 1 except that istream::sentry does not set +eofbit or failbit in an initially good stream object when its +attempt to extract whitespace fails). +<br> + +The major difference seems to be in how badbit is treated in the +initial stream state. Most implementations still set failbit in +this case, but there are three implementations of classic +iostreams that do not. Since all surveyed implementations of +standard iostreams do set failbit in this case, I think we +should probably either require such behavior, or leave it +unspecified (in which case I would prefer to be explicit +about it to avoid any confusion). +<br> + +0. Compaq C++ classic + standard, g++ 2.95.2 classic, +g++ 3.2 standard, HP aCC 3.45 standard, Rogue Wave 3.1.1, +Sunpro 5.5 classic + standard, IBM VAC++ 6.0 standard, +STLport 4.5 classic + standard +<br> + +1. HP aCC 4.45 classic, SGI MIPSpro 7.3 classic, IBM VAC++ 6.0 classic +<br> + +2. SGI MIPSpro 7.3 standard +<br> + </p> +<pre> 0 1 2 + =========+=====+=====+===== + B-- 00 | B-F B-- B-F + B-- 01 | B-F B-- B-F + B-- 10 | B-F B-- B-F + B-- 11 | B-F B-- B-F + -E- 00 | -EF -EF -EF + -E- 01 | -EF -EF -EF + -E- 10 | -EF -EF -EF + -E- 11 | -EF -EF -EF + --F 00 | --F --F --F + --F 01 | --F --F --F + --F 10 | --F --F --F + --F 11 | --F --F --F + --- 00 | --- --- --- + --- 01 | --- --- --- + --- 10 | -EF -EF --- + --- 11 | --- --- --- + BE- 00 | BEF BEF BEF + BE- 01 | BEF BEF BEF + BE- 10 | BEF BEF BEF + BE- 11 | BEF BEF BEF + B-F 00 | B-F B-F B-F + B-F 01 | B-F B-F B-F + B-F 10 | B-F B-F B-F + B-F 11 | B-F B-F B-F + BEF 00 | BEF BEF BEF + BEF 01 | BEF BEF BEF + BEF 10 | BEF BEF BEF + BEF 11 | BEF BEF BEF + -EF 00 | -EF -EF -EF + -EF 01 | -EF -EF -EF + -EF 10 | -EF -EF -EF + -EF 11 | -EF -EF -EF + =========+=====+=====+===== + ^^^ ^^ ^^^ ^^^ ^^^ + | || | | | + | || +-----+-----+-- final stream state (Bad, Eof, Good, + | || or '-') + | |+-------------------- noskiws argument to sentry or ipfx(int) + | +--------------------- value of (ios::skipws & rdflags()) != 0 + +------------------------- initial stream state (Bad, Eof, Good, + '-') + + +#include <istream> +#include <streambuf> +#include <stdio.h> + +struct mybuf: std::streambuf { }; + +int main () +{ + static const std::ios::iostate states[] = { + std::ios::badbit, + std::ios::eofbit, + std::ios::failbit, + std::ios::goodbit, + std::ios::badbit | std::ios::eofbit, + std::ios::badbit | std::ios::failbit, + std::ios::badbit | std::ios::eofbit | std::ios::failbit, + std::ios::eofbit | std::ios::failbit + }; + + for (int i = 0; i != sizeof states / sizeof *states; ++i) { + for (int skipws = 0; skipws != 2; ++skipws) { + for (int noskipws = 0; noskipws != 2; ++noskipws) { + mybuf sb; + + std::istream strm (&sb); + + strm.setstate (states [i]); + + if (skipws) + strm.setf (std::ios::skipws); + else + strm.unsetf (std::ios::skipws); + + // strm.ipfx (noskipws); + std::istream::sentry guard (strm, !!noskipws); + + const std::ios::iostate state = strm.rdstate (); + + printf ("%c%c%c %d%d -> %c%c%c\n", + states [i] & std::ios::badbit ? 'B' : '-', + states [i] & std::ios::eofbit ? 'E' : '-', + states [i] & std::ios::failbit ? 'F' : '-', + skipws, noskipws, + state & std::ios::badbit ? 'B' : '-', + state & std::ios::eofbit ? 'E' : '-', + state & std::ios::failbit ? 'F' : '-'); + } + } + } +} + +</pre> + <hr> +<a name="420"><h3>420. is std::FILE a complete type?</h3></a><p> +<b>Section:</b> 27.8.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.fstreams"> [lib.fstreams]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +7.19.1, p2, of C99 requires that the FILE type only be declared in <stdio.h>. +None of the (implementation-defined) members of the struct is mentioned +anywhere for obvious reasons. + +C++ says in 27.8.1, p2 that FILE is a type that's defined in <cstdio>. Is +it really the intent that FILE be a complete type or is an implementation +allowed to just declare it without providing a full definition? + + </p> + <p><b>Proposed resolution:</b></p> + <p> + +Change 27.8.1, p2 to say that FILE is declared in <cstdio> and a note saying +that it's implementation-defined whether the type is complete or not. + </p> + <hr> +<a name="421"><h3>421. is basic_streambuf copy-constructible?</h3></a><p> +<b>Section:</b> 27.5.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.cons"> [lib.streambuf.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +The reflector thread starting with c++std-lib-11346 notes that the class +template basic_streambuf, along with basic_stringbuf and basic_filebuf, +is copy-constructible but that the semantics of the copy constructors +are not defined anywhere. Further, different implementations behave +differently in this respect: some prevent copy construction of objects +of these types by declaring their copy ctors and assignment operators +private, others exhibit undefined behavior, while others still give +these operations well-defined semantics. +</p> + +<p> +Note that this problem doesn't seem to be isolated to just the three +types mentioned above. A number of other types in the library section +of the standard provide a compiler-generated copy ctor and assignment +operator yet fail to specify their semantics. A (possibly still +incomplete) list of such types along with the headers they are defined +in is provided below, courtesy of Howard Hinnant: +<br> + </p> +<pre><limits> + numeric_limits +<stdexcept> + logic_error + domain_error + invalid_argument + length_error + out_of_range + runtime_error + range_error + overflow_error + underflow_error +<utility> + pair +<functional> + unary_function + binary_function + plus + minus + multiplies + divides + modulus + negate + equal_to + not_equal_to + greater + less + greater_equal + less_equal + logical_and + logical_or + logical_not + unary_negate + binary_negate + binder1st + binder2nd + pointer_to_unary_function + pointer_to_binary_function + mem_fun_t + mem_fun1_t + mem_fun_ref_t + mem_fun1_ref_t + const_mem_fun_t + const_mem_fun1_t + const_mem_fun_ref_t + const_mem_fun1_ref_t +<memory> + allocator<void> + allocator // operator= only, which also isn't required by Allocator Requirements + raw_storage_iterator +<string> + char_traits<char> + char_traits<wchar_t> +<locale> + ctype_base + ctype + ctype_byname + ctype<char> + ctype_byname<char> + codecvt_base + codecvt + codecvt_byname + num_get + num_put + numpunct + numpunct_byname + collate + collate_byname + time_base + time_get + time_get_byname + time_put + time_put_byname + money_get + money_put + money_base + moneypunct + moneypunct_byname + messages_base + messages + messages_byname +<queue> + queue + priority_queue +<stack> + stack +<vector> + vector<bool>::reference // copy ctor only +<map> + map::value_compare + multimap::value_compare +<bitset> + bitset::reference // copy ctor only + bitset +<iterator> + iterator_traits + iterator_traits<T*> + iterator_traits<const T*> + iterator + input_iterator_tag + output_iterator_tag + forward_iterator_tag + bidirectional_iterator_tag + random_access_iterator_tag + reverse_iterator + back_insert_iterator + front_insert_iterator + insert_iterator + istream_iterator // operator= only + ostream_iterator // operator= only + istreambuf_iterator + istreambuf_iterator::proxy + ostreambuf_iterator +<complex> + complex<float> // copy ctor only + complex<double> // copy ctor only + complex<long double> // copy ctor only +<valarray> + slice + gslice +<ios> + ios_base // addressed by TC issue 50 + ios_base::failure + ios_base::Init + fpos +<streambuf> + basic_streambuf +<istream> + basic_istream + basic_iostream +<ostream> + basic_ostream +<sstream> + basic_stringbuf + basic_istringstream + basic_ostringstream + basic_stringstream +<fstream> + basic_filebuf + basic_ifstream + basic_ofstream + basic_fstream +<strstream> + strstreambuf + istrstream + ostrstream + strstream +</pre> + <p><b>Proposed resolution:</b></p> + <p> + +The standard ought to be clarified to either explicitly disallow copy +ctors and assignment operators for these types, or to specify what +the exact semantics of these functions are. + </p> + <hr> +<a name="422"><h3>422. explicit specializations of member functions of class templates</h3></a><p> +<b>Section:</b> 17.4.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.reserved.names"> [lib.reserved.names]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> +<p> +It has been suggested that 17.4.3.1, p1 may or may not allow programs to +explicitly specialize members of standard templates on user-defined types. +The answer to the question might have an impact where library requirements +are given using the "as if" rule. I.e., if programs are allowed to specialize +member functions they will be able to detect an implementation's strict +conformance to Effects clauses that describe the behavior of the function +in terms of the other member function (the one explicitly specialized by +the program) by relying on the "as if" rule. +</p> +<p><b>Proposed resolution:</b></p> +<p> +While I think programs should be allowed to explicitly specialize member +functions of standard templates, I don't find it reasonable to expect +implementations to follow the "as if" rule to the letter. I propose to add +a clause to chapter 17 saying that where a function is described in terms +of another (non-virtual) function using the "as if" rule, an implementation +may substitute another (non-virtual) function call as long as the effects +on the object remain the same as in the absence of any specializations +of the called function in the program. +</p> +<hr> +<a name="423"><h3>423. effects of negative streamsize in iostreams</h3></a><p> +<b>Section:</b> 27 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + +<p> +A third party test suite tries to exercise istream::ignore(N) with +a negative value of N and expects that the implementation will treat +N as if it were 0. Our implementation asserts that (N >= 0) holds and +aborts the test. +</p> + +<p> +I can't find anything in section 27 that prohibits such values but I don't +see what the effects of such calls should be, either (this applies to +a number of unformatted input functions as well as some member functions +of the basic_streambuf template). +</p> +<p><b>Proposed resolution:</b></p> +<p> +I propose that we add to each function in clause 27 that takes an argument, +say N, of type streamsize a Requires clause saying that "N >= 0." The intent +is to allow negative streamsize values in calls to precision() and width() +but disallow it in calls to streambuf::sgetn(), istream::ignore(), or +ostream::write(). +</p> +<hr> +<a name="424"><h3>424. normative notes</h3></a><p> +<b>Section:</b> 17.3.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.structure.summary"> [lib.structure.summary]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + +<p> +The text in 17.3.1.1, p1 says: +<br> + +"Paragraphs labelled "Note(s):" or "Example(s):" are informative, other +paragraphs are normative." +<br> + +The library section makes heavy use of paragraphs labeled "Notes(s)," +some of which are clearly intended to be normative (see list 1), while +some others are not (see list 2). There are also those where the intent +is not so clear (see list 3). +<br> + +List 1 -- Examples of (presumably) normative Notes: +<br> + +20.4.1.1, p3, 20.4.1.1, p10, 21.3.1, p11, 22.1.1.2, p11, 23.2.1.3, p2, +25.3.7, p3, 26.2.6, p14a, 27.5.2.4.3, p7. +<br> + +List 2 -- Examples of (presumably) informative Notes: +<br> + +18.4.1.3, p3, 21.3.5.6, p14, 22.2.1.5.2, p3, 25.1.1, p4, 26.2.5, p1, +27.4.2.5, p6. +<br> + +List 3 -- Examples of Notes that are not clearly either normative +or informative: +<br> + +22.1.1.2, p8, 22.1.1.5, p6, 27.5.2.4.5, p4. +<br> + +None of these lists is meant to be exhaustive. +</p> + +<p><b>Proposed resolution:</b></p> + +<p> +One possible solution is to identify all the paragraphs marked "Note(s):" +that are intended to be normative and either remove the labeling or replace +it with some other word, such as "Effects:" to make the normative intent +clear. +<br> + +Another possible solution is to change 17.3.1.1, p1 and remove the mention +of Notes being informative, and then go through all the paragraphs marked +"Note(s):" that are intended to be informative and make change preserving +their informative nature. + </p> + <hr> +<a name="425"><h3>425. return value of std::get_temporary_buffer</h3></a><p> +<b>Section:</b> 20.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.temporary.buffer"> [lib.temporary.buffer]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +The standard is not clear about the requirements on the value returned from +a call to get_temporary_buffer(0). In particular, it fails to specify whether +the call should return a distinct pointer each time it is called (like +operator new), or whether the value is unspecified (as if returned by +malloc). The standard also fails to mention what the required behavior +is when the argument is less than 0. + + </p> + <p><b>Proposed resolution:</b></p> + <p> + +In the first case, I propose that the function behave like malloc, i.e., +<br> + +If the size of the space requested is zero, the behavior is +implementation-defined: either pair(0, 0) is returned, or the behavior is +as if the size were some nonzero value, except that the returned pointer +is not dereferenceable. +<br> + +In the second case, I propose that the function fail by returning pair(0, 0). + </p> + <hr> +<a name="426"><h3>426. search_n(), fill_n(), and generate_n() with negative n</h3></a><p> +<b>Section:</b> 25.1.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.search"> [lib.alg.search]</a>, 25.2.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.fill"> [lib.alg.fill]</a>, 25.2.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.generate"> [lib.alg.generate]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +The complexity requirements for these function templates are incorrect +(or don't even make sense) for negative n: +<br> + +25.1.9, p7 (search_n): +<br> + +Complexity: At most (last1 - first1) * count applications +of the corresponding predicate. +<br> + +25.2.5, p3 (fill_n): +<br> + +Complexity: Exactly last - first (or n) assignments. +<br> + +25.2.6, p3 (generate_n): +<br> + +Complexity: Exactly last - first (or n) assignments. +<br> + +In addition, the Requirements or the Effects clauses for the latter two +templates don't say anything about the behavior when n is negative. + + </p> + <p><b>Proposed resolution:</b></p> + <p> + +My proposed fix is to: +<br> + +Change 25.1.9, p7 to +<br> + +Complexity: At most (last1 - first1) * count applications +of the corresponding predicate if count is non-negative, +or 0 otherwise. +<br> + +Change 25.2.5, p2 from +<br> + +Effects: Assigns value through all the iterators in the +range [first, last) or [first, first + n). +<br> + +to +<br> + +Effects: Assigns value through all the iterators in the +range [first, last), or [first, first + n) if n is non +negative, none otherwise. +<br> + +Change 25.2.5, p3 to: +<br> + +Complexity: Exactly last - first (or n if n is non-negative, +or 0 otherwise) assignments. +<br> + +Change 25.2.6, p1 from +<br> + +Effects: Invokes the function object gen and assigns the return +value of gen though all the iterators in the range [first, last) +or [first, first + n). +<br> + +to (notice the correction for the misspelled "through"): +<br> + +Effects: Invokes the function object genand assigns the return +value of gen through all the iterators in the range [first, last), +or [first, first + n) if n is non-negative, or [first, first) +otherwise. +<br> + +Change 25.2.6, p3 to: +<br> + +Complexity: Exactly last - first (or n if n is non-negative, +or 0 otherwise) assignments. +<br> + +The alternative is to require that n be non-negative. I chose +the other option in order to keep the requirements in line with +those of search_n which allows negative counts. + </p> + <hr> +<a name="427"><h3>427. stage 2 and rationale of DR 221</h3></a><p> +<b>Section:</b> 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +The requirements specified in Stage 2 and reiterated in the rationale +of DR 221 (and echoed again in DR 303) specify that num_get<charT>:: +do_get() compares characters on the stream against the widened elements +of "012...abc...ABCX+-" +<br> + +An implementation is required to allow programs to instantiate the num_get +template on any charT that satisfies the requirements on a user-defined +character type. These requirements do not include the ability of the +character type to be equality comparable (the char_traits template must +be used to perform tests for equality). Hence, the num_get template cannot +be implemented to support any arbitrary character type. The num_get template +must either make the assumption that the character type is equality-comparable +(as some popular implementations do), or it may use char_traits<charT> to do +the comparisons (some other popular implementations do that). This diversity +of approaches makes it difficult to write portable programs that attempt to +instantiate the num_get template on user-defined types. + + </p> + <p><b>Proposed resolution:</b></p> + <p> + +Specify a mechanism whereby the num_get template may compare objects of +user-defined character types. Several possible solutions, each having +some drawbacks, were discussed in a thread on c++std-lib@research.att.com +starting with c++std-lib-10623. +<br> + +One possibility is to require that user-defined character types be equality +comparable, thus obviating tye need for the char_traits::eq() function. This +solution would make the requirements imposed on user-defined character types +by the locale templates inconsistent with those of basic_string. +<br> + +Another option is to require that programs that instantiate num_get on +user-defined types provide an explicit specialization of the std::char_traits +template on that type and require num_get to use it. This solution would +render the basic_string Traits template parameter useless. +<br> + +Yet another option is to specify that when the num_get facet is instantiated +on a user-defined character type, say charT, that defines the nested type +charT::traits_type, num_get should use it to do comparisons. Otherwise, +num_get should use std::char_traits<charT>. This solution, while more +robust than the first two, might set the unwarranted expectation that +a program that provides two traits classes for the same character type +will have meaningful semantics. +<br> + +Finally, arguably the most flexible solution is to remove the requirement +from Stage 2 that num_get compare the widened set of character literals and +instead have the template compare the narrowed characters read from the +input sequence. This issue proposes to adopt this last option as the +resolution. + </p> + <hr> +<a name="428"><h3>428. string::erase(iterator) validity</h3></a><p> +<b>Section:</b> 21.3.5.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::erase"> [lib.string::erase]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +23.1.1, p3 along with Table 67 specify as a prerequisite for a.erase(q) +that q must be a valid dereferenceable iterator into the sequence a. +<br> + +However, 21.3.5.5, p5 describing string::erase(p) only requires that +p be a valid iterator. +<br> + +This may be interepreted as a relaxation of the general requirement, +which is most likely not the intent. + + </p> + <p><b>Proposed resolution:</b></p> + <p> + +Either clarify 21.3.5.5, p5 to say that the iterator is required to be +valid and dereferenceable or drop the requirement altogether and rely +on the general container requirements outlined in Table 67. + </p> + <hr> +<a name="429"><h3>429. typo in basic_ios::clear(iostate)</h3></a><p> +<b>Section:</b> 27.4.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostate.flags"> [lib.iostate.flags]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +The Effects clause in 27.4.4.3, p5 describing the effects of a call to +the ios_base member function clear(iostate state) says that the function +only throws if the respective bits are already set prior to the function +call. That's obviously not the intent. If it was, a call to clear(badbit) +on an object for which (rdstate() == goodbit && exceptions() == badbit) +holds would not result in an exception being thrown. + + </p> + <p><b>Proposed resolution:</b></p> + <p> + +The text ought to be changed from +<br> + +"If (rdstate() & exceptions()) == 0, returns. ..." +<br> + +to +<br> + +"If (state & exceptions()) == 0, returns. ..." + </p> + <hr> +<a name="430"><h3>430. valarray subset operations</h3></a><p> +<b>Section:</b> 26.3.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.valarray.sub"> [lib.valarray.sub]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2003</p> + <p> + +The standard fails to specify the behavior of valarray::operator[](slice) +and other valarray subset operations when they are passed an "invalid" +slice object, i.e., either a slice that doesn't make sense at all (e.g., +slice (0, 1, 0) or one that doesn't specify a valid subset of the valarray +object (e.g., slice (2, 1, 1) for a valarray of size 1). + + </p> + <p><b>Proposed resolution:</b></p> + <p> + +Clarify the text of the standard to define what constitutes a valid and +invalid slice object, and either specify the exact behavior of these +member functions when passed an invalid slice object, or explicitly +specify that the behavior is undefined under these conditions for the +sake of efficiency. + </p> + <hr> +<a name="431"><h3>431. Swapping containers with unequal allocators</h3></a><p> +<b>Section:</b> 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a>, 25 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#New">New</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 20 Sep 2003</p> +<p>Clause 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> paragraph 4 says that implementations + are permitted to supply containers that are unable to cope with + allocator instances and that container implementations may assume + that all instances of an allocator type compare equal. We gave + implementers this latitude as a temporary hack, and eventually we + want to get rid of it. What happens when we're dealing with + allocators that <i>don't</i> compare equal? +</p> + +<p>In particular: suppose that <tt>v1</tt> and <tt>v2</tt> are both + objects of type <tt>vector<int, my_alloc></tt> and that + <tt>v1.get_allocator() != v2.get_allocator()</tt>. What happens if + we write <tt>v1.swap(v2)</tt>? Informally, three possibilities:</p> + +<p>1. This operation is illegal. Perhaps we could say that an + implementation is required to check and to throw an exception, or + perhaps we could say it's undefined behavior.</p> +<p>2. The operation performs a slow swap (i.e. using three + invocations of <tt>operator=</tt>, leaving each allocator with its + original container. This would be an O(N) operation.</p> +<p>3. The operation swaps both the vectors' contents and their + allocators. This would be an O(1) operation. That is:</p> + <blockquote> + <pre> my_alloc a1(...); + my_alloc a2(...); + assert(a1 != a2); + + vector<int, my_alloc> v1(a1); + vector<int, my_alloc> v2(a2); + assert(a1 == v1.get_allocator()); + assert(a2 == v2.get_allocator()); + + v1.swap(v2); + assert(a1 == v2.get_allocator()); + assert(a2 == v1.get_allocator()); + </pre> + </blockquote> + +<p><b>Proposed resolution:</b></p> <p>----- End of document -----</p> -</body> -</html> +</body></html>
\ No newline at end of file diff --git a/libstdc++-v3/docs/html/ext/lwg-defects.html b/libstdc++-v3/docs/html/ext/lwg-defects.html index 41ae2f822c6..3c26633595f 100644 --- a/libstdc++-v3/docs/html/ext/lwg-defects.html +++ b/libstdc++-v3/docs/html/ext/lwg-defects.html @@ -1,15 +1,14 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"> -<html> -<head><title>C++ Standard Library Defect Report List</title></head> -<body bgcolor="#ffffff" text="#000000"> +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/REC-html40/loose.dtd"><html><head><title>C++ Standard Library Defect Report List</title></head> + +<body text="#000000" bgcolor="#ffffff"> <table> -<tr> +<tbody><tr> <td align="left">Doc. no.</td> -<td align="left">J16/02-0049 = WG21 N1391</td> +<td align="left">N1516 = 03-0099</td> </tr> <tr> <td align="left">Date:</td> -<td align="left">10 Sep 2002</td> +<td align="left">20 Sep 2003</td> </tr> <tr> <td align="left">Project:</td> @@ -19,221 +18,239 @@ <td align="left">Reply to:</td> <td align="left">Matt Austern <austern@apple.com></td> </tr> -</table> -<h1>C++ Standard Library Defect Report List (Revision 23)</h1> +</tbody></table> +<h1>C++ Standard Library Defect Report List (Revision 27)</h1> <p>Reference ISO/IEC IS 14882:1998(E)</p> <p>Also see:</p> <ul> <li> -<a href="lwg-toc.html">Table of Contents</a> for all library issues.</li> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-toc.html">Table of Contents</a> for all library issues.</li> <li> -<a href="lwg-index.html">Index by Section</a> for all library issues.</li> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-index.html">Index by Section</a> for all library issues.</li> <li> -<a href="lwg-status.html">Index by Status</a> for all library issues.</li> - <li><a href="lwg-active.html">Library Active Issues List</a></li> - <li><a href="lwg-closed.html">Library Closed Issues List</a></li> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-status.html">Index by Status</a> for all library issues.</li> + <li><a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html">Library Active Issues List</a></li> + <li><a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html">Library Closed Issues List</a></li> </ul> <p>This document contains only library issues which have been closed by the Library Working Group (LWG) after being found to be defects - in the standard. That is, issues which have a status of <a href="lwg-active.html#DR">DR</a>, <a href="lwg-active.html#TC">TC</a>, or <a href="lwg-active.html#RR">RR</a>. See the - <a href="lwg-closed.html">Library Closed Issues List</a> for issues closed as non-defects. See the - <a href="lwg-active.html">Library Active Issues List</a> for active issues and more information. The + in the standard. That is, issues which have a status of <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#DR">DR</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a>, or <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#RR">RR</a>. See the + <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html">Library Closed Issues List</a> for issues closed as non-defects. See the + <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html">Library Active Issues List</a> for active issues and more information. The introductory material in that document also applies to this document.</p> <h2>Revision History</h2> <ul> +<li>R27: +Pre-Kona mailing. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#404">404</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#431">431</a>. +</li> +<li>R26: +Post-Oxford mailing: reflects decisions made at the Oxford meeting. +All issues in Ready status were voted into DR status. All issues in +DR status were voted into WP status. +</li> +<li>R25: +Pre-Oxford mailing. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#390">390</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#402">402</a>. +</li> +<li>R24: +Post-Santa Cruz mailing: reflects decisions made at the Santa Cruz +meeting. All Ready issues from R23 with the exception of <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#253">253</a>, which has been given a new proposed resolution, were +moved to DR status. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#383">383</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#389">389</a>. (Issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#387">387</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#389">389</a> were discussed +at the meeting.) Made progress on issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#225">225</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#226">226</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#229">229</a>: <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#225">225</a> and <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#229">229</a> have been moved to Ready status, and the only remaining +concerns with <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#226">226</a> involve wording. +</li> <li>R23: -Pre-Santa Cruz mailing. Added new issues <a href="lwg-active.html#367">367</a>-<a href="lwg-active.html#382">382</a>. +Pre-Santa Cruz mailing. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#367">367</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#382">382</a>. Moved issues in the TC to TC status. </li> <li>R22: -Post-Curaçao mailing. Added new issues <a href="lwg-active.html#362">362</a>-<a href="lwg-active.html#366">366</a>. +Post-Curaçao mailing. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#362">362</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#366">366</a>. </li> <li>R21: -Pre-Curaçao mailing. Added new issues <a href="lwg-closed.html#351">351</a>-<a href="lwg-active.html#361">361</a>. +Pre-Curaçao mailing. Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#351">351</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#361">361</a>. </li> <li>R20: Post-Redmond mailing; reflects actions taken in Redmond. Added -new issues <a href="lwg-active.html#336">336</a>-<a href="lwg-active.html#350">350</a>, of which issues -<a href="lwg-active.html#347">347</a>-<a href="lwg-active.html#350">350</a> were added since Redmond, hence +new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#336">336</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#350">350</a>, of which issues +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#347">347</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#350">350</a> were added since Redmond, hence not discussed at the meeting. All Ready issues were moved to DR status, with the exception of issues -<a href="lwg-defects.html#284">284</a>, <a href="lwg-active.html#241">241</a>, and <a href="lwg-closed.html#267">267</a>. +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#284">284</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#241">241</a>, and <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#267">267</a>. Noteworthy issues discussed at Redmond include -<a href="lwg-active.html#120">120</a> <a href="lwg-active.html#202">202</a>, <a href="lwg-active.html#226">226</a>, <a href="lwg-active.html#233">233</a>, -<a href="lwg-defects.html#270">270</a>, <a href="lwg-active.html#253">253</a>, <a href="lwg-active.html#254">254</a>, <a href="lwg-active.html#323">323</a>. +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#120">120</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#202">202</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#226">226</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#233">233</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#270">270</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#253">253</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#254">254</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#323">323</a>. </li> <li>R19: Pre-Redmond mailing. Added new issues -<a href="lwg-active.html#323">323</a>-<a href="lwg-defects.html#335">335</a>. +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#323">323</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#335">335</a>. </li> <li>R18: Post-Copenhagen mailing; reflects actions taken in Copenhagen. -Added new issues <a href="lwg-defects.html#312">312</a>-<a href="lwg-defects.html#317">317</a>, and discussed -new issues <a href="lwg-defects.html#271">271</a>-<a href="lwg-closed.html#314">314</a>. +Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#312">312</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#317">317</a>, and discussed +new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#271">271</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#314">314</a>. Changed status of issues -<a href="lwg-defects.html#103">103</a> <a href="lwg-defects.html#118">118</a> <a href="lwg-defects.html#136">136</a> <a href="lwg-defects.html#153">153</a> -<a href="lwg-defects.html#165">165</a> <a href="lwg-defects.html#171">171</a> <a href="lwg-defects.html#183">183</a> <a href="lwg-defects.html#184">184</a> -<a href="lwg-defects.html#185">185</a> <a href="lwg-defects.html#186">186</a> <a href="lwg-defects.html#214">214</a> <a href="lwg-defects.html#221">221</a> -<a href="lwg-defects.html#234">234</a> <a href="lwg-defects.html#237">237</a> <a href="lwg-defects.html#243">243</a> <a href="lwg-defects.html#248">248</a> -<a href="lwg-defects.html#251">251</a> <a href="lwg-defects.html#252">252</a> <a href="lwg-defects.html#256">256</a> <a href="lwg-defects.html#260">260</a> -<a href="lwg-defects.html#261">261</a> <a href="lwg-defects.html#262">262</a> <a href="lwg-defects.html#263">263</a> <a href="lwg-defects.html#265">265</a> -<a href="lwg-defects.html#268">268</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#103">103</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#118">118</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#136">136</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#153">153</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#165">165</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#171">171</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#183">183</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#184">184</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#185">185</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#186">186</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#214">214</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#221">221</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#234">234</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#237">237</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#243">243</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#248">248</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#251">251</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#252">252</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#256">256</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#260">260</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#261">261</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#262">262</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#263">263</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#265">265</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#268">268</a> to DR. Changed status of issues -<a href="lwg-defects.html#49">49</a> <a href="lwg-defects.html#109">109</a> <a href="lwg-defects.html#117">117</a> <a href="lwg-defects.html#182">182</a> -<a href="lwg-defects.html#228">228</a> <a href="lwg-defects.html#230">230</a> <a href="lwg-defects.html#232">232</a> <a href="lwg-defects.html#235">235</a> -<a href="lwg-defects.html#238">238</a> <a href="lwg-active.html#241">241</a> <a href="lwg-defects.html#242">242</a> <a href="lwg-defects.html#250">250</a> -<a href="lwg-defects.html#259">259</a> <a href="lwg-defects.html#264">264</a> <a href="lwg-defects.html#266">266</a> <a href="lwg-closed.html#267">267</a> -<a href="lwg-defects.html#271">271</a> <a href="lwg-defects.html#272">272</a> <a href="lwg-defects.html#273">273</a> <a href="lwg-defects.html#275">275</a> -<a href="lwg-defects.html#281">281</a> <a href="lwg-defects.html#284">284</a> <a href="lwg-defects.html#285">285</a> <a href="lwg-defects.html#286">286</a> -<a href="lwg-defects.html#288">288</a> <a href="lwg-defects.html#292">292</a> <a href="lwg-defects.html#295">295</a> <a href="lwg-defects.html#297">297</a> -<a href="lwg-defects.html#298">298</a> <a href="lwg-defects.html#301">301</a> <a href="lwg-defects.html#303">303</a> <a href="lwg-defects.html#306">306</a> -<a href="lwg-defects.html#307">307</a> <a href="lwg-defects.html#308">308</a> <a href="lwg-defects.html#312">312</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#49">49</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#109">109</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#117">117</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#182">182</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#228">228</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#230">230</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#232">232</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#235">235</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#238">238</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#241">241</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#242">242</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#250">250</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#259">259</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#264">264</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#266">266</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#267">267</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#271">271</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#272">272</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#273">273</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#275">275</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#281">281</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#284">284</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#285">285</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#286">286</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#288">288</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#292">292</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#295">295</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#297">297</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#298">298</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#301">301</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#303">303</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#306">306</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#307">307</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#308">308</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#312">312</a> to Ready. Closed issues -<a href="lwg-closed.html#111">111</a> <a href="lwg-closed.html#277">277</a> <a href="lwg-closed.html#279">279</a> <a href="lwg-closed.html#287">287</a> -<a href="lwg-closed.html#289">289</a> <a href="lwg-closed.html#293">293</a> <a href="lwg-closed.html#302">302</a> <a href="lwg-closed.html#313">313</a> -<a href="lwg-closed.html#314">314</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#111">111</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#277">277</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#279">279</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#287">287</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#289">289</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#293">293</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#302">302</a> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#313">313</a> +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#314">314</a> as NAD. </li> <li>R17: Pre-Copenhagen mailing. Converted issues list to XML. Added proposed -resolutions for issues <a href="lwg-defects.html#49">49</a>, <a href="lwg-defects.html#76">76</a>, <a href="lwg-active.html#91">91</a>, <a href="lwg-defects.html#235">235</a>, <a href="lwg-defects.html#250">250</a>, <a href="lwg-closed.html#267">267</a>. -Added new issues <a href="lwg-active.html#278">278</a>-<a href="lwg-defects.html#311">311</a>. +resolutions for issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#49">49</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#76">76</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#91">91</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#235">235</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#250">250</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#267">267</a>. +Added new issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#278">278</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#311">311</a>. </li> <li>R16: post-Toronto mailing; reflects actions taken in Toronto. Added new -issues <a href="lwg-defects.html#265">265</a>-<a href="lwg-closed.html#277">277</a>. Changed status of issues -<a href="lwg-defects.html#3">3</a>, <a href="lwg-defects.html#8">8</a>, <a href="lwg-defects.html#9">9</a>, <a href="lwg-defects.html#19">19</a>, -<a href="lwg-defects.html#26">26</a>, <a href="lwg-defects.html#31">31</a>, <a href="lwg-defects.html#61">61</a>, -<a href="lwg-defects.html#63">63</a>, <a href="lwg-defects.html#86">86</a>, <a href="lwg-defects.html#108">108</a>, -<a href="lwg-defects.html#112">112</a>, <a href="lwg-defects.html#114">114</a>, <a href="lwg-defects.html#115">115</a>, -<a href="lwg-defects.html#122">122</a>, <a href="lwg-defects.html#127">127</a>, <a href="lwg-defects.html#129">129</a>, -<a href="lwg-defects.html#134">134</a>, <a href="lwg-defects.html#137">137</a>, <a href="lwg-defects.html#142">142</a>, -<a href="lwg-defects.html#144">144</a>, <a href="lwg-defects.html#146">146</a>, <a href="lwg-defects.html#147">147</a>, -<a href="lwg-defects.html#159">159</a>, <a href="lwg-defects.html#164">164</a>, <a href="lwg-defects.html#170">170</a>, -<a href="lwg-defects.html#181">181</a>, <a href="lwg-defects.html#199">199</a>, <a href="lwg-defects.html#208">208</a>, -<a href="lwg-defects.html#209">209</a>, <a href="lwg-defects.html#210">210</a>, <a href="lwg-defects.html#211">211</a>, -<a href="lwg-defects.html#212">212</a>, <a href="lwg-defects.html#217">217</a>, <a href="lwg-defects.html#220">220</a>, -<a href="lwg-defects.html#222">222</a>, <a href="lwg-defects.html#223">223</a>, <a href="lwg-defects.html#224">224</a>, -<a href="lwg-defects.html#227">227</a> to "DR". Reopened issue <a href="lwg-active.html#23">23</a>. Reopened -issue <a href="lwg-active.html#187">187</a>. Changed issues <a href="lwg-closed.html#2">2</a> and -<a href="lwg-closed.html#4">4</a> to NAD. Fixed a typo in issue <a href="lwg-defects.html#17">17</a>. Fixed -issue <a href="lwg-defects.html#70">70</a>: signature should be changed both places it -appears. Fixed issue <a href="lwg-defects.html#160">160</a>: previous version didn't fix +issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#265">265</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#277">277</a>. Changed status of issues +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#3">3</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#8">8</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#9">9</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#19">19</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#26">26</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#31">31</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#61">61</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#63">63</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#86">86</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#108">108</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#112">112</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#114">114</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#115">115</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#122">122</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#127">127</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#129">129</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#134">134</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#137">137</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#142">142</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#144">144</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#146">146</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#147">147</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#159">159</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#164">164</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#170">170</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#181">181</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#199">199</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#208">208</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#209">209</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#210">210</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#211">211</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#212">212</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#217">217</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#220">220</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#222">222</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#223">223</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#224">224</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#227">227</a> to "DR". Reopened issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#23">23</a>. Reopened +issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#187">187</a>. Changed issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#2">2</a> and +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#4">4</a> to NAD. Fixed a typo in issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#17">17</a>. Fixed +issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#70">70</a>: signature should be changed both places it +appears. Fixed issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#160">160</a>: previous version didn't fix the bug in enough places. </li> <li>R15: pre-Toronto mailing. Added issues -<a href="lwg-active.html#233">233</a>-<a href="lwg-defects.html#264">264</a>. Some small HTML formatting +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#233">233</a>-<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#264">264</a>. Some small HTML formatting changes so that we pass Weblint tests. </li> <li>R14: post-Tokyo II mailing; reflects committee actions taken in -Tokyo. Added issues <a href="lwg-defects.html#228">228</a> to <a href="lwg-defects.html#232">232</a>. (00-0019R1/N1242) +Tokyo. Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#228">228</a> to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#232">232</a>. (00-0019R1/N1242) </li> <li>R13: -pre-Tokyo II updated: Added issues <a href="lwg-defects.html#212">212</a> to <a href="lwg-defects.html#227">227</a>. +pre-Tokyo II updated: Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#212">212</a> to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#227">227</a>. </li> <li>R12: -pre-Tokyo II mailing: Added issues <a href="lwg-defects.html#199">199</a> to -<a href="lwg-defects.html#211">211</a>. Added "and paragraph 5" to the proposed resolution -of issue <a href="lwg-defects.html#29">29</a>. Add further rationale to issue -<a href="lwg-closed.html#178">178</a>. +pre-Tokyo II mailing: Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#199">199</a> to +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#211">211</a>. Added "and paragraph 5" to the proposed resolution +of issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#29">29</a>. Add further rationale to issue +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#178">178</a>. </li> <li>R11: post-Kona mailing: Updated to reflect LWG and full committee actions in Kona (99-0048/N1224). Note changed resolution of issues -<a href="lwg-closed.html#4">4</a> and <a href="lwg-defects.html#38">38</a>. Added issues <a href="lwg-closed.html#196">196</a> -to <a href="lwg-defects.html#198">198</a>. Closed issues list split into "defects" and -"closed" documents. Changed the proposed resolution of issue -<a href="lwg-closed.html#4">4</a> to NAD, and changed the wording of proposed resolution -of issue <a href="lwg-defects.html#38">38</a>. +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#4">4</a> and <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#38">38</a>. Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#196">196</a> +to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#198">198</a>. Closed issues list split into "defects" and +"closed" documents. Changed the proposed resolution of issue +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#4">4</a> to NAD, and changed the wording of proposed resolution +of issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#38">38</a>. </li> <li>R10: -pre-Kona updated. Added proposed resolutions <a href="lwg-defects.html#83">83</a>, -<a href="lwg-defects.html#86">86</a>, <a href="lwg-active.html#91">91</a>, <a href="lwg-active.html#92">92</a>, -<a href="lwg-defects.html#109">109</a>. Added issues <a href="lwg-closed.html#190">190</a> to -<a href="lwg-defects.html#195">195</a>. (99-0033/D1209, 14 Oct 99) +pre-Kona updated. Added proposed resolutions <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#83">83</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#86">86</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#91">91</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#92">92</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#109">109</a>. Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#190">190</a> to +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#195">195</a>. (99-0033/D1209, 14 Oct 99) </li> <li>R9: -pre-Kona mailing. Added issues <a href="lwg-closed.html#140">140</a> to -<a href="lwg-defects.html#189">189</a>. Issues list split into separate "active" and -"closed" documents. (99-0030/N1206, 25 Aug 99) +pre-Kona mailing. Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#140">140</a> to +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#189">189</a>. Issues list split into separate "active" and +"closed" documents. (99-0030/N1206, 25 Aug 99) </li> <li>R8: post-Dublin mailing. Updated to reflect LWG and full committee actions in Dublin. (99-0016/N1193, 21 Apr 99) </li> <li>R7: -pre-Dublin updated: Added issues <a href="lwg-closed.html#130">130</a>, <a href="lwg-closed.html#131">131</a>, -<a href="lwg-defects.html#132">132</a>, <a href="lwg-defects.html#133">133</a>, <a href="lwg-defects.html#134">134</a>, -<a href="lwg-closed.html#135">135</a>, <a href="lwg-defects.html#136">136</a>, <a href="lwg-defects.html#137">137</a>, -<a href="lwg-closed.html#138">138</a>, <a href="lwg-defects.html#139">139</a> (31 Mar 99) +pre-Dublin updated: Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#130">130</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#131">131</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#132">132</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#133">133</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#134">134</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#135">135</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#136">136</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#137">137</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#138">138</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#139">139</a> (31 Mar 99) </li> <li>R6: -pre-Dublin mailing. Added issues <a href="lwg-defects.html#127">127</a>, <a href="lwg-closed.html#128">128</a>, -and <a href="lwg-defects.html#129">129</a>. (99-0007/N1194, 22 Feb 99) +pre-Dublin mailing. Added issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#127">127</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#128">128</a>, +and <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#129">129</a>. (99-0007/N1194, 22 Feb 99) </li> <li>R5: -update issues <a href="lwg-defects.html#103">103</a>, <a href="lwg-defects.html#112">112</a>; added issues -<a href="lwg-defects.html#114">114</a> to <a href="lwg-defects.html#126">126</a>. Format revisions to prepare +update issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#103">103</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#112">112</a>; added issues +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#114">114</a> to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#126">126</a>. Format revisions to prepare for making list public. (30 Dec 98) </li> <li>R4: -post-Santa Cruz II updated: Issues <a href="lwg-defects.html#110">110</a>, -<a href="lwg-closed.html#111">111</a>, <a href="lwg-defects.html#112">112</a>, <a href="lwg-closed.html#113">113</a> added, several +post-Santa Cruz II updated: Issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#110">110</a>, +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#111">111</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#112">112</a>, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#113">113</a> added, several issues corrected. (22 Oct 98) </li> <li>R3: -post-Santa Cruz II: Issues <a href="lwg-closed.html#94">94</a> to <a href="lwg-defects.html#109">109</a> +post-Santa Cruz II: Issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#94">94</a> to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#109">109</a> added, many issues updated to reflect LWG consensus (12 Oct 98) </li> <li>R2: -pre-Santa Cruz II: Issues <a href="lwg-closed.html#73">73</a> to <a href="lwg-closed.html#93">93</a> added, -issue <a href="lwg-defects.html#17">17</a> updated. (29 Sep 98) +pre-Santa Cruz II: Issues <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#73">73</a> to <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#93">93</a> added, +issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#17">17</a> updated. (29 Sep 98) </li> <li>R1: -Correction to issue <a href="lwg-defects.html#55">55</a> resolution, <a href="lwg-defects.html#60">60</a> code -format, <a href="lwg-defects.html#64">64</a> title. (17 Sep 98) +Correction to issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#55">55</a> resolution, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#60">60</a> code +format, <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#64">64</a> title. (17 Sep 98) </li> </ul> <h2>Defect Reports</h2> <hr> <a name="1"><h3>1. C library linkage editing oversight</h3></a><p> -<b>Section:</b> 17.4.2.2 <a href="lib-intro.html#lib.using.linkage"> [lib.using.linkage]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 16 Nov 1997</p> +<b>Section:</b> 17.4.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.using.linkage"> [lib.using.linkage]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 16 Nov 1997</p> <p>The change specified in the proposed resolution below did not make it into the Standard. This change was accepted in principle at the London meeting, and the exact wording below was accepted at the Morristown meeting.</p> <p><b>Proposed resolution:</b></p> -<p>Change 17.4.2.2 <a href="lib-intro.html#lib.using.linkage"> [lib.using.linkage]</a> paragraph 2 +<p>Change 17.4.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.using.linkage"> [lib.using.linkage]</a> paragraph 2 from:</p> <blockquote> <p>It is unspecified whether a name from the Standard C library - declared with external linkage has either extern "C" or - extern "C++" linkage.</p> + declared with external linkage has either extern "C" or + extern "C++" linkage.</p> </blockquote> <p>to:</p> <blockquote> <p>Whether a name from the Standard C library declared with external - linkage has extern "C" or extern "C++" linkage + linkage has extern "C" or extern "C++" linkage is implementation defined. It is recommended that an implementation - use extern "C++" linkage for this purpose.</p> + use extern "C++" linkage for this purpose.</p> </blockquote> <hr> <a name="3"><h3>3. Atexit registration during atexit() call is not described</h3></a><p> -<b>Section:</b> 18.3 <a href="lib-support.html#lib.support.start.term"> [lib.support.start.term]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 12 Dec 1997</p> +<b>Section:</b> 18.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.support.start.term"> [lib.support.start.term]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 12 Dec 1997</p> <p>We appear not to have covered all the possibilities of exit processing with respect to atexit registration. <br> @@ -286,7 +303,7 @@ through its definition, and all static objects are destroyed during exit processing. Is the code valid? If so, what are its semantics?</p> <p> -Section 18.3 "Start and termination" says that if a function +Section 18.3 "Start and termination" says that if a function F is registered with atexit before a static object t is initialized, F will not be called until after t's destructor completes.</p> @@ -353,7 +370,7 @@ committee decides. </p> supporting to the proposed resolution.</p> <hr> <a name="5"><h3>5. String::compare specification questionable</h3></a><p> -<b>Section:</b> 21.3.6.8 <a href="lib-strings.html#lib.string::compare"> [lib.string::compare]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Jack Reeves <b>Date:</b> 11 Dec 1997</p> +<b>Section:</b> 21.3.6.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::compare"> [lib.string::compare]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Jack Reeves <b>Date:</b> 11 Dec 1997</p> <p>At the very end of the basic_string class definition is the signature: int compare(size_type pos1, size_type n1, const charT* s, size_type n2 = npos) const; In the following text this is defined as: returns @@ -373,7 +390,7 @@ something like: str.compare(1, str.size()-1, s, strlen(s)-1); </p> pos1, size_type n1, const charT* s) const int compare(size_type pos1, size_type n1, const charT* s, size_type n2) const; each defined in terms of the corresponding constructor. </p> <p><b>Proposed resolution:</b></p> -<p>Replace the compare signature in 21.3 <a href="lib-strings.html#lib.basic.string"> [lib.basic.string]</a> +<p>Replace the compare signature in 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a> (at the very end of the basic_string synopsis) which reads:</p> <blockquote> @@ -392,7 +409,7 @@ charT* s, size_type n2) const; each defined in terms of the corresponding constr size_type n2) const;</tt></p> </blockquote> -<p>Replace the portion of 21.3.6.8 <a href="lib-strings.html#lib.string::compare"> [lib.string::compare]</a> +<p>Replace the portion of 21.3.6.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::compare"> [lib.string::compare]</a> paragraphs 5 and 6 which read:</p> <blockquote> @@ -435,9 +452,9 @@ becomes const, matching the existing synopsis.</p> the Standard which must be fixed. The same problem was also identified in issues 7 (item 5) and 87.</p> <hr> -<a name="7"><h3>7. String clause minor problems</h3></a><p> -<b>Section:</b> 21 <a href="lib-strings.html#lib.strings"> [lib.strings]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 15 Dec 1997</p> -<p>(1) In 21.3.5.4 <a href="lib-strings.html#lib.string::insert"> [lib.string::insert]</a>, the description of template +<a name="7"></a><h3><a name="7">7. String clause minor problems</a></h3><p> +<b>Section:</b> 21 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.strings"> [lib.strings]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 15 Dec 1997</p> +<p>(1) In 21.3.5.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::insert"> [lib.string::insert]</a>, the description of template <class InputIterator> insert(iterator, InputIterator, InputIterator) makes no sense. It refers to a member function that doesn't exist. It also talks about the return value of a void @@ -458,12 +475,12 @@ possible const charT&. </p> charT* in the description. Second, given what it says in RETURNS, leaving out the final argument will always result in an exception getting thrown. This is paragraphs 5 and 6 of -21.3.6.8 <a href="lib-strings.html#lib.string::compare"> [lib.string::compare]</a> +21.3.6.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::compare"> [lib.string::compare]</a> </p> -<p>(6) In table 37, in section 21.1.1 <a href="lib-strings.html#lib.char.traits.require"> [lib.char.traits.require]</a>, -there's a note for X::move(s, p, n). It says "Copies correctly -even where p is in [s, s+n)". This is correct as far as it goes, +<p>(6) In table 37, in section 21.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.char.traits.require"> [lib.char.traits.require]</a>, +there's a note for X::move(s, p, n). It says "Copies correctly +even where p is in [s, s+n)". This is correct as far as it goes, but it doesn't go far enough; it should also guarantee that the copy is correct even where s in in [p, p+n). These are two orthogonal guarantees, and neither one follows from the other. Both guarantees @@ -499,15 +516,15 @@ ITEM 5: Duplicate; see issue 5 (and 87).<br> <br> ITEM 6: In table 37, Replace:<br> <br> - "Copies correctly even where p is in [s, s+n)."<br> + "Copies correctly even where p is in [s, s+n)."<br> <br> with:<br> <br> - "Copies correctly even where the ranges [p, p+n) and [s, -s+n) overlap."</p> + "Copies correctly even where the ranges [p, p+n) and [s, +s+n) overlap."</p> <hr> <a name="8"><h3>8. Locale::global lacks guarantee</h3></a><p> -<b>Section:</b> 22.1.1.5 <a href="lib-locales.html#lib.locale.statics"> [lib.locale.statics]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 24 Dec 1997</p> +<b>Section:</b> 22.1.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.statics"> [lib.locale.statics]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 24 Dec 1997</p> <p>It appears there's an important guarantee missing from clause 22. We're told that invoking locale::global(L) sets the C locale if L has a name. However, we're not told whether or not invoking @@ -516,7 +533,7 @@ setlocale(s) sets the global C++ locale. </p> <p>The intent, I think, is that it should not, but I can't find any such words anywhere. </p> <p><b>Proposed resolution:</b></p> -<p>Add a sentence at the end of 22.1.1.5 <a href="lib-locales.html#lib.locale.statics"> [lib.locale.statics]</a>, +<p>Add a sentence at the end of 22.1.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.statics"> [lib.locale.statics]</a>, paragraph 2: </p> <blockquote> @@ -526,7 +543,7 @@ paragraph 2: </p> </blockquote> <hr> <a name="9"><h3>9. Operator new(0) calls should not yield the same pointer</h3></a><p> -<b>Section:</b> 18.4.1 <a href="lib-support.html#lib.new.delete"> [lib.new.delete]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 4 Jan 1998</p> +<b>Section:</b> 18.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete"> [lib.new.delete]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 4 Jan 1998</p> <p>Scott Meyers, in a comp.std.c++ posting: I just noticed that section 3.7.3.1 of CD2 seems to allow for the possibility that all calls to operator new(0) yield the same pointer, an implementation @@ -581,7 +598,7 @@ list maintainer's note: the IS is the same.]</p> supporting to the proposed resolution.</p> <hr> <a name="11"><h3>11. Bitset minor problems</h3></a><p> -<b>Section:</b> 23.3.5 <a href="lib-containers.html#lib.template.bitset"> [lib.template.bitset]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 22 Jan 1998</p> +<b>Section:</b> 23.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.template.bitset"> [lib.template.bitset]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 22 Jan 1998</p> <p>(1) bitset<>::operator[] is mentioned in the class synopsis (23.3.5), but it is not documented in 23.3.5.2. </p> @@ -595,7 +612,7 @@ go in the Effects clause.</p> <p><b>Proposed resolution:</b></p> <p>ITEMS 1 AND 2:<br> <br> -In the bitset synopsis (23.3.5 <a href="lib-containers.html#lib.template.bitset"> [lib.template.bitset]</a>), +In the bitset synopsis (23.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.template.bitset"> [lib.template.bitset]</a>), replace the member function <br> <br> <tt> reference operator[](size_t pos);<br> @@ -605,7 +622,7 @@ with the two member functions<br> <tt> bool operator[](size_t pos) const; <br> reference operator[](size_t pos); <br> </tt><br> -Add the following text at the end of 23.3.5.2 <a href="lib-containers.html#lib.bitset.members"> [lib.bitset.members]</a>, +Add the following text at the end of 23.3.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.bitset.members"> [lib.bitset.members]</a>, immediately after paragraph 45:</p> <blockquote> @@ -624,71 +641,71 @@ immediately after paragraph 45:</p> </p> </blockquote> <p><b>Rationale:</b></p> -<p>The LWG believes Item 3 is not a defect. "Formatted -input" implies the desired semantics. See 27.6.1.2 <a href="lib-iostreams.html#lib.istream.formatted"> [lib.istream.formatted]</a>. +<p>The LWG believes Item 3 is not a defect. "Formatted +input" implies the desired semantics. See 27.6.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted"> [lib.istream.formatted]</a>. </p> <hr> <a name="13"><h3>13. Eos refuses to die</h3></a><p> -<b>Section:</b> 27.6.1.2.3 <a href="lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> William M. Miller <b>Date:</b> 3 Mar 1998</p> -<p>In 27.6.1.2.3, there is a reference to "eos", which is +<b>Section:</b> 27.6.1.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> William M. Miller <b>Date:</b> 3 Mar 1998</p> +<p>In 27.6.1.2.3, there is a reference to "eos", which is the only one in the whole draft (at least using Acrobat search), so it's undefined. </p> <p><b>Proposed resolution:</b></p> -<p>In 27.6.1.2.3 <a href="lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a>, replace "eos" with -"charT()"</p> +<p>In 27.6.1.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a>, replace "eos" with +"charT()"</p> <hr> <a name="14"><h3>14. Locale::combine should be const</h3></a><p> -<b>Section:</b> 22.1.1.3 <a href="lib-locales.html#lib.locale.members"> [lib.locale.members]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 22.1.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.members"> [lib.locale.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>locale::combine is the only member function of locale (other than constructors and destructor) that is not const. There is no reason for it not to be const, and good reasons why it should have been const. Furthermore, leaving it non-const conflicts with 22.1.1 -paragraph 6: "An instance of a locale is immutable." </p> +paragraph 6: "An instance of a locale is immutable." </p> <p>History: this member function originally was a constructor. it happened that the interface it specified had no corresponding language syntax, so it was changed to a member -function. As constructors are never const, there was no "const" in the interface -which was transformed into member "combine". It should have been added at that +function. As constructors are never const, there was no "const" in the interface +which was transformed into member "combine". It should have been added at that time, but the omission was not noticed. </p> <p><b>Proposed resolution:</b></p> -<p>In 22.1.1 <a href="lib-locales.html#lib.locale"> [lib.locale]</a> and also in 22.1.1.3 <a href="lib-locales.html#lib.locale.members"> [lib.locale.members]</a>, add -"const" to the declaration of member combine: </p> +<p>In 22.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale"> [lib.locale]</a> and also in 22.1.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.members"> [lib.locale.members]</a>, add +"const" to the declaration of member combine: </p> <blockquote> <pre>template <class Facet> locale combine(const locale& other) const; </pre> </blockquote> <hr> <a name="15"><h3>15. Locale::name requirement inconsistent</h3></a><p> -<b>Section:</b> 22.1.1.3 <a href="lib-locales.html#lib.locale.members"> [lib.locale.members]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 22.1.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.members"> [lib.locale.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>locale::name() is described as returning a string that can be passed to a locale constructor, but there is no matching constructor. </p> <p><b>Proposed resolution:</b></p> -<p>In 22.1.1.3 <a href="lib-locales.html#lib.locale.members"> [lib.locale.members]</a>, paragraph 5, replace -"<tt>locale(name())</tt>" with -"<tt>locale(name().c_str())</tt>". +<p>In 22.1.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.members"> [lib.locale.members]</a>, paragraph 5, replace +"<tt>locale(name())</tt>" with +"<tt>locale(name().c_str())</tt>". </p> <hr> <a name="16"><h3>16. Bad ctype_byname<char> decl</h3></a><p> -<b>Section:</b> 22.2.1.4 <a href="lib-locales.html#lib.locale.ctype.byname.special"> [lib.locale.ctype.byname.special]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 22.2.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.byname.special"> [lib.locale.ctype.byname.special]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>The new virtual members ctype_byname<char>::do_widen and do_narrow did not get edited in properly. Instead, the member do_widen appears four times, with wrong argument lists. </p> <p><b>Proposed resolution:</b></p> <p>The correct declarations for the overloaded members <tt>do_narrow</tt> and <tt>do_widen</tt> should be copied -from 22.2.1.3 <a href="lib-locales.html#lib.facet.ctype.special"> [lib.facet.ctype.special]</a>.</p> +from 22.2.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.ctype.special"> [lib.facet.ctype.special]</a>.</p> <hr> <a name="17"><h3>17. Bad bool parsing</h3></a><p> -<b>Section:</b> 22.2.2.1.2 <a href="lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>This section describes the process of parsing a text boolean value from the input -stream. It does not say it recognizes either of the sequences "true" or -"false" and returns the corresponding bool value; instead, it says it recognizes +stream. It does not say it recognizes either of the sequences "true" or +"false" and returns the corresponding bool value; instead, it says it recognizes only one of those sequences, and chooses which according to the received value of a reference argument intended for returning the result, and reports an error if the other sequence is found. (!) Furthermore, it claims to get the names from the ctype<> -facet rather than the numpunct<> facet, and it examines the "boolalpha" -flag wrongly; it doesn't define the value "loc"; and finally, it computes -wrongly whether to use numeric or "alpha" parsing.<br> +facet rather than the numpunct<> facet, and it examines the "boolalpha" +flag wrongly; it doesn't define the value "loc"; and finally, it computes +wrongly whether to use numeric or "alpha" parsing.<br> <br> -I believe the correct algorithm is "as if": </p> +I believe the correct algorithm is "as if": </p> <pre> // in, err, val, and str are arguments. err = 0; @@ -719,14 +736,14 @@ I believe the correct algorithm is "as if": </p> when one is a substring of the other. The proposed text below captures the logic of the code above.</p> <p><b>Proposed resolution:</b></p> -<p>In 22.2.2.1.2 <a href="lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a>, in the first line of paragraph 14, -change "&&" to "&".</p> +<p>In 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a>, in the first line of paragraph 14, +change "&&" to "&".</p> <p>Then, replace paragraphs 15 and 16 as follows:</p> <blockquote> - <p>Otherwise target sequences are determined "as if" by + <p>Otherwise target sequences are determined "as if" by calling the members <tt>falsename()</tt> and <tt>truename()</tt> of the facet obtained by <tt>use_facet<numpunct<charT> >(str.getloc())</tt>. @@ -747,38 +764,38 @@ change "&&" to "&".</p> <tt>(in==end)</tt>. If <tt>val</tt> is not set, then <i>err</i> is set to <tt>str.failbit</tt>; or to <tt>(str.failbit|str.eofbit)</tt>if the reason for the failure was that <tt>(in==end)</tt>. [Example: for targets - <tt>true</tt>:"a" and <tt>false</tt>:"abb", the input sequence "a" yields - <tt>val==true</tt> and <tt>err==str.eofbit</tt>; the input sequence "abc" yields + <tt>true</tt>:"a" and <tt>false</tt>:"abb", the input sequence "a" yields + <tt>val==true</tt> and <tt>err==str.eofbit</tt>; the input sequence "abc" yields <tt>err=str.failbit</tt>, with <tt>in</tt> ending at the 'c' element. For targets - <tt>true</tt>:"1" - and <tt>false</tt>:"0", the input sequence "1" yields <tt>val==true</tt> - and <tt>err=str.goodbit</tt>. For empty targets (""), any input sequence yields + <tt>true</tt>:"1" + and <tt>false</tt>:"0", the input sequence "1" yields <tt>val==true</tt> + and <tt>err=str.goodbit</tt>. For empty targets (""), any input sequence yields <tt>err==str.failbit</tt>. --end example]</p> </blockquote> <hr> <a name="18"><h3>18. Get(...bool&) omitted</h3></a><p> -<b>Section:</b> 22.2.2.1.1 <a href="lib-locales.html#lib.facet.num.get.members"> [lib.facet.num.get.members]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 22.2.2.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.members"> [lib.facet.num.get.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>In the list of num_get<> non-virtual members on page 22-23, the member that parses bool values was omitted from the list of definitions of non-virtual members, though it is listed in the class definition and the corresponding virtual is listed everywhere appropriate. </p> <p><b>Proposed resolution:</b></p> -<p>Add at the beginning of 22.2.2.1.1 <a href="lib-locales.html#lib.facet.num.get.members"> [lib.facet.num.get.members]</a> +<p>Add at the beginning of 22.2.2.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.members"> [lib.facet.num.get.members]</a> another get member for bool&, copied from the entry in -22.2.2.1 <a href="lib-locales.html#lib.locale.num.get"> [lib.locale.num.get]</a>.</p> +22.2.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.num.get"> [lib.locale.num.get]</a>.</p> <hr> -<a name="19"><h3>19. "Noconv" definition too vague</h3></a><p> -<b>Section:</b> 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<a name="19"><h3>19. "Noconv" definition too vague</h3></a><p> +<b>Section:</b> 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p> In the definitions of codecvt<>::do_out and do_in, they are -specified to return noconv if "no conversion is -needed". This definition is too vague, and does not say +specified to return noconv if "no conversion is +needed". This definition is too vague, and does not say normatively what is done with the buffers. </p> <p><b>Proposed resolution:</b></p> <p> Change the entry for noconv in the table under paragraph 4 in section -22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> to read: +22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> to read: </p> <blockquote> <p> @@ -794,24 +811,24 @@ Change the entry for noconv in the table under paragraph 4 in section </blockquote> <hr> <a name="20"><h3>20. Thousands_sep returns wrong type</h3></a><p> -<b>Section:</b> 22.2.3.1.2 <a href="lib-locales.html#lib.facet.numpunct.virtuals"> [lib.facet.numpunct.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 22.2.3.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.numpunct.virtuals"> [lib.facet.numpunct.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>The synopsis for numpunct<>::do_thousands_sep, and the definition of numpunct<>::thousands_sep which calls it, specify that it returns a value of type char_type. Here it is erroneously -described as returning a "string_type". </p> +described as returning a "string_type". </p> <p><b>Proposed resolution:</b></p> -<p>In 22.2.3.1.2 <a href="lib-locales.html#lib.facet.numpunct.virtuals"> [lib.facet.numpunct.virtuals]</a>, above paragraph 2, change -"string_type" to "char_type". </p> +<p>In 22.2.3.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.numpunct.virtuals"> [lib.facet.numpunct.virtuals]</a>, above paragraph 2, change +"string_type" to "char_type". </p> <hr> <a name="21"><h3>21. Codecvt_byname<> instantiations</h3></a><p> -<b>Section:</b> 22.1.1.1.1 <a href="lib-locales.html#lib.locale.category"> [lib.locale.category]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> -<p>In the second table in the section, captioned "Required -instantiations", the instantiations for codecvt_byname<> +<b>Section:</b> 22.1.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.category"> [lib.locale.category]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<p>In the second table in the section, captioned "Required +instantiations", the instantiations for codecvt_byname<> have been omitted. These are necessary to allow users to construct a locale by name from facets. </p> <p><b>Proposed resolution:</b></p> -<p>Add in 22.1.1.1.1 <a href="lib-locales.html#lib.locale.category"> [lib.locale.category]</a> to the table captioned -"Required instantiations", in the category "ctype" +<p>Add in 22.1.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.category"> [lib.locale.category]</a> to the table captioned +"Required instantiations", in the category "ctype" the lines </p> <blockquote> @@ -820,7 +837,7 @@ codecvt_byname<wchar_t,char,mbstate_t> </pre> </blockquote> <hr> <a name="22"><h3>22. Member open vs. flags</h3></a><p> -<b>Section:</b> 27.8.1.7 <a href="lib-iostreams.html#lib.ifstream.members"> [lib.ifstream.members]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 27.8.1.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ifstream.members"> [lib.ifstream.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>The description of basic_istream<>::open leaves unanswered questions about how it responds to or changes flags in the error status for the stream. A strict reading indicates that it ignores the bits and does not change them, which confuses users who do @@ -828,7 +845,7 @@ not expect eofbit and failbit to remain set after a successful open. There are t reasonable resolutions: 1) status quo 2) fail if fail(), ignore eofbit 3) clear failbit and eofbit on call to open(). </p> <p><b>Proposed resolution:</b></p> -<p>In 27.8.1.7 <a href="lib-iostreams.html#lib.ifstream.members"> [lib.ifstream.members]</a> paragraph 3, <i>and</i> in 27.8.1.10 <a href="lib-iostreams.html#lib.ofstream.members"> [lib.ofstream.members]</a> paragraph 3, under open() effects, add a footnote: +<p>In 27.8.1.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ifstream.members"> [lib.ifstream.members]</a> paragraph 3, <i>and</i> in 27.8.1.10 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ofstream.members"> [lib.ofstream.members]</a> paragraph 3, under open() effects, add a footnote: </p> <blockquote> @@ -846,35 +863,35 @@ one case. The resolution of this issue clarifies what the LWG believes to have been the original intent.</p> <hr> -<a name="24"><h3>24. "do_convert" doesn't exist</h3></a><p> -<b>Section:</b> 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<a name="24"><h3>24. "do_convert" doesn't exist</h3></a><p> +<b>Section:</b> 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>The description of codecvt<>::do_out and do_in mentions a -symbol "do_convert" which is not defined in the -standard. This is a leftover from an edit, and should be "do_in -and do_out". </p> +symbol "do_convert" which is not defined in the +standard. This is a leftover from an edit, and should be "do_in +and do_out". </p> <p><b>Proposed resolution:</b></p> -<p>In 22.2.1.5 <a href="lib-locales.html#lib.locale.codecvt"> [lib.locale.codecvt]</a>, paragraph 3, change -"do_convert" to "do_in or do_out". Also, in 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, change "do_convert()" to "do_in -or do_out". </p> +<p>In 22.2.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt"> [lib.locale.codecvt]</a>, paragraph 3, change +"do_convert" to "do_in or do_out". Also, in 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, change "do_convert()" to "do_in +or do_out". </p> <hr> <a name="25"><h3>25. String operator<< uses width() value wrong</h3></a><p> -<b>Section:</b> 21.3.7.9 <a href="lib-strings.html#lib.string.io"> [lib.string.io]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 21.3.7.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.io"> [lib.string.io]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>In the description of operator<< applied to strings, the standard says that uses -the smaller of os.width() and str.size(), to pad "as described in stage 3" +the smaller of os.width() and str.size(), to pad "as described in stage 3" elsewhere; but this is inconsistent, as this allows no possibility of space for padding. </p> <p><b>Proposed resolution:</b></p> -<p>Change 21.3.7.9 <a href="lib-strings.html#lib.string.io"> [lib.string.io]</a> paragraph 4 from:<br> +<p>Change 21.3.7.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.io"> [lib.string.io]</a> paragraph 4 from:<br> <br> - "... where <tt>n</tt> is the smaller of <tt>os.width()</tt> and <tt>str.size()</tt>; -..."<br> + "... where <tt>n</tt> is the smaller of <tt>os.width()</tt> and <tt>str.size()</tt>; +..."<br> <br> to: <br> <br> - "... where <tt>n</tt> is the larger of <tt>os.width()</tt> and <tt>str.size()</tt>; -..."</p> + "... where <tt>n</tt> is the larger of <tt>os.width()</tt> and <tt>str.size()</tt>; +..."</p> <hr> <a name="26"><h3>26. Bad sentry example</h3></a><p> -<b>Section:</b> 27.6.1.1.2 <a href="lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 27.6.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>In paragraph 6, the code in the example: </p> <pre> template <class charT, class traits = char_traits<charT> > @@ -898,7 +915,7 @@ particular, it fails to use traits operators, and specifies incorrect semantics. (E.g. it specifies skipping over the first character in the sequence without examining it.) </p> <p><b>Proposed resolution:</b></p> -<p>Remove the example above from 27.6.1.1.2 <a href="lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a> +<p>Remove the example above from 27.6.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a> paragraph 6.</p> <p><b>Rationale:</b></p> <p>The originally proposed replacement code for the example was not @@ -909,13 +926,13 @@ decided that it would be counter-productive to include such a lengthy example, which might well still contain errors.</p> <hr> <a name="27"><h3>27. String::erase(range) yields wrong iterator</h3></a><p> -<b>Section:</b> 21.3.5.5 <a href="lib-strings.html#lib.string::erase"> [lib.string::erase]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 21.3.5.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::erase"> [lib.string::erase]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>The string::erase(iterator first, iterator last) is specified to return an element one place beyond the next element after the last one erased. E.g. for the string -"abcde", erasing the range ['b'..'d') would yield an iterator for element 'e', +"abcde", erasing the range ['b'..'d') would yield an iterator for element 'e', while 'd' has not been erased. </p> <p><b>Proposed resolution:</b></p> -<p>In 21.3.5.5 <a href="lib-strings.html#lib.string::erase"> [lib.string::erase]</a>, paragraph 10, change: </p> +<p>In 21.3.5.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::erase"> [lib.string::erase]</a>, paragraph 10, change: </p> <blockquote> <p>Returns: an iterator which points to the element immediately following _last_ prior to @@ -929,8 +946,8 @@ while 'd' has not been erased. </p> other elements being erased. </p> </blockquote> <hr> -<a name="28"><h3>28. Ctype<char>is ambiguous</h3></a><p> -<b>Section:</b> 22.2.1.3.2 <a href="lib-locales.html#lib.facet.ctype.char.members"> [lib.facet.ctype.char.members]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<a name="28"></a><h3><a name="28">28. Ctype<char>is ambiguous</a></h3><p> +<b>Section:</b> 22.2.1.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.ctype.char.members"> [lib.facet.ctype.char.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>The description of the vector form of ctype<char>::is can be interpreted to mean something very different from what was intended. Paragraph 4 says </p> @@ -942,7 +959,7 @@ something very different from what was intended. Paragraph 4 says </p> <p>This is intended to copy the value indexed from table()[] into the place identified in vec[]. </p> <p><b>Proposed resolution:</b></p> -<p>Change 22.2.1.3.2 <a href="lib-locales.html#lib.facet.ctype.char.members"> [lib.facet.ctype.char.members]</a>, paragraph 4, to read </p> +<p>Change 22.2.1.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.ctype.char.members"> [lib.facet.ctype.char.members]</a>, paragraph 4, to read </p> <blockquote> <p>Effects: The second form, for all *p in the range [low, high), assigns into vec[p-low] @@ -950,15 +967,15 @@ vec[]. </p> </blockquote> <hr> <a name="29"><h3>29. Ios_base::init doesn't exist</h3></a><p> -<b>Section:</b> 27.3.1 <a href="lib-iostreams.html#lib.narrow.stream.objects"> [lib.narrow.stream.objects]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> -<p>Sections 27.3.1 <a href="lib-iostreams.html#lib.narrow.stream.objects"> [lib.narrow.stream.objects]</a> and 27.3.2 <a href="lib-iostreams.html#lib.wide.stream.objects"> [lib.wide.stream.objects]</a> mention +<b>Section:</b> 27.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.narrow.stream.objects"> [lib.narrow.stream.objects]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<p>Sections 27.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.narrow.stream.objects"> [lib.narrow.stream.objects]</a> and 27.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.wide.stream.objects"> [lib.wide.stream.objects]</a> mention a function ios_base::init, which is not defined. Probably they mean -basic_ios<>::init, defined in 27.4.4.1 <a href="lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a>, +basic_ios<>::init, defined in 27.4.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a>, paragraph 3. </p> <p><b>Proposed resolution:</b></p> <p>[R12: modified to include paragraph 5.]</p> -<p>In 27.3.1 <a href="lib-iostreams.html#lib.narrow.stream.objects"> [lib.narrow.stream.objects]</a> paragraph 2 and 5, change </p> +<p>In 27.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.narrow.stream.objects"> [lib.narrow.stream.objects]</a> paragraph 2 and 5, change </p> <blockquote> <p>ios_base::init </p> @@ -970,7 +987,7 @@ paragraph 3. </p> <p>basic_ios<char>::init </p> </blockquote> -<p>Also, make a similar change in 27.3.2 <a href="lib-iostreams.html#lib.wide.stream.objects"> [lib.wide.stream.objects]</a> except it +<p>Also, make a similar change in 27.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.wide.stream.objects"> [lib.wide.stream.objects]</a> except it should read </p> <blockquote> @@ -978,21 +995,21 @@ should read </p> </blockquote> <hr> <a name="30"><h3>30. Wrong header for LC_*</h3></a><p> -<b>Section:</b> 22.1.1.1.1 <a href="lib-locales.html#lib.locale.category"> [lib.locale.category]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 22.1.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.category"> [lib.locale.category]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>Paragraph 2 implies that the C macros LC_CTYPE etc. are defined in <cctype>, where they are in fact defined elsewhere to appear in <clocale>. </p> <p><b>Proposed resolution:</b></p> -<p>In 22.1.1.1.1 <a href="lib-locales.html#lib.locale.category"> [lib.locale.category]</a>, paragraph 2, change -"<cctype>" to read "<clocale>". </p> +<p>In 22.1.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.category"> [lib.locale.category]</a>, paragraph 2, change +"<cctype>" to read "<clocale>". </p> <hr> <a name="31"><h3>31. Immutable locale values</h3></a><p> -<b>Section:</b> 22.1.1 <a href="lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> -<p>Paragraph 6, says "An instance of <tt>locale</tt> is +<b>Section:</b> 22.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<p>Paragraph 6, says "An instance of <tt>locale</tt> is <i>immutable</i>; once a facet reference is obtained from it, -...". This has caused some confusion, because locale variables +...". This has caused some confusion, because locale variables are manifestly assignable. </p> <p><b>Proposed resolution:</b></p> -<p>In 22.1.1 <a href="lib-locales.html#lib.locale"> [lib.locale]</a> replace paragraph 6</p> +<p>In 22.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale"> [lib.locale]</a> replace paragraph 6</p> <blockquote> <p>An instance of <tt>locale</tt> is immutable; once a facet @@ -1010,7 +1027,7 @@ are manifestly assignable. </p> </blockquote> <hr> <a name="32"><h3>32. Pbackfail description inconsistent</h3></a><p> -<b>Section:</b> 27.5.2.4.4 <a href="lib-iostreams.html#lib.streambuf.virt.pback"> [lib.streambuf.virt.pback]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 27.5.2.4.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.virt.pback"> [lib.streambuf.virt.pback]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>The description of the required state before calling virtual member basic_streambuf<>::pbackfail requirements is inconsistent with the conditions described in 27.5.2.2.4 [lib.streambuf.pub.pback] where member sputbackc calls it. @@ -1024,16 +1041,16 @@ Specifically, the latter says it calls pbackfail if: </p> <p>It appears that the pbackfail description is wrong. </p> <p><b>Proposed resolution:</b></p> -<p>In 27.5.2.4.4 <a href="lib-iostreams.html#lib.streambuf.virt.pback"> [lib.streambuf.virt.pback]</a>, paragraph 1, change:</p> +<p>In 27.5.2.4.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.virt.pback"> [lib.streambuf.virt.pback]</a>, paragraph 1, change:</p> <blockquote> - <p>"<tt>traits::eq(*gptr(),traits::to_char_type( c))</tt>"</p> + <p>"<tt>traits::eq(*gptr(),traits::to_char_type( c))</tt>"</p> </blockquote> <p>to </p> <blockquote> - <p>"<tt>traits::eq(traits::to_char_type(c),gptr()[-1])</tt>" + <p>"<tt>traits::eq(traits::to_char_type(c),gptr()[-1])</tt>" </p> </blockquote> <p><b>Rationale:</b></p> @@ -1041,7 +1058,7 @@ Specifically, the latter says it calls pbackfail if: </p> the argument value.</p> <hr> <a name="33"><h3>33. Codecvt<> mentions from_type</h3></a><p> -<b>Section:</b> 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>In the table defining the results from do_out and do_in, the specification for the result <i>error</i> says </p> @@ -1052,7 +1069,7 @@ result <i>error</i> says </p> <p>but from_type is not defined. This clearly is intended to be an externT for do_in, or an internT for do_out. </p> <p><b>Proposed resolution:</b></p> -<p>In 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> paragraph 4, replace the definition +<p>In 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> paragraph 4, replace the definition in the table for the case of _error_ with </p> <blockquote> @@ -1060,12 +1077,12 @@ in the table for the case of _error_ with </p> </blockquote> <hr> <a name="34"><h3>34. True/falsename() not in ctype<></h3></a><p> -<b>Section:</b> 22.2.2.2.2 <a href="lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 22.2.2.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>In paragraph 19, Effects:, members truename() and falsename are used from facet ctype<charT>, but it has no such members. Note that this is also a problem in 22.2.2.1.2, addressed in (4). </p> <p><b>Proposed resolution:</b></p> -<p>In 22.2.2.2.2 <a href="lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a>, paragraph 19, in the Effects: +<p>In 22.2.2.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a>, paragraph 19, in the Effects: clause for member put(...., bool), replace the initialization of the string_type value s as follows: </p> @@ -1075,13 +1092,13 @@ string_type s = val ? np.truename() : np.falsename(); </pre> </blockquote> <hr> <a name="35"><h3>35. No manipulator unitbuf in synopsis</h3></a><p> -<b>Section:</b> 27.4 <a href="lib-iostreams.html#lib.iostreams.base"> [lib.iostreams.base]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> -<p>In 27.4.5.1 <a href="lib-iostreams.html#lib.fmtflags.manip"> [lib.fmtflags.manip]</a>, we have a definition for a manipulator -named "unitbuf". Unlike other manipulators, it's not listed -in synopsis. Similarly for "nounitbuf". </p> +<b>Section:</b> 27.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostreams.base"> [lib.iostreams.base]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<p>In 27.4.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.fmtflags.manip"> [lib.fmtflags.manip]</a>, we have a definition for a manipulator +named "unitbuf". Unlike other manipulators, it's not listed +in synopsis. Similarly for "nounitbuf". </p> <p><b>Proposed resolution:</b></p> -<p>Add to the synopsis for <ios> in 27.4 <a href="lib-iostreams.html#lib.iostreams.base"> [lib.iostreams.base]</a>, after -the entry for "nouppercase", the prototypes: </p> +<p>Add to the synopsis for <ios> in 27.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostreams.base"> [lib.iostreams.base]</a>, after +the entry for "nouppercase", the prototypes: </p> <blockquote> <pre>ios_base& unitbuf(ios_base& str); @@ -1089,7 +1106,7 @@ ios_base& nounitbuf(ios_base& str); </pre> </blockquote> <hr> <a name="36"><h3>36. Iword & pword storage lifetime omitted</h3></a><p> -<b>Section:</b> 27.4.2.5 <a href="lib-iostreams.html#lib.ios.base.storage"> [lib.ios.base.storage]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 27.4.2.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base.storage"> [lib.ios.base.storage]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>In the definitions for ios_base::iword and pword, the lifetime of the storage is specified badly, so that an implementation which only keeps the last value stored appears to conform. In particular, it says: </p> @@ -1099,7 +1116,7 @@ member with a different index ... </p> <p>This is not idle speculation; at least one implementation was done this way. </p> <p><b>Proposed resolution:</b></p> -<p>Add in 27.4.2.5 <a href="lib-iostreams.html#lib.ios.base.storage"> [lib.ios.base.storage]</a>, in both paragraph 2 and also in +<p>Add in 27.4.2.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base.storage"> [lib.ios.base.storage]</a>, in both paragraph 2 and also in paragraph 4, replace the sentence: </p> <blockquote> @@ -1116,10 +1133,10 @@ paragraph 4, replace the sentence: </p> calling iword [pword] with the same index yields another reference to the same value. </p> </blockquote> -<p>substituting "iword" or "pword" as appropriate. </p> +<p>substituting "iword" or "pword" as appropriate. </p> <hr> -<a name="37"><h3>37. Leftover "global" reference</h3></a><p> -<b>Section:</b> 22.1.1 <a href="lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<a name="37"><h3>37. Leftover "global" reference</h3></a><p> +<b>Section:</b> 22.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>In the overview of locale semantics, paragraph 4, is the sentence </p> <blockquote> @@ -1130,7 +1147,7 @@ paragraph 4, replace the sentence: </p> <p>This is not supported by the definition of use_facet<>, and represents semantics from an old draft. </p> <p><b>Proposed resolution:</b></p> -<p>In 22.1.1 <a href="lib-locales.html#lib.locale"> [lib.locale]</a>, paragraph 4, delete the parenthesized +<p>In 22.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale"> [lib.locale]</a>, paragraph 4, delete the parenthesized expression </p> <blockquote> @@ -1138,9 +1155,9 @@ expression </p> </blockquote> <hr> <a name="38"><h3>38. Facet definition incomplete</h3></a><p> -<b>Section:</b> 22.1.2 <a href="lib-locales.html#lib.locale.global.templates"> [lib.locale.global.templates]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 22.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.global.templates"> [lib.locale.global.templates]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>It has been noticed by Esa Pulkkinen that the definition of -"facet" is incomplete. In particular, a class derived from +"facet" is incomplete. In particular, a class derived from another facet, but which does not define a member <i>id</i>, cannot safely serve as the argument <i>F</i> to use_facet<F>(loc), because there is no guarantee that a reference to the facet instance @@ -1157,19 +1174,19 @@ reads: </p> <blockquote> <p>Requires: <tt>Facet</tt> is a facet class whose definition - contains the public static member <tt>id</tt> as defined in 22.1.1.1.2 <a href="lib-locales.html#lib.locale.facet"> [lib.locale.facet]</a>. </p> + contains the public static member <tt>id</tt> as defined in 22.1.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.facet"> [lib.locale.facet]</a>. </p> </blockquote> <p><i>[ -Kona: strike as overspecification the text "(not inherits)" -from the original resolution, which read "... whose definition +Kona: strike as overspecification the text "(not inherits)" +from the original resolution, which read "... whose definition contains (not inherits) the public static member -<tt>id</tt>..." +<tt>id</tt>..." ]</i></p> <hr> <a name="39"><h3>39. istreambuf_iterator<>::operator++(int) definition garbled</h3></a><p> -<b>Section:</b> 24.5.3.4 <a href="lib-iterators.html#lib.istreambuf.iterator::op%2B%2B"> [lib.istreambuf.iterator::op++]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 24.5.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.istreambuf.iterator::op%2B%2B"> [lib.istreambuf.iterator::op++]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>Following the definition of istreambuf_iterator<>::operator++(int) in paragraph 3, the standard contains three lines of garbage text left over from a previous edit. </p> @@ -1179,28 +1196,28 @@ sbuf_->sbumpc(); return(tmp); </pre> </blockquote> <p><b>Proposed resolution:</b></p> -<p>In 24.5.3.4 <a href="lib-iterators.html#lib.istreambuf.iterator::op%2B%2B"> [lib.istreambuf.iterator::op++]</a>, delete the three lines of code at the +<p>In 24.5.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.istreambuf.iterator::op%2B%2B"> [lib.istreambuf.iterator::op++]</a>, delete the three lines of code at the end of paragraph 3. </p> <hr> <a name="40"><h3>40. Meaningless normative paragraph in examples</h3></a><p> -<b>Section:</b> 22.2.8 <a href="lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 22.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>Paragraph 3 of the locale examples is a description of part of an implementation technique that has lost its referent, and doesn't mean anything. </p> <p><b>Proposed resolution:</b></p> -<p>Delete 22.2.8 <a href="lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> paragraph 3 which begins "This -initialization/identification system depends...", or (at the +<p>Delete 22.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> paragraph 3 which begins "This +initialization/identification system depends...", or (at the editor's option) replace it with a place-holder to keep the paragraph numbering the same. </p> <hr> <a name="41"><h3>41. Ios_base needs clear(), exceptions()</h3></a><p> -<b>Section:</b> 27.4.2 <a href="lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> -<p>The description of ios_base::iword() and pword() in 27.4.2.4 <a href="lib-iostreams.html#lib.ios.members.static"> [lib.ios.members.static]</a>, say that if they fail, they "set badbit, -which may throw an exception". However, ios_base offers no +<b>Section:</b> 27.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<p>The description of ios_base::iword() and pword() in 27.4.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.members.static"> [lib.ios.members.static]</a>, say that if they fail, they "set badbit, +which may throw an exception". However, ios_base offers no interface to set or to test badbit; those interfaces are defined in basic_ios<>. </p> <p><b>Proposed resolution:</b></p> -<p>Change the description in 27.4.2.5 <a href="lib-iostreams.html#lib.ios.base.storage"> [lib.ios.base.storage]</a> in +<p>Change the description in 27.4.2.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base.storage"> [lib.ios.base.storage]</a> in paragraph 2, and also in paragraph 4, as follows. Replace</p> <blockquote> @@ -1221,7 +1238,7 @@ setstate(badbit).]</i></p> <hr> <a name="42"><h3>42. String ctors specify wrong default allocator</h3></a><p> -<b>Section:</b> 21.3 <a href="lib-strings.html#lib.basic.string"> [lib.basic.string]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 6 Aug 1998</p> <p>The basic_string<> copy constructor: </p> <pre>basic_string(const basic_string& str, size_type pos = 0, @@ -1237,7 +1254,7 @@ vector) do not have this form of constructor, so it is inconsistent, and an evident source of confusion, for basic_string<> to have it, so it might better be removed. </p> <p><b>Proposed resolution:</b></p> -<p> In 21.3 <a href="lib-strings.html#lib.basic.string"> [lib.basic.string]</a>, replace the declaration of the copy +<p> In 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a>, replace the declaration of the copy constructor as follows: </p> <blockquote> @@ -1246,7 +1263,7 @@ basic_string(const basic_string& str, size_type pos, size_type n = npos, const Allocator& a = Allocator());</pre> </blockquote> -<p>In 21.3.1 <a href="lib-strings.html#lib.string.cons"> [lib.string.cons]</a>, replace the copy constructor declaration +<p>In 21.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.cons"> [lib.string.cons]</a>, replace the copy constructor declaration as above. Add to paragraph 5, Effects:</p> <blockquote> @@ -1259,7 +1276,7 @@ just an unfortunate design choice.</p> <p>The LWG considered two other possible resolutions:</p> -<p>A. In 21.3 <a href="lib-strings.html#lib.basic.string"> [lib.basic.string]</a>, replace the declaration of the copy +<p>A. In 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a>, replace the declaration of the copy constructor as follows:</p> <blockquote> @@ -1269,7 +1286,7 @@ basic_string(const basic_string& str, size_type pos, size_type n, const Allocator& a); </pre> </blockquote> -<p>In 21.3.1 <a href="lib-strings.html#lib.string.cons"> [lib.string.cons]</a>, replace the copy constructor declaration +<p>In 21.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.cons"> [lib.string.cons]</a>, replace the copy constructor declaration as above. Add to paragraph 5, Effects: </p> <blockquote> @@ -1277,7 +1294,7 @@ as above. Add to paragraph 5, Effects: </p> value <tt>str.get_allocator()</tt>. </p> </blockquote> -<p>B. In 21.3 <a href="lib-strings.html#lib.basic.string"> [lib.basic.string]</a>, and also in 21.3.1 <a href="lib-strings.html#lib.string.cons"> [lib.string.cons]</a>, replace +<p>B. In 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a>, and also in 21.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.cons"> [lib.string.cons]</a>, replace the declaration of the copy constructor as follows: </p> <blockquote> @@ -1286,19 +1303,19 @@ the declaration of the copy constructor as follows: </p> </blockquote> <p>The proposed resolution reflects the original intent of the LWG. It -was also noted by Pete Becker that this fix "will cause -a small amount of existing code to now work correctly."</p> +was also noted by Pete Becker that this fix "will cause +a small amount of existing code to now work correctly."</p> <p><i>[ Kona: issue editing snafu fixed - the proposed resolution now correctly reflects the LWG consensus. ]</i></p> <hr> -<a name="46"><h3>46. Minor Annex D errors</h3></a><p> -<b>Section:</b> D.7 <a href="future.html#depr.str.strstreams"> [depr.str.strstreams]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Brendan Kehoe <b>Date:</b> 1 Jun 1998</p> +<a name="46"></a><h3><a name="46">46. Minor Annex D errors</a></h3><p> +<b>Section:</b> D.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.str.strstreams"> [depr.str.strstreams]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Brendan Kehoe <b>Date:</b> 1 Jun 1998</p> <p>See lib-6522 and edit-814.</p> <p><b>Proposed resolution:</b></p> -<p>Change D.7.1 <a href="future.html#depr.strstreambuf"> [depr.strstreambuf]</a> (since streambuf is a typedef of +<p>Change D.7.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.strstreambuf"> [depr.strstreambuf]</a> (since streambuf is a typedef of basic_streambuf<char>) from:</p> <pre> virtual streambuf<char>* setbuf(char* s, streamsize n);</pre> @@ -1307,7 +1324,7 @@ basic_streambuf<char>) from:</p> <pre> virtual streambuf* setbuf(char* s, streamsize n);</pre> -<p>In D.7.4 <a href="future.html#depr.strstream"> [depr.strstream]</a> insert the semicolon now missing after +<p>In D.7.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.strstream"> [depr.strstream]</a> insert the semicolon now missing after int_type:</p> <pre> namespace std { @@ -1320,29 +1337,29 @@ int_type:</p> typedef typename char_traits<char>::pos_type pos_type;</pre> <hr> <a name="47"><h3>47. Imbue() and getloc() Returns clauses swapped</h3></a><p> -<b>Section:</b> 27.4.2.3 <a href="lib-iostreams.html#lib.ios.base.locales"> [lib.ios.base.locales]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 21 Jun 1998</p> +<b>Section:</b> 27.4.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base.locales"> [lib.ios.base.locales]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 21 Jun 1998</p> <p>Section 27.4.2.3 specifies how imbue() and getloc() work. That section has two RETURNS clauses, and they make no sense as stated. They make perfect sense, though, if you swap them. Am I correct in thinking that paragraphs 2 and 4 just got mixed up by accident?</p> <p><b>Proposed resolution:</b></p> -<p>In 27.4.2.3 <a href="lib-iostreams.html#lib.ios.base.locales"> [lib.ios.base.locales]</a> swap paragraphs 2 and 4.</p> +<p>In 27.4.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base.locales"> [lib.ios.base.locales]</a> swap paragraphs 2 and 4.</p> <hr> <a name="48"><h3>48. Use of non-existent exception constructor</h3></a><p> -<b>Section:</b> 27.4.2.1.1 <a href="lib-iostreams.html#lib.ios::failure"> [lib.ios::failure]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 21 Jun 1998</p> +<b>Section:</b> 27.4.2.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios::failure"> [lib.ios::failure]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 21 Jun 1998</p> <p>27.4.2.1.1, paragraph 2, says that class failure initializes the base class, exception, with exception(msg). Class exception (see 18.6.1) has no such constructor.</p> <p><b>Proposed resolution:</b></p> -<p>Replace 27.4.2.1.1 <a href="lib-iostreams.html#lib.ios::failure"> [lib.ios::failure]</a>, paragraph 2, with</p> +<p>Replace 27.4.2.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios::failure"> [lib.ios::failure]</a>, paragraph 2, with</p> <blockquote> <p>EFFECTS: Constructs an object of class <tt>failure</tt>.</p> </blockquote> <hr> <a name="49"><h3>49. Underspecification of ios_base::sync_with_stdio</h3></a><p> -<b>Section:</b> 27.4.2.4 <a href="lib-iostreams.html#lib.ios.members.static"> [lib.ios.members.static]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 21 Jun 1998</p> +<b>Section:</b> 27.4.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.members.static"> [lib.ios.members.static]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 21 Jun 1998</p> <p>Two problems</p> <p>(1) 27.4.2.4 doesn't say what ios_base::sync_with_stdio(f) @@ -1355,7 +1372,7 @@ synchronized with stdio. Again, of course, I can make some guesses. (And I'm unhappy about the performance implications of those guesses, but that's another matter.)</p> <p><b>Proposed resolution:</b></p> -<p>Change the following sentence in 27.4.2.4 <a href="lib-iostreams.html#lib.ios.members.static"> [lib.ios.members.static]</a> +<p>Change the following sentence in 27.4.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.members.static"> [lib.ios.members.static]</a> returns clause from:</p> <blockquote> @@ -1373,41 +1390,35 @@ returns clause from:</p> <tt>false</tt>.</p> </blockquote> -<p>Add the following immediately after 27.4.2.4 <a href="lib-iostreams.html#lib.ios.members.static"> [lib.ios.members.static]</a>, +<p>Add the following immediately after 27.4.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.members.static"> [lib.ios.members.static]</a>, paragraph 2:</p> <blockquote> <p>When a standard iostream object str is <i>synchronized</i> with a standard stdio stream f, the effect of inserting a character c by</p> -<pre> - fputc(f, c); +<pre> fputc(f, c); </pre> <p>is the same as the effect of</p> -<pre> - str.rdbuf()->sputc(c); +<pre> str.rdbuf()->sputc(c); </pre> <p>for any sequence of characters; the effect of extracting a character c by</p> -<pre> - c = fgetc(f); +<pre> c = fgetc(f); </pre> <p>is the same as the effect of:</p> -<pre> - c = str.rdbuf()->sbumpc(c); +<pre> c = str.rdbuf()->sbumpc(c); </pre> <p>for any sequences of characters; and the effect of pushing back a character c by</p> -<pre> - ungetc(c, f); +<pre> ungetc(c, f); </pre> <p>is the same as the effect of</p> -<pre> - str.rdbuf()->sputbackc(c); +<pre> str.rdbuf()->sputbackc(c); </pre> <p>for any sequence of characters. [<i>Footnote</i>: This implies @@ -1418,14 +1429,14 @@ and a standard stdio object share a buffer. <i>--End Footnote</i>]</p> </blockquote> <p><i>[pre-Copenhagen: PJP and Matt contributed the definition -of "synchronization"]</i></p> +of "synchronization"]</i></p> <p><i>[post-Copenhagen: proposed resolution was revised slightly: text was added in the non-normative footnote to say that operations on the two streams can be mixed arbitrarily.]</i></p> <hr> <a name="50"><h3>50. Copy constructor and assignment operator of ios_base</h3></a><p> -<b>Section:</b> 27.4.2 <a href="lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 21 Jun 1998</p> +<b>Section:</b> 27.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 21 Jun 1998</p> <p>As written, ios_base has a copy constructor and an assignment operator. (Nothing in the standard says it doesn't have one, and all classes have copy constructors and assignment operators unless you @@ -1445,14 +1456,14 @@ that intention would have required a explicit description of the semantics (e.g. what happens to the iarray and parray stuff). </p> <p><b>Proposed resolution:</b></p> -<p>In 27.4.2 <a href="lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a>, class ios_base, specify the copy +<p>In 27.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a>, class ios_base, specify the copy constructor and operator= members as being private.</p> <p><b>Rationale:</b></p> <p>The LWG believes the difficulty of specifying correct semantics outweighs any benefit of allowing ios_base objects to be copyable.</p> <hr> <a name="51"><h3>51. Requirement to not invalidate iterators missing</h3></a><p> -<b>Section:</b> 23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> David Vandevoorde <b>Date:</b> 23 Jun 1998</p> +<b>Section:</b> 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> David Vandevoorde <b>Date:</b> 23 Jun 1998</p> <p>The std::sort algorithm can in general only sort a given sequence by moving around values. The list<>::sort() member on the other hand could move around values or just update internal pointers. Either @@ -1495,23 +1506,23 @@ function otherwise.</p> <p>This was US issue CD2-23-011; it was accepted in London but the change was not made due to an editing oversight. The wording in the proposed resolution below is somewhat updated from CD2-23-011, -particularly the addition of the phrase "or change the values -of"</p> +particularly the addition of the phrase "or change the values +of"</p> <hr> <a name="52"><h3>52. Small I/O problems</h3></a><p> -<b>Section:</b> 27.4.3.2 <a href="lib-iostreams.html#lib.fpos.operations"> [lib.fpos.operations]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 23 Jun 1998</p> -<p>First, 27.4.4.1 <a href="lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a>, table 89. This is pretty obvious: -it should be titled "basic_ios<>() effects", not -"ios_base() effects". </p> +<b>Section:</b> 27.4.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.fpos.operations"> [lib.fpos.operations]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 23 Jun 1998</p> +<p>First, 27.4.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a>, table 89. This is pretty obvious: +it should be titled "basic_ios<>() effects", not +"ios_base() effects". </p> -<p>[The second item is a duplicate; see issue <a href="lwg-closed.html#6">6</a> for +<p>[The second item is a duplicate; see issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#6">6</a> for resolution.]</p> -<p>Second, 27.4.3.2 <a href="lib-iostreams.html#lib.fpos.operations"> [lib.fpos.operations]</a> table 88 . There are a couple +<p>Second, 27.4.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.fpos.operations"> [lib.fpos.operations]</a> table 88 . There are a couple different things wrong with it, some of which I've already discussed with Jerry, but the most obvious mechanical sort of error is that it uses expressions like P(i) and p(i), without ever defining what sort -of thing "i" is. +of thing "i" is. </p> <p>(The other problem is that it requires support for streampos @@ -1522,17 +1533,17 @@ streampos arithmetic, but that it wasn't actually supposed to do anything meaningful except on platforms, like Unix, where genuine arithmetic is possible.) </p> <p><b>Proposed resolution:</b></p> -<p>Change 27.4.4.1 <a href="lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a> table 89 title from -"ios_base() effects" to "basic_ios<>() -effects". </p> +<p>Change 27.4.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a> table 89 title from +"ios_base() effects" to "basic_ios<>() +effects". </p> <hr> <a name="53"><h3>53. Basic_ios destructor unspecified</h3></a><p> -<b>Section:</b> 27.4.4.1 <a href="lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 23 Jun 1998</p> +<b>Section:</b> 27.4.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 23 Jun 1998</p> <p>There's nothing in 27.4.4 saying what basic_ios's destructor does. The important question is whether basic_ios::~basic_ios() destroys rdbuf().</p> <p><b>Proposed resolution:</b></p> -<p>Add after 27.4.4.1 <a href="lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a> paragraph 2:</p> +<p>Add after 27.4.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a> paragraph 2:</p> <blockquote> <p><tt>virtual ~basic_ios();</tt></p> @@ -1542,19 +1553,19 @@ rdbuf().</p> <p><b>Rationale:</b></p> <p>The LWG reviewed the additional question of whether or not <tt>rdbuf(0)</tt> may set <tt>badbit</tt>. The answer is -clearly yes; it may be set via <tt>clear()</tt>. See 27.4.4.2 <a href="lib-iostreams.html#lib.basic.ios.members"> [lib.basic.ios.members]</a>, paragraph 6. This issue was reviewed at length +clearly yes; it may be set via <tt>clear()</tt>. See 27.4.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.basic.ios.members"> [lib.basic.ios.members]</a>, paragraph 6. This issue was reviewed at length by the LWG, which removed from the original proposed resolution a -footnote which incorrectly said "<tt>rdbuf(0)</tt> does not set -<tt>badbit</tt>".</p> +footnote which incorrectly said "<tt>rdbuf(0)</tt> does not set +<tt>badbit</tt>".</p> <hr> <a name="54"><h3>54. Basic_streambuf's destructor</h3></a><p> -<b>Section:</b> 27.5.2.1 <a href="lib-iostreams.html#lib.streambuf.cons"> [lib.streambuf.cons]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 25 Jun 1998</p> +<b>Section:</b> 27.5.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.cons"> [lib.streambuf.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 25 Jun 1998</p> <p>The class synopsis for basic_streambuf shows a (virtual) destructor, but the standard doesn't say what that destructor does. My assumption is that it does nothing, but the standard should say so explicitly. </p> <p><b>Proposed resolution:</b></p> -<p>Add after 27.5.2.1 <a href="lib-iostreams.html#lib.streambuf.cons"> [lib.streambuf.cons]</a> paragraph 2:</p> +<p>Add after 27.5.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.cons"> [lib.streambuf.cons]</a> paragraph 2:</p> <blockquote> <p><tt>virtual ~basic_streambuf();</tt></p> @@ -1563,9 +1574,9 @@ explicitly. </p> </blockquote> <hr> <a name="55"><h3>55. Invalid stream position is undefined</h3></a><p> -<b>Section:</b> 27 <a href="lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 26 Jun 1998</p> +<b>Section:</b> 27 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 26 Jun 1998</p> <p>Several member functions in clause 27 are defined in certain -circumstances to return an "invalid stream position", a term +circumstances to return an "invalid stream position", a term that is defined nowhere in the standard. Two places (27.5.2.4.2, paragraph 4, and 27.8.1.4, paragraph 15) contain a cross-reference to a definition in _lib.iostreams.definitions_, a nonexistent @@ -1574,68 +1585,68 @@ section. </p> <p>I suspect that the invalid stream position is just supposed to be pos_type(-1). Probably best to say explicitly in (for example) 27.5.2.4.2 that the return value is pos_type(-1), rather than to use -the term "invalid stream position", define that term +the term "invalid stream position", define that term somewhere, and then put in a cross-reference. </p> -<p>The phrase "invalid stream position" appears ten times in +<p>The phrase "invalid stream position" appears ten times in the C++ Standard. In seven places it refers to a return value, and it should be changed. In three places it refers to an argument, and it -should not be changed. Here are the three places where "invalid -stream position" should not be changed:</p> +should not be changed. Here are the three places where "invalid +stream position" should not be changed:</p> <blockquote> - <p>27.7.1.3 <a href="lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a>, paragraph 14<br> - 27.8.1.4 <a href="lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a>, paragraph 14<br> - D.7.1.3 <a href="future.html#depr.strstreambuf.virtuals"> [depr.strstreambuf.virtuals]</a>, paragraph 17 + <p>27.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a>, paragraph 14<br> + 27.8.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a>, paragraph 14<br> + D.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.strstreambuf.virtuals"> [depr.strstreambuf.virtuals]</a>, paragraph 17 </p> </blockquote> <p><b>Proposed resolution:</b></p> -<p>In 27.5.2.4.2 <a href="lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a>, paragraph 4, change "Returns an +<p>In 27.5.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a>, paragraph 4, change "Returns an object of class pos_type that stores an invalid stream position -(_lib.iostreams.definitions_)" to "Returns -<tt>pos_type(off_type(-1))</tt>". +(_lib.iostreams.definitions_)" to "Returns +<tt>pos_type(off_type(-1))</tt>". </p> -<p>In 27.5.2.4.2 <a href="lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a>, paragraph 6, change "Returns +<p>In 27.5.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a>, paragraph 6, change "Returns an object of class pos_type that stores an invalid stream -position" to "Returns <tt>pos_type(off_type(-1))</tt>".</p> +position" to "Returns <tt>pos_type(off_type(-1))</tt>".</p> -<p>In 27.7.1.3 <a href="lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a>, paragraph 13, change "the object -stores an invalid stream position" to "the return value is -<tt>pos_type(off_type(-1))</tt>". </p> +<p>In 27.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a>, paragraph 13, change "the object +stores an invalid stream position" to "the return value is +<tt>pos_type(off_type(-1))</tt>". </p> -<p>In 27.8.1.4 <a href="lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a>, paragraph 13, change "returns an -invalid stream position (27.4.3)" to "returns -<tt>pos_type(off_type(-1))</tt>" </p> +<p>In 27.8.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a>, paragraph 13, change "returns an +invalid stream position (27.4.3)" to "returns +<tt>pos_type(off_type(-1))</tt>" </p> -<p>In 27.8.1.4 <a href="lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a>, paragraph 15, change "Otherwise -returns an invalid stream position (_lib.iostreams.definitions_)" -to "Otherwise returns <tt>pos_type(off_type(-1))</tt>" +<p>In 27.8.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a>, paragraph 15, change "Otherwise +returns an invalid stream position (_lib.iostreams.definitions_)" +to "Otherwise returns <tt>pos_type(off_type(-1))</tt>" </p> -<p>In D.7.1.3 <a href="future.html#depr.strstreambuf.virtuals"> [depr.strstreambuf.virtuals]</a>, paragraph 15, change "the object -stores an invalid stream position" to "the return value is -<tt>pos_type(off_type(-1))</tt>" </p> +<p>In D.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.strstreambuf.virtuals"> [depr.strstreambuf.virtuals]</a>, paragraph 15, change "the object +stores an invalid stream position" to "the return value is +<tt>pos_type(off_type(-1))</tt>" </p> -<p>In D.7.1.3 <a href="future.html#depr.strstreambuf.virtuals"> [depr.strstreambuf.virtuals]</a>, paragraph 18, change "the object -stores an invalid stream position" to "the return value is -<tt>pos_type(off_type(-1))</tt>"</p> +<p>In D.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.strstreambuf.virtuals"> [depr.strstreambuf.virtuals]</a>, paragraph 18, change "the object +stores an invalid stream position" to "the return value is +<tt>pos_type(off_type(-1))</tt>"</p> <hr> <a name="56"><h3>56. Showmanyc's return type</h3></a><p> -<b>Section:</b> 27.5.2 <a href="lib-iostreams.html#lib.streambuf"> [lib.streambuf]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 29 Jun 1998</p> +<b>Section:</b> 27.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf"> [lib.streambuf]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 29 Jun 1998</p> <p>The class summary for basic_streambuf<>, in 27.5.2, says that showmanyc has return type int. However, 27.5.2.4.3 says that its return type is streamsize. </p> <p><b>Proposed resolution:</b></p> <p>Change <tt>showmanyc</tt>'s return type in the -27.5.2 <a href="lib-iostreams.html#lib.streambuf"> [lib.streambuf]</a> class summary to <tt>streamsize</tt>.</p> +27.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf"> [lib.streambuf]</a> class summary to <tt>streamsize</tt>.</p> <hr> <a name="57"><h3>57. Mistake in char_traits</h3></a><p> -<b>Section:</b> 21.1.3.2 <a href="lib-strings.html#lib.char.traits.specializations.wchar.t"> [lib.char.traits.specializations.wchar.t]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 1 Jul 1998</p> -<p>21.1.3.2, paragraph 3, says "The types streampos and +<b>Section:</b> 21.1.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.char.traits.specializations.wchar.t"> [lib.char.traits.specializations.wchar.t]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 1 Jul 1998</p> +<p>21.1.3.2, paragraph 3, says "The types streampos and wstreampos may be different if the implementation supports no shift encoding in narrow-oriented iostreams but supports one or more shift -encodings in wide-oriented streams". </p> +encodings in wide-oriented streams". </p> <p>That's wrong: the two are the same type. The <iosfwd> summary in 27.2 says that streampos and wstreampos are, respectively, synonyms @@ -1645,14 +1656,14 @@ to clause 21, we see in 21.1.3.1 and 21.1.3.2 that char_traits<char>::state_type and char_traits<wchar_t>::state_type must both be mbstate_t. </p> <p><b>Proposed resolution:</b></p> -<p>Remove the sentence in 21.1.3.2 <a href="lib-strings.html#lib.char.traits.specializations.wchar.t"> [lib.char.traits.specializations.wchar.t]</a> paragraph 3 which -begins "The types streampos and wstreampos may be -different..." . </p> +<p>Remove the sentence in 21.1.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.char.traits.specializations.wchar.t"> [lib.char.traits.specializations.wchar.t]</a> paragraph 3 which +begins "The types streampos and wstreampos may be +different..." . </p> <hr> <a name="59"><h3>59. Ambiguity in specification of gbump</h3></a><p> -<b>Section:</b> 27.5.2.3.1 <a href="lib-iostreams.html#lib.streambuf.get.area"> [lib.streambuf.get.area]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 28 Jul 1998</p> -<p>27.5.2.3.1 says that basic_streambuf::gbump() "Advances the -next pointer for the input sequence by n." </p> +<b>Section:</b> 27.5.2.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.get.area"> [lib.streambuf.get.area]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 28 Jul 1998</p> +<p>27.5.2.3.1 says that basic_streambuf::gbump() "Advances the +next pointer for the input sequence by n." </p> <p>The straightforward interpretation is that it is just gptr() += n. An alternative interpretation, though, is that it behaves as if it @@ -1660,10 +1671,10 @@ calls sbumpc n times. (The issue, of course, is whether it might ever call underflow.) There is a similar ambiguity in the case of pbump. </p> -<p>(The "classic" AT&T implementation used the +<p>(The "classic" AT&T implementation used the former interpretation.)</p> <p><b>Proposed resolution:</b></p> -<p>Change 27.5.2.3.1 <a href="lib-iostreams.html#lib.streambuf.get.area"> [lib.streambuf.get.area]</a> paragraph 4 gbump effects from:</p> +<p>Change 27.5.2.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.get.area"> [lib.streambuf.get.area]</a> paragraph 4 gbump effects from:</p> <blockquote> <p>Effects: Advances the next pointer for the input sequence by n.</p> @@ -1675,20 +1686,20 @@ former interpretation.)</p> <p>Effects: Adds <tt>n</tt> to the next pointer for the input sequence.</p> </blockquote> -<p>Make the same change to 27.5.2.3.2 <a href="lib-iostreams.html#lib.streambuf.put.area"> [lib.streambuf.put.area]</a> paragraph 4 pbump +<p>Make the same change to 27.5.2.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.put.area"> [lib.streambuf.put.area]</a> paragraph 4 pbump effects.</p> <hr> <a name="60"><h3>60. What is a formatted input function?</h3></a><p> -<b>Section:</b> 27.6.1.2.1 <a href="lib-iostreams.html#lib.istream.formatted.reqmts"> [lib.istream.formatted.reqmts]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 3 Aug 1998</p> +<b>Section:</b> 27.6.1.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted.reqmts"> [lib.istream.formatted.reqmts]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 3 Aug 1998</p> <p>Paragraph 1 of 27.6.1.2.1 contains general requirements for all formatted input functions. Some of the functions defined in section -27.6.1.2 explicitly say that those requirements apply ("Behaves -like a formatted input member (as described in 27.6.1.2.1)"), but +27.6.1.2 explicitly say that those requirements apply ("Behaves +like a formatted input member (as described in 27.6.1.2.1)"), but others don't. The question: is 27.6.1.2.1 supposed to apply to everything in 27.6.1.2, or only to those member functions that -explicitly say "behaves like a formatted input member"? Or +explicitly say "behaves like a formatted input member"? Or to put it differently: are we to assume that everything that appears -in a section called "Formatted input functions" really is a +in a section called "Formatted input functions" really is a formatted input function? I assume that 27.6.1.2.1 is intended to apply to the arithmetic extractors (27.6.1.2.2), but I assume that it is not intended to apply to extractors like </p> @@ -1706,102 +1717,102 @@ output. </p> basic_istream and basic_ostream operator <<()'s that are used for the manipulators and streambuf* are in the wrong section and should have their own separate section or be modified to make it clear -that the "Common requirements" listed in section 27.6.1.2.1 +that the "Common requirements" listed in section 27.6.1.2.1 (for basic_istream) and section 27.6.2.5.1 (for basic_ostream) do not apply to them. </p> -<p>Additional comments from Dietmar Kühl: It appears to be somewhat -nonsensical to consider the functions defined in 27.6.1.2.3 <a href="lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a> paragraphs 1 to 5 to be "Formatted input -function" but since these functions are defined in a section -labeled "Formatted input functions" it is unclear to me +<p>Additional comments from Dietmar Kühl: It appears to be somewhat +nonsensical to consider the functions defined in 27.6.1.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a> paragraphs 1 to 5 to be "Formatted input +function" but since these functions are defined in a section +labeled "Formatted input functions" it is unclear to me whether these operators are considered formatted input functions which -have to conform to the "common requirements" from 27.6.1.2.1 <a href="lib-iostreams.html#lib.istream.formatted.reqmts"> [lib.istream.formatted.reqmts]</a>: If this is the case, all manipulators, not +have to conform to the "common requirements" from 27.6.1.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted.reqmts"> [lib.istream.formatted.reqmts]</a>: If this is the case, all manipulators, not just <tt>ws</tt>, would skip whitespace unless <tt>noskipws</tt> is set (... but setting <tt>noskipws</tt> using the manipulator syntax would also skip whitespace :-)</p> <p>It is not clear which functions are to be considered unformatted input functions. As written, it seems -that all functions in 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> are unformatted input +that all functions in 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> are unformatted input functions. However, it does not really make much sense to construct a sentry object for <tt>gcount()</tt>, <tt>sync()</tt>, ... Also it is unclear what happens to the <tt>gcount()</tt> if eg. <tt>gcount()</tt>, <tt>putback()</tt>, <tt>unget()</tt>, or <tt>sync()</tt> is called: These functions don't extract characters, -some of them even "unextract" a character. Should this still +some of them even "unextract" a character. Should this still be reflected in <tt>gcount()</tt>? Of course, it could be read as if after a call to <tt>gcount()</tt> <tt>gcount()</tt> return <tt>0</tt> (the last unformatted input function, <tt>gcount()</tt>, didn't extract any character) and after a call to <tt>putback()</tt> <tt>gcount()</tt> returns <tt>-1</tt> (the last unformatted input -function <tt>putback()</tt> did "extract" back into the +function <tt>putback()</tt> did "extract" back into the stream). Correspondingly for <tt>unget()</tt>. Is this what is intended? If so, this should be clarified. Otherwise, a corresponding clarification should be used.</p> <p><b>Proposed resolution:</b></p> <p> In 27.6.1.2.2 [lib.istream.formatted.arithmetic], paragraph 1. -Change the beginning of the second sentence from "The conversion -occurs" to "These extractors behave as formatted input functions (as +Change the beginning of the second sentence from "The conversion +occurs" to "These extractors behave as formatted input functions (as described in 27.6.1.2.1). After a sentry object is constructed, -the conversion occurs" +the conversion occurs" </p> <p> In 27.6.1.2.3, [lib.istream::extractors], before paragraph 1. -Add an effects clause. "Effects: None. This extractor does +Add an effects clause. "Effects: None. This extractor does not behave as a formatted input function (as described in 27.6.1.2.1). </p> <p> In 27.6.1.2.3, [lib.istream::extractors], paragraph 2. Change the -effects clause to "Effects: Calls pf(*this). This extractor does not +effects clause to "Effects: Calls pf(*this). This extractor does not behave as a formatted input function (as described in 27.6.1.2.1). </p> <p> In 27.6.1.2.3, [lib.istream::extractors], paragraph 4. Change the -effects clause to "Effects: Calls pf(*this). This extractor does not +effects clause to "Effects: Calls pf(*this). This extractor does not behave as a formatted input function (as described in 27.6.1.2.1). </p> <p> In 27.6.1.2.3, [lib.istream::extractors], paragraph 12. Change the -first two sentences from "If sb is null, calls setstate(failbit), +first two sentences from "If sb is null, calls setstate(failbit), which may throw ios_base::failure (27.4.4.3). Extracts characters -from *this..." to "Behaves as a formatted input function (as described +from *this..." to "Behaves as a formatted input function (as described in 27.6.1.2.1). If sb is null, calls setstate(failbit), which may throw ios_base::failure (27.4.4.3). After a sentry object is -constructed, extracts characters from *this...". +constructed, extracts characters from *this...". </p> <p> In 27.6.1.3, [lib.istream.unformatted], before paragraph 2. Add an -effects clause. "Effects: none. This member function does not behave -as an unformatted input function (as described in 27.6.1.3, paragraph 1)." +effects clause. "Effects: none. This member function does not behave +as an unformatted input function (as described in 27.6.1.3, paragraph 1)." </p> <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 3. Change the -beginning of the first sentence of the effects clause from "Extracts a -character" to "Behaves as an unformatted input function (as described +beginning of the first sentence of the effects clause from "Extracts a +character" to "Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1). After constructing a sentry object, extracts a -character" +character" </p> <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 5. Change the -beginning of the first sentence of the effects clause from "Extracts a -character" to "Behaves as an unformatted input function (as described +beginning of the first sentence of the effects clause from "Extracts a +character" to "Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1). After constructing a sentry object, extracts a -character" +character" </p> <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 5. Change the -beginning of the first sentence of the effects clause from "Extracts -characters" to "Behaves as an unformatted input function (as described +beginning of the first sentence of the effects clause from "Extracts +characters" to "Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1). After constructing a sentry object, extracts -characters" +characters" </p> <p> @@ -1810,10 +1821,10 @@ characters" <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 12. Change the -beginning of the first sentence of the effects clause from "Extracts -characters" to "Behaves as an unformatted input function (as described +beginning of the first sentence of the effects clause from "Extracts +characters" to "Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1). After constructing a sentry object, extracts -characters" +characters" </p> <p> @@ -1822,10 +1833,10 @@ characters" <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 17. Change the -beginning of the first sentence of the effects clause from "Extracts -characters" to "Behaves as an unformatted input function (as described +beginning of the first sentence of the effects clause from "Extracts +characters" to "Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1). After constructing a sentry object, extracts -characters" +characters" </p> <p> @@ -1834,75 +1845,75 @@ characters" <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 24. Change the -beginning of the first sentence of the effects clause from "Extracts -characters" to "Behaves as an unformatted input function (as described +beginning of the first sentence of the effects clause from "Extracts +characters" to "Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1). After constructing a sentry object, extracts -characters" +characters" </p> <p> In 27.6.1.3, [lib.istream.unformatted], before paragraph 27. Add an -Effects clause: "Effects: Behaves as an unformatted input function (as +Effects clause: "Effects: Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1). After constructing a sentry -object, reads but does not extract the current input character." +object, reads but does not extract the current input character." </p> <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 28. Change the -first sentence of the Effects clause from "If !good() calls" to +first sentence of the Effects clause from "If !good() calls" to Behaves as an unformatted input function (as described in 27.6.1.3, -paragraph 1). After constructing a sentry object, if !good() calls" +paragraph 1). After constructing a sentry object, if !good() calls" </p> <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 30. Change the -first sentence of the Effects clause from "If !good() calls" to -"Behaves as an unformatted input function (as described in 27.6.1.3, -paragraph 1). After constructing a sentry object, if !good() calls" +first sentence of the Effects clause from "If !good() calls" to +"Behaves as an unformatted input function (as described in 27.6.1.3, +paragraph 1). After constructing a sentry object, if !good() calls" </p> <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 32. Change the -first sentence of the Effects clause from "If !good() calls..." to -"Behaves as an unformatted input function (as described in 27.6.1.3, +first sentence of the Effects clause from "If !good() calls..." to +"Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1). After constructing a sentry object, if !good() -calls..." Add a new sentence to the end of the Effects clause: -"[Note: this function extracts no characters, so the value returned -by the next call to gcount() is 0.]" +calls..." Add a new sentence to the end of the Effects clause: +"[Note: this function extracts no characters, so the value returned +by the next call to gcount() is 0.]" </p> <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 34. Change the -first sentence of the Effects clause from "If !good() calls" to -"Behaves as an unformatted input function (as described in 27.6.1.3, -paragraph 1). After constructing a sentry object, if !good() calls". -Add a new sentence to the end of the Effects clause: "[Note: this +first sentence of the Effects clause from "If !good() calls" to +"Behaves as an unformatted input function (as described in 27.6.1.3, +paragraph 1). After constructing a sentry object, if !good() calls". +Add a new sentence to the end of the Effects clause: "[Note: this function extracts no characters, so the value returned by the next -call to gcount() is 0.]" +call to gcount() is 0.]" </p> <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 36. Change the -first sentence of the Effects clause from "If !rdbuf() is" to "Behaves +first sentence of the Effects clause from "If !rdbuf() is" to "Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1), except that it does not count the number of characters extracted and does not affect the value returned by subsequent calls to -gcount(). After constructing a sentry object, if rdbuf() is" +gcount(). After constructing a sentry object, if rdbuf() is" </p> <p> In 27.6.1.3, [lib.istream.unformatted], before paragraph 37. Add an -Effects clause: "Effects: Behaves as an unformatted input function (as +Effects clause: "Effects: Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1), except that it does not count the number of characters extracted and does not affect the value returned -by subsequent calls to gcount()." Change the first sentence of -paragraph 37 from "if fail()" to "after constructing a sentry object, -if fail()". +by subsequent calls to gcount()." Change the first sentence of +paragraph 37 from "if fail()" to "after constructing a sentry object, +if fail()". </p> <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 38. Change the -first sentence of the Effects clause from "If fail()" to "Behaves +first sentence of the Effects clause from "If fail()" to "Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1), except that it does not count the number of characters extracted and does not affect the value returned by subsequent calls to @@ -1911,7 +1922,7 @@ gcount(). After constructing a sentry object, if fail() <p> In 27.6.1.3, [lib.istream.unformatted], paragraph 40. Change the -first sentence of the Effects clause from "If fail()" to "Behaves +first sentence of the Effects clause from "If fail()" to "Behaves as an unformatted input function (as described in 27.6.1.3, paragraph 1), except that it does not count the number of characters extracted and does not affect the value returned by subsequent calls to @@ -1920,55 +1931,55 @@ gcount(). After constructing a sentry object, if fail() <p> In 27.6.2.5.2 [lib.ostream.inserters.arithmetic], paragraph 1. Change -the beginning of the third sentence from "The formatting conversion" -to "These extractors behave as formatted output functions (as +the beginning of the third sentence from "The formatting conversion" +to "These extractors behave as formatted output functions (as described in 27.6.2.5.1). After the sentry object is constructed, the -conversion occurs". +conversion occurs". </p> <p> In 27.6.2.5.3 [lib.ostream.inserters], before paragraph 1. Add an -effects clause: "Effects: None. Does not behave as a formatted output -function (as described in 27.6.2.5.1).". +effects clause: "Effects: None. Does not behave as a formatted output +function (as described in 27.6.2.5.1).". </p> <p> In 27.6.2.5.3 [lib.ostream.inserters], paragraph 2. Change the -effects clause to "Effects: calls pf(*this). This extractor does not -behave as a formatted output function (as described in 27.6.2.5.1).". +effects clause to "Effects: calls pf(*this). This extractor does not +behave as a formatted output function (as described in 27.6.2.5.1).". </p> <p> In 27.6.2.5.3 [lib.ostream.inserters], paragraph 4. Change the -effects clause to "Effects: calls pf(*this). This extractor does not -behave as a formatted output function (as described in 27.6.2.5.1).". +effects clause to "Effects: calls pf(*this). This extractor does not +behave as a formatted output function (as described in 27.6.2.5.1).". </p> <p> In 27.6.2.5.3 [lib.ostream.inserters], paragraph 6. Change the first -sentence from "If sb" to "Behaves as a formatted output function (as +sentence from "If sb" to "Behaves as a formatted output function (as described in 27.6.2.5.1). After the sentry object is constructed, if -sb". +sb". </p> <p> In 27.6.2.6 [lib.ostream.unformatted], paragraph 2. Change the first -sentence from "Inserts the character" to "Behaves as an unformatted +sentence from "Inserts the character" to "Behaves as an unformatted output function (as described in 27.6.2.6, paragraph 1). After -constructing a sentry object, inserts the character". +constructing a sentry object, inserts the character". </p> <p> In 27.6.2.6 [lib.ostream.unformatted], paragraph 5. Change the first -sentence from "Obtains characters" to "Behaves as an unformatted +sentence from "Obtains characters" to "Behaves as an unformatted output function (as described in 27.6.2.6, paragraph 1). After -constructing a sentry object, obtains characters". +constructing a sentry object, obtains characters". </p> <p> In 27.6.2.6 [lib.ostream.unformatted], paragraph 7. Add a new -sentence at the end of the paragraph: "Does not behave as an -unformatted output function (as described in 27.6.2.6, paragraph 1)." +sentence at the end of the paragraph: "Does not behave as an +unformatted output function (as described in 27.6.2.6, paragraph 1)." </p> <p><b>Rationale:</b></p> <p>See J16/99-0043==WG21/N1219, Proposed Resolution to Library Issue 60, @@ -1976,7 +1987,7 @@ by Judy Ward and Matt Austern. This proposed resolution is section VI of that paper.</p> <hr> <a name="61"><h3>61. Ambiguity in iostreams exception policy</h3></a><p> -<b>Section:</b> 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 6 Aug 1998</p> +<b>Section:</b> 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 6 Aug 1998</p> <p>The introduction to the section on unformatted input (27.6.1.3) says that every unformatted input function catches all exceptions that were thrown during input, sets badbit, and then conditionally rethrows @@ -1986,7 +1997,7 @@ circumstances as setting eofbit and/or failbit. (The standard notes, correctly, that setting eofbit or failbit can sometimes result in an exception being thrown.) The question: if one of these functions throws an exception triggered by setting failbit, is this an exception -"thrown during input" and hence covered by 27.6.1.3, or does +"thrown during input" and hence covered by 27.6.1.3, or does 27.6.1.3 only refer to a limited class of exceptions? Just to make this concrete, suppose you have the following snippet. </p> @@ -2003,29 +2014,29 @@ be thrown? </p> <p><b>Proposed resolution:</b></p> <p> In 27.6.1.3, paragraph 1, after the sentence that begins -"If an exception is thrown...", add the following -parenthetical comment: "(Exceptions thrown from -<tt>basic_ios<>::clear()</tt> are not caught or rethrown.)" +"If an exception is thrown...", add the following +parenthetical comment: "(Exceptions thrown from +<tt>basic_ios<>::clear()</tt> are not caught or rethrown.)" </p> <p><b>Rationale:</b></p> <p>The LWG looked to two alternative wordings, and choose the proposed resolution as better standardese.</p> <hr> -<a name="62"><h3>62. <tt>Sync</tt>'s return value</h3></a><p> -<b>Section:</b> 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 6 Aug 1998</p> +<a name="62"></a><h3><a name="62">62. <tt>Sync</tt>'s return value</a></h3><p> +<b>Section:</b> 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 6 Aug 1998</p> <p>The Effects clause for sync() (27.6.1.3, paragraph 36) says that it -"calls rdbuf()->pubsync() and, if that function returns -1 -... returns traits::eof()." </p> +"calls rdbuf()->pubsync() and, if that function returns -1 +... returns traits::eof()." </p> <p>That looks suspicious, because traits::eof() is of type traits::int_type while the return type of sync() is int. </p> <p><b>Proposed resolution:</b></p> -<p>In 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>, paragraph 36, change "returns -<tt>traits::eof()</tt>" to "returns <tt>-1</tt>". +<p>In 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>, paragraph 36, change "returns +<tt>traits::eof()</tt>" to "returns <tt>-1</tt>". </p> <hr> <a name="63"><h3>63. Exception-handling policy for unformatted output</h3></a><p> -<b>Section:</b> 27.6.2.6 <a href="lib-iostreams.html#lib.ostream.unformatted"> [lib.ostream.unformatted]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 11 Aug 1998</p> +<b>Section:</b> 27.6.2.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.unformatted"> [lib.ostream.unformatted]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 11 Aug 1998</p> <p>Clause 27 details an exception-handling policy for formatted input, unformatted input, and formatted output. It says nothing for unformatted output (27.6.2.6). 27.6.2.6 should either include the same @@ -2034,10 +2045,10 @@ else it should have a footnote saying that the omission is deliberate. </p> <p><b>Proposed resolution:</b></p> <p> -In 27.6.2.6, paragraph 1, replace the last sentence ("In any +In 27.6.2.6, paragraph 1, replace the last sentence ("In any case, the unformatted output function ends by destroying the sentry object, then returning the value specified for the formatted output -function.") with the following text: +function.") with the following text: </p> <blockquote> If an exception is thrown during output, then <tt>ios::badbit</tt> is @@ -2056,13 +2067,13 @@ input, unformatted input, and formatted output. <hr> <a name="64"><h3>64. Exception handling in <tt>basic_istream::operator>>(basic_streambuf*)</tt> </h3></a><p> -<b>Section:</b> 27.6.1.2.3 <a href="lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 11 Aug 1998 </p> +<b>Section:</b> 27.6.1.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 11 Aug 1998 </p> <p>27.6.1.2.3, paragraph 13, is ambiguous. It can be interpreted two different ways, depending on whether the second sentence is read as an elaboration of the first. </p> <p><b>Proposed resolution:</b></p> -<p>Replace 27.6.1.2.3 <a href="lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a>, paragraph 13, which begins -"If the function inserts no characters ..." with:</p> +<p>Replace 27.6.1.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a>, paragraph 13, which begins +"If the function inserts no characters ..." with:</p> <blockquote> <p>If the function inserts no characters, it calls @@ -2074,16 +2085,16 @@ elaboration of the first. </p> </blockquote> <hr> <a name="66"><h3>66. Strstreambuf::setbuf</h3></a><p> -<b>Section:</b> D.7.1.3 <a href="future.html#depr.strstreambuf.virtuals"> [depr.strstreambuf.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 18 Aug 1998</p> +<b>Section:</b> D.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.strstreambuf.virtuals"> [depr.strstreambuf.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 18 Aug 1998</p> <p>D.7.1.3, paragraph 19, says that strstreambuf::setbuf -"Performs an operation that is defined separately for each class -derived from strstreambuf". This is obviously an incorrect +"Performs an operation that is defined separately for each class +derived from strstreambuf". This is obviously an incorrect cut-and-paste from basic_streambuf. There are no classes derived from strstreambuf. </p> <p><b>Proposed resolution:</b></p> -<p>D.7.1.3 <a href="future.html#depr.strstreambuf.virtuals"> [depr.strstreambuf.virtuals]</a>, paragraph 19, replace the setbuf effects -clause which currently says "Performs an operation that is -defined separately for each class derived from strstreambuf" +<p>D.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.strstreambuf.virtuals"> [depr.strstreambuf.virtuals]</a>, paragraph 19, replace the setbuf effects +clause which currently says "Performs an operation that is +defined separately for each class derived from strstreambuf" with:</p> <blockquote> @@ -2093,7 +2104,7 @@ with:</p> </blockquote> <hr> <a name="68"><h3>68. Extractors for char* should store null at end</h3></a><p> -<b>Section:</b> 27.6.1.2.3 <a href="lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 14 Jul 1998</p> +<b>Section:</b> 27.6.1.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 14 Jul 1998</p> <p>Extractors for char* (27.6.1.2.3) do not store a null character after the extracted character sequence whereas the unformatted functions like get() do. Why is this?</p> @@ -2103,7 +2114,7 @@ glitch. You'll notice that the last item of the list of what stops extraction doesn't make any sense. It was supposed to be the line that said a null is stored.</p> <p><b>Proposed resolution:</b></p> -<p>27.6.1.2.3 <a href="lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a>, paragraph 7, change the last list +<p>27.6.1.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::extractors"> [lib.istream::extractors]</a>, paragraph 7, change the last list item from:</p> <blockquote> @@ -2120,15 +2131,15 @@ item from:</p> </blockquote> <hr> <a name="69"><h3>69. Must elements of a vector be contiguous?</h3></a><p> -<b>Section:</b> 23.2.4 <a href="lib-containers.html#lib.vector"> [lib.vector]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 29 Jul 1998</p> +<b>Section:</b> 23.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector"> [lib.vector]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 29 Jul 1998</p> <p>The issue is this: Must the elements of a vector be in contiguous memory?</p> <p>(Please note that this is entirely separate from the question of whether a vector iterator is required to be a pointer; the answer to -that question is clearly "no," as it would rule out +that question is clearly "no," as it would rule out debugging implementations)</p> <p><b>Proposed resolution:</b></p> -<p>Add the following text to the end of 23.2.4 <a href="lib-containers.html#lib.vector"> [lib.vector]</a>, +<p>Add the following text to the end of 23.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector"> [lib.vector]</a>, paragraph 1. </p> <blockquote> @@ -2139,22 +2150,22 @@ paragraph 1. </p> </blockquote> <p><b>Rationale:</b></p> <p>The LWG feels that as a practical matter the answer is clearly -"yes". There was considerable discussion as to the best way -to express the concept of "contiguous", which is not +"yes". There was considerable discussion as to the best way +to express the concept of "contiguous", which is not directly defined in the standard. Discussion included:</p> <ul> <li>An operational definition similar to the above proposed resolution is - already used for valarray (26.3.2.3 <a href="lib-numerics.html#lib.valarray.access"> [lib.valarray.access]</a>).</li> + already used for valarray (26.3.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.valarray.access"> [lib.valarray.access]</a>).</li> <li>There is no need to explicitly consider a user-defined operator& - because elements must be copyconstructible (23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> para 3) - and copyconstructible (20.1.3 <a href="lib-utilities.html#lib.copyconstructible"> [lib.copyconstructible]</a>) specifies + because elements must be copyconstructible (23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> para 3) + and copyconstructible (20.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.copyconstructible"> [lib.copyconstructible]</a>) specifies requirements for operator&.</li> <li>There is no issue of one-past-the-end because of language rules.</li> </ul> <hr> <a name="70"><h3>70. Uncaught_exception() missing throw() specification</h3></a><p> -<b>Section:</b> 18.6 <a href="lib-support.html#lib.support.exception"> [lib.support.exception]</a>, 18.6.4 <a href="lib-support.html#lib.uncaught"> [lib.uncaught]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> Unknown</p> +<b>Section:</b> 18.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.support.exception"> [lib.support.exception]</a>, 18.6.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.uncaught"> [lib.uncaught]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> Unknown</p> <p>In article 3E04@pratique.fr, Valentin Bonnard writes: </p> <p>uncaught_exception() doesn't have a throw specification.</p> @@ -2165,18 +2176,18 @@ handle exceptions thrown from uncaught_exception() ?</p> <p>uncaught_exception() is called in exception handling contexts where exception safety is very important.</p> <p><b>Proposed resolution:</b></p> -<p>In 15.5.3 <a href="except.html#except.uncaught"> [except.uncaught]</a>, paragraph 1, 18.6 <a href="lib-support.html#lib.support.exception"> [lib.support.exception]</a>, and 18.6.4 <a href="lib-support.html#lib.uncaught"> [lib.uncaught]</a>, add "throw()" to uncaught_exception().</p> +<p>In 15.5.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/except.html#except.uncaught"> [except.uncaught]</a>, paragraph 1, 18.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.support.exception"> [lib.support.exception]</a>, and 18.6.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.uncaught"> [lib.uncaught]</a>, add "throw()" to uncaught_exception().</p> <hr> <a name="71"><h3>71. Do_get_monthname synopsis missing argument</h3></a><p> -<b>Section:</b> 22.2.5.1 <a href="lib-locales.html#lib.locale.time.get"> [lib.locale.time.get]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 13 Aug 1998</p> +<b>Section:</b> 22.2.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.time.get"> [lib.locale.time.get]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 13 Aug 1998</p> <p>The locale facet member <tt>time_get<>::do_get_monthname</tt> -is described in 22.2.5.1.2 <a href="lib-locales.html#lib.locale.time.get.virtuals"> [lib.locale.time.get.virtuals]</a> with five arguments, +is described in 22.2.5.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.time.get.virtuals"> [lib.locale.time.get.virtuals]</a> with five arguments, consistent with do_get_weekday and with its specified use by member get_monthname. However, in the synopsis, it is specified instead with -four arguments. The missing argument is the "end" iterator +four arguments. The missing argument is the "end" iterator value.</p> <p><b>Proposed resolution:</b></p> -<p>In 22.2.5.1 <a href="lib-locales.html#lib.locale.time.get"> [lib.locale.time.get]</a>, add an "end" argument to +<p>In 22.2.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.time.get"> [lib.locale.time.get]</a>, add an "end" argument to the declaration of member do_monthname as follows:</p> <pre> virtual iter_type do_get_monthname(iter_type s, iter_type end, ios_base&, @@ -2184,12 +2195,12 @@ the declaration of member do_monthname as follows:</p> <hr> <a name="74"><h3>74. Garbled text for <tt>codecvt::do_max_length</tt> </h3></a><p> -<b>Section:</b> 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 8 Sep 1998</p> -<p>The text of <tt>codecvt::do_max_length</tt>'s "Returns" +<b>Section:</b> 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 8 Sep 1998</p> +<p>The text of <tt>codecvt::do_max_length</tt>'s "Returns" clause (22.2.1.5.2, paragraph 11) is garbled. It has unbalanced parentheses and a spurious <b>n</b>.</p> <p><b>Proposed resolution:</b></p> -<p>Replace 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> paragraph 11 with the +<p>Replace 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> paragraph 11 with the following:</p> <blockquote> @@ -2201,7 +2212,7 @@ following:</p> </blockquote> <hr> <a name="75"><h3>75. Contradiction in <tt>codecvt::length</tt>'s argument types</h3></a><p> -<b>Section:</b> 22.2.1.5 <a href="lib-locales.html#lib.locale.codecvt"> [lib.locale.codecvt]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt +<b>Section:</b> 22.2.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt"> [lib.locale.codecvt]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 18 Sep 1998</p> <p>The class synopses for classes <tt>codecvt<></tt> (22.2.1.5) and <tt>codecvt_byname<></tt> (22.2.1.6) say that the first @@ -2215,7 +2226,7 @@ synopsis or the summary must be changed. </p> then we must also add text saying how <tt>do_length</tt> changes its <tt>stateT</tt> argument. </p> <p><b>Proposed resolution:</b></p> -<p>In 22.2.1.5 <a href="lib-locales.html#lib.locale.codecvt"> [lib.locale.codecvt]</a>, and also in 22.2.1.6 <a href="lib-locales.html#lib.locale.codecvt.byname"> [lib.locale.codecvt.byname]</a>, +<p>In 22.2.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt"> [lib.locale.codecvt]</a>, and also in 22.2.1.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.byname"> [lib.locale.codecvt.byname]</a>, change the <tt>stateT</tt> argument type on both member <tt>length()</tt> and member <tt>do_length()</tt> from </p> @@ -2229,7 +2240,7 @@ change the <tt>stateT</tt> argument type on both member <p><tt>stateT&</tt></p> </blockquote> -<p>In 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, add to the definition for member +<p>In 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, add to the definition for member <tt>do_length</tt> a paragraph:</p> <blockquote> @@ -2240,7 +2251,7 @@ change the <tt>stateT</tt> argument type on both member </blockquote> <hr> <a name="76"><h3>76. Can a <tt>codecvt</tt> facet always convert one internal character at a time?</h3></a><p> -<b>Section:</b> 22.2.1.5 <a href="lib-locales.html#lib.locale.codecvt"> [lib.locale.codecvt]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 25 Sep 1998</p> +<b>Section:</b> 22.2.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt"> [lib.locale.codecvt]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 25 Sep 1998</p> <p>This issue concerns the requirements on classes derived from <tt>codecvt</tt>, including user-defined classes. What are the restrictions on the conversion from external characters @@ -2268,15 +2279,15 @@ that the corresponding sequence of internal characters is the single character <tt>*ifirst</tt>? </p> -<p>(What a "no" answer would mean is that +<p>(What a "no" answer would mean is that <tt>my_encoding</tt> translates sequences only as blocks. There's a sequence of <i>M</i> external characters that maps to a sequence of <i>N</i> internal characters, but that external sequence has no subsequence that maps to <i>N-1</i> internal characters.) </p> <p>Some of the wording in the standard, such as the description of -<tt>codecvt::do_max_length</tt> (22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, -paragraph 11) and <tt>basic_filebuf::underflow</tt> (27.8.1.4 <a href="lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a>, paragraph 3) suggests that it must always be +<tt>codecvt::do_max_length</tt> (22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a>, +paragraph 11) and <tt>basic_filebuf::underflow</tt> (27.8.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a>, paragraph 3) suggests that it must always be possible to pick off internal characters one at a time from a sequence of external characters. However, this is never explicitly stated one way or the other. </p> @@ -2289,25 +2300,21 @@ be aware of the assumptions that the library makes. This issue affects positioning operations on <tt>basic_filebuf</tt>, unbuffered input, and several of <tt>codecvt</tt>'s member functions. </p> <p><b>Proposed resolution:</b></p> -<p>Add the following text as a new paragraph, following 22.2.1.5.2 <a href="lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> paragraph 2:</p> +<p>Add the following text as a new paragraph, following 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> paragraph 2:</p> <blockquote> <p>A <tt>codecvt</tt> facet that is used by <tt>basic_filebuf</tt> -(27.8 <a href="lib-iostreams.html#lib.file.streams"> [lib.file.streams]</a>) must have the property that if</p> -<pre> - do_out(state, from, from_end, from_next, to, to_lim, to_next) +(27.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.file.streams"> [lib.file.streams]</a>) must have the property that if</p> +<pre> do_out(state, from, from_end, from_next, to, to_lim, to_next) </pre> would return <tt>ok</tt>, where <tt>from != from_end</tt>, then -<pre> - do_out(state, from, from + 1, from_next, to, to_end, to_next) +<pre> do_out(state, from, from + 1, from_next, to, to_end, to_next) </pre> must also return <tt>ok</tt>, and that if -<pre> - do_in(state, from, from_end, from_next, to, to_lim, to_next) +<pre> do_in(state, from, from_end, from_next, to, to_lim, to_next) </pre> would return <tt>ok</tt>, where <tt>to != to_lim</tt>, then -<pre> - do_in(state, from, from_end, from_next, to, to + 1, to_next) +<pre> do_in(state, from, from_end, from_next, to, to + 1, to_next) </pre> <p>must also return <tt>ok</tt>. [<i>Footnote:</i> Informally, this means that <tt>basic_filebuf</tt> assumes that the mapping from @@ -2317,9 +2324,9 @@ one internal character at a time. <i>--End Footnote</i>]</p> </blockquote> <p><i>[Redmond: Minor change in proposed resolution. Original -proposed resolution talked about "success", with a parenthetical +proposed resolution talked about "success", with a parenthetical comment that success meant returning <tt>ok</tt>. New wording -removes all talk about "success", and just talks about the +removes all talk about "success", and just talks about the return value.]</i></p> <p><b>Rationale:</b></p> @@ -2353,37 +2360,37 @@ return value.]</i></p> </p> <hr> <a name="78"><h3>78. Typo: event_call_back</h3></a><p> -<b>Section:</b> 27.4.2 <a href="lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> +<b>Section:</b> 27.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> <p>typo: event_call_back should be event_callback </p> <p><b>Proposed resolution:</b></p> -<p>In the 27.4.2 <a href="lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> synopsis change -"event_call_back" to "event_callback". </p> +<p>In the 27.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> synopsis change +"event_call_back" to "event_callback". </p> <hr> <a name="79"><h3>79. Inconsistent declaration of polar()</h3></a><p> -<b>Section:</b> 26.2.1 <a href="lib-numerics.html#lib.complex.synopsis"> [lib.complex.synopsis]</a>, 26.2.7 <a href="lib-numerics.html#lib.complex.value.ops"> [lib.complex.value.ops]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> -<p>In 26.2.1 <a href="lib-numerics.html#lib.complex.synopsis"> [lib.complex.synopsis]</a> polar is declared as follows:</p> +<b>Section:</b> 26.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.synopsis"> [lib.complex.synopsis]</a>, 26.2.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.value.ops"> [lib.complex.value.ops]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> +<p>In 26.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.synopsis"> [lib.complex.synopsis]</a> polar is declared as follows:</p> <pre> template<class T> complex<T> polar(const T&, const T&); </pre> -<p>In 26.2.7 <a href="lib-numerics.html#lib.complex.value.ops"> [lib.complex.value.ops]</a> it is declared as follows:</p> +<p>In 26.2.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.value.ops"> [lib.complex.value.ops]</a> it is declared as follows:</p> <pre> template<class T> complex<T> polar(const T& rho, const T& theta = 0); </pre> <p>Thus whether the second parameter is optional is not clear. </p> <p><b>Proposed resolution:</b></p> -<p>In 26.2.1 <a href="lib-numerics.html#lib.complex.synopsis"> [lib.complex.synopsis]</a> change:</p> +<p>In 26.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.synopsis"> [lib.complex.synopsis]</a> change:</p> <pre> template<class T> complex<T> polar(const T&, const T&);</pre> <p>to:</p> <pre> template<class T> complex<T> polar(const T& rho, const T& theta = 0); </pre> <hr> <a name="80"><h3>80. Global Operators of complex declared twice</h3></a><p> -<b>Section:</b> 26.2.1 <a href="lib-numerics.html#lib.complex.synopsis"> [lib.complex.synopsis]</a>, 26.2.2 <a href="lib-numerics.html#lib.complex"> [lib.complex]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> +<b>Section:</b> 26.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.synopsis"> [lib.complex.synopsis]</a>, 26.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex"> [lib.complex]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> <p>Both 26.2.1 and 26.2.2 contain declarations of global operators for class complex. This redundancy should be removed.</p> <p><b>Proposed resolution:</b></p> <p>Reduce redundancy according to the general style of the standard. </p> <hr> <a name="83"><h3>83. String::npos vs. string::max_size()</h3></a><p> -<b>Section:</b> 21.3 <a href="lib-strings.html#lib.basic.string"> [lib.basic.string]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> +<b>Section:</b> 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> <p>Many string member functions throw if size is getting or exceeding npos. However, I wonder why they don't throw if size is getting or exceeding max_size() instead of npos. May be npos is known at compile @@ -2391,8 +2398,8 @@ time, while max_size() is known at runtime. However, what happens if size exceeds max_size() but not npos, then? It seems the standard lacks some clarifications here.</p> <p><b>Proposed resolution:</b></p> -<p>After 21.3 <a href="lib-strings.html#lib.basic.string"> [lib.basic.string]</a> paragraph 4 ("The functions -described in this clause...") add a new paragraph:</p> +<p>After 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a> paragraph 4 ("The functions +described in this clause...") add a new paragraph:</p> <blockquote> <p>For any string operation, if as a result of the operation, <tt> size()</tt> would exceed @@ -2403,7 +2410,7 @@ described in this clause...") add a new paragraph:</p> <p>The LWG believes length_error is the correct exception to throw.</p> <hr> <a name="86"><h3>86. String constructors don't describe exceptions</h3></a><p> -<b>Section:</b> 21.3.1 <a href="lib-strings.html#lib.string.cons"> [lib.string.cons]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> +<b>Section:</b> 21.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.cons"> [lib.string.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> <p>The constructor from a range:</p> <pre>template<class InputIterator> @@ -2414,16 +2421,16 @@ described in this clause...") add a new paragraph:</p> according to the other constructors if the numbers of characters in the range equals npos (or exceeds max_size(), see above). </p> <p><b>Proposed resolution:</b></p> -<p>In 21.3.1 <a href="lib-strings.html#lib.string.cons"> [lib.string.cons]</a>, Strike throws paragraphs for -constructors which say "Throws: length_error if n == -npos."</p> +<p>In 21.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.cons"> [lib.string.cons]</a>, Strike throws paragraphs for +constructors which say "Throws: length_error if n == +npos."</p> <p><b>Rationale:</b></p> <p>Throws clauses for length_error if n == npos are no longer needed because they are subsumed by the general wording added by the -resolution for issue <a href="lwg-defects.html#83">83</a>.</p> +resolution for issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#83">83</a>.</p> <hr> <a name="90"><h3>90. Incorrect description of operator >> for strings</h3></a><p> -<b>Section:</b> 21.3.7.9 <a href="lib-strings.html#lib.string.io"> [lib.string.io]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> +<b>Section:</b> 21.3.7.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.io"> [lib.string.io]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> <p>The effect of operator >> for strings contain the following item:</p> <p> <tt>isspace(c,getloc())</tt> is true for the next available input @@ -2431,7 +2438,7 @@ character c.</p> <p>Here <tt>getloc()</tt> has to be replaced by <tt>is.getloc()</tt>. </p> <p><b>Proposed resolution:</b></p> -<p>In 21.3.7.9 <a href="lib-strings.html#lib.string.io"> [lib.string.io]</a> paragraph 1 Effects clause replace:</p> +<p>In 21.3.7.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.io"> [lib.string.io]</a> paragraph 1 Effects clause replace:</p> <blockquote> <p> @@ -2445,8 +2452,70 @@ character c.</p> <tt>isspace(c,is.getloc())</tt> is true for the next available input character c.</p> </blockquote> <hr> -<a name="103"><h3>103. set::iterator is required to be modifiable, but this allows modification of keys</h3></a><p> -<b>Section:</b> 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> AFNOR <b>Date:</b> 7 Oct 1998</p> +<a name="91"><h3>91. Description of operator>> and getline() for string<> might cause endless loop</h3></a><p> +<b>Section:</b> 21.3.7.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.io"> [lib.string.io]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 29 Sep 1998</p> +<p>Operator >> and getline() for strings read until eof() +in the input stream is true. However, this might never happen, if the +stream can't read anymore without reaching EOF. So shouldn't it be +changed into that it reads until !good() ? </p> +<p><b>Proposed resolution:</b></p> +<p>In 21.3.7.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.io"> [lib.string.io]</a>, paragraph 1, replace:</p> +<blockquote> +Effects: Begins by constructing a sentry object k as if k were +constructed by typename basic_istream<charT,traits>::sentry k( is). If +bool( k) is true, it calls str.erase() and then extracts characters +from is and appends them to str as if by calling str.append(1, c). If +is.width() is greater than zero, the maximum number n of characters +appended is is.width(); otherwise n is str.max_size(). Characters are +extracted and appended until any of the following occurs: +</blockquote> +<p>with:</p> +<blockquote> +Effects: Behaves as a formatted input function (27.6.1.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted.reqmts"> [lib.istream.formatted.reqmts]</a>). After constructing a sentry object, if the +sentry converts to true, calls str.erase() and then extracts +characters from is and appends them to str as if by calling +str.append(1,c). If is.width() is greater than zero, the maximum +number n of characters appended is is.width(); otherwise n is +str.max_size(). Characters are extracted and appended until any of the +following occurs: +</blockquote> + +<p>In 21.3.7.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.io"> [lib.string.io]</a>, paragraph 6, replace</p> +<blockquote> +Effects: Begins by constructing a sentry object k as if by typename +basic_istream<charT,traits>::sentry k( is, true). If bool( k) is true, +it calls str.erase() and then extracts characters from is and appends +them to str as if by calling str.append(1, c) until any of the +following occurs: +</blockquote> +<p>with:</p> +<blockquote> +Effects: Behaves as an unformatted input function (27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>), except that it does not affect the value returned +by subsequent calls to basic_istream<>::gcount(). After +constructing a sentry object, if the sentry converts to true, calls +str.erase() and then extracts characters from is and appends them to +str as if by calling str.append(1,c) until any of the following +occurs: +</blockquote> + +<p><i>[Redmond: Made changes in proposed resolution. <tt>operator>></tt> +should be a formatted input function, not an unformatted input function. +<tt>getline</tt> should not be required to set <tt>gcount</tt>, since +there is no mechanism for <tt>gcount</tt> to be set except by one of +<tt>basic_istream</tt>'s member functions.]</i></p> + +<p><i>[Curaçao: Nico agrees with proposed resolution.]</i></p> + +<p><b>Rationale:</b></p> +<p>The real issue here is whether or not these string input functions +get their characters from a streambuf, rather than by calling an +istream's member functions, a streambuf signals failure either by +returning eof or by throwing an exception; there are no other +possibilities. The proposed resolution makes it clear that these two +functions do get characters from a streambuf.</p> +<hr> +<a name="103"></a><h3><a name="103">103. set::iterator is required to be modifiable, but this allows modification of keys</a></h3><p> +<b>Section:</b> 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> AFNOR <b>Date:</b> 7 Oct 1998</p> <p>Set::iterator is described as implementation-defined with a reference to the container requirement; the container requirement says that const_iterator is an iterator pointing to const T and iterator an @@ -2461,7 +2530,7 @@ const_iterator. Set, for example, has the following: </p> <p><tt>typedef implementation defined iterator;<br> // See _lib.container.requirements_</tt></p> -<p>23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> actually requires that iterator type pointing +<p>23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> actually requires that iterator type pointing to T (table 65). Disallowing user modification of keys by changing the standard to require an iterator for associative container to be the same as const_iterator would be overkill since that will unnecessarily @@ -2475,27 +2544,27 @@ goes in line with trusting user knows what he is doing. </p> <p> <b>Other Options Evaluated:</b> </p> -<p>Option A. In 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a>, paragraph 2, after -first sentence, and before "In addition,...", add one line: +<p>Option A. In 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a>, paragraph 2, after +first sentence, and before "In addition,...", add one line: </p> <blockquote> <p>Modification of keys shall not change their strict weak ordering. </p> </blockquote> -<p>Option B. Add three new sentences to 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a>:</p> +<p>Option B. Add three new sentences to 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a>:</p> <blockquote> - <p>At the end of paragraph 5: "Keys in an associative container - are immutable." At the end of paragraph 6: "For + <p>At the end of paragraph 5: "Keys in an associative container + are immutable." At the end of paragraph 6: "For associative containers where the value type is the same as the key type, both <tt>iterator</tt> and <tt>const_iterator</tt> are constant iterators. It is unspecified whether or not <tt>iterator</tt> and <tt>const_iterator</tt> are the same - type."</p> + type."</p> </blockquote> -<p>Option C. To 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a>, paragraph 3, which +<p>Option C. To 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a>, paragraph 3, which currently reads:</p> <blockquote> @@ -2518,18 +2587,18 @@ currently reads:</p> different than it was the previous time k2 was in the container.]</p> </blockquote> <p><b>Proposed resolution:</b></p> -<p>Add the following to 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> at +<p>Add the following to 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> at the indicated location:</p> <blockquote> - <p>At the end of paragraph 3: "For any two keys k1 and k2 in the same container, + <p>At the end of paragraph 3: "For any two keys k1 and k2 in the same container, calling comp(k1, k2) shall always return the same - value."</p> - <p>At the end of paragraph 5: "Keys in an associative container are immutable."</p> - <p>At the end of paragraph 6: "For associative containers where the value type is the + value."</p> + <p>At the end of paragraph 5: "Keys in an associative container are immutable."</p> + <p>At the end of paragraph 6: "For associative containers where the value type is the same as the key type, both <tt>iterator</tt> and <tt>const_iterator</tt> are constant iterators. It is unspecified whether or not <tt>iterator</tt> and <tt>const_iterator</tt> - are the same type."</p> + are the same type."</p> </blockquote> <p><b>Rationale:</b></p> <p>Several arguments were advanced for and against allowing set elements to be @@ -2557,33 +2626,33 @@ conversion from <tt>iterator</tt> to <tt>const_iterator</tt>. <p><i>[Tokyo: The LWG crafted the proposed resolution and rationale.]</i></p> <hr> <a name="106"><h3>106. Numeric library private members are implementation defined</h3></a><p> -<b>Section:</b> 26.3.5 <a href="lib-numerics.html#lib.template.slice.array"> [lib.template.slice.array]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> AFNOR <b>Date:</b> 7 Oct 1998</p> +<b>Section:</b> 26.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.slice.array"> [lib.template.slice.array]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> AFNOR <b>Date:</b> 7 Oct 1998</p> <p>This is the only place in the whole standard where the implementation has to document something private.</p> <p><b>Proposed resolution:</b></p> <p> -Remove the comment which says "// remainder implementation defined" from: +Remove the comment which says "// remainder implementation defined" from: </p> <ul> - <li>26.3.5 <a href="lib-numerics.html#lib.template.slice.array"> [lib.template.slice.array]</a> + <li>26.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.slice.array"> [lib.template.slice.array]</a> </li> - <li>26.3.7 <a href="lib-numerics.html#lib.template.gslice.array"> [lib.template.gslice.array]</a> + <li>26.3.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.gslice.array"> [lib.template.gslice.array]</a> </li> - <li>26.3.8 <a href="lib-numerics.html#lib.template.mask.array"> [lib.template.mask.array]</a> + <li>26.3.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.mask.array"> [lib.template.mask.array]</a> </li> - <li>26.3.9 <a href="lib-numerics.html#lib.template.indirect.array"> [lib.template.indirect.array]</a> + <li>26.3.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.indirect.array"> [lib.template.indirect.array]</a> </li> </ul> <hr> <a name="108"><h3>108. Lifetime of exception::what() return unspecified</h3></a><p> -<b>Section:</b> 18.6.1 <a href="lib-support.html#lib.exception"> [lib.exception]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> AFNOR <b>Date:</b> 7 Oct 1998</p> +<b>Section:</b> 18.6.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.exception"> [lib.exception]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> AFNOR <b>Date:</b> 7 Oct 1998</p> <p>In 18.6.1, paragraphs 8-9, the lifetime of the return value of exception::what() is left unspecified. This issue has implications with exception safety of exception handling: some exceptions should not throw bad_alloc.</p> <p><b>Proposed resolution:</b></p> -<p>Add to 18.6.1 <a href="lib-support.html#lib.exception"> [lib.exception]</a> paragraph 9 (exception::what notes +<p>Add to 18.6.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.exception"> [lib.exception]</a> paragraph 9 (exception::what notes clause) the sentence:</p> <blockquote> @@ -2596,12 +2665,12 @@ to set internal state that should affect the contents of the string returned by <tt>what()</tt>. </p> <hr> -<a name="109"><h3>109. Missing binders for non-const sequence elements</h3></a><p> -<b>Section:</b> 20.3.6 <a href="lib-utilities.html#lib.binders"> [lib.binders]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Bjarne Stroustrup <b>Date:</b> 7 Oct 1998</p> +<a name="109"></a><h3><a name="109">109. Missing binders for non-const sequence elements</a></h3><p> +<b>Section:</b> 20.3.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.binders"> [lib.binders]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Bjarne Stroustrup <b>Date:</b> 7 Oct 1998</p> <p>There are no versions of binders that apply to non-const elements of a sequence. This makes examples like for_each() using bind2nd() on -page 521 of "The C++ Programming Language (3rd)" +page 521 of "The C++ Programming Language (3rd)" non-conforming. Suitable versions of the binders need to be added.</p> <p>Further discussion from Nico:</p> @@ -2673,7 +2742,7 @@ public: <b>Howard believes there is a flaw</b> in this resolution. See c++std-lib-9127. We may need to reopen this issue.</p> -<p>In 20.3.6.1 <a href="lib-utilities.html#lib.binder.1st"> [lib.binder.1st]</a> in the declaration of binder1st after:</p> +<p>In 20.3.6.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.binder.1st"> [lib.binder.1st]</a> in the declaration of binder1st after:</p> <blockquote> <p><tt>typename Operation::result_type<br> operator()(const typename Operation::second_argument_type& x) const;</tt></p> @@ -2683,7 +2752,7 @@ See c++std-lib-9127. We may need to reopen this issue.</p> <p><tt>typename Operation::result_type<br> operator()(typename Operation::second_argument_type& x) const;</tt></p> </blockquote> -<p>In 20.3.6.3 <a href="lib-utilities.html#lib.binder.2nd"> [lib.binder.2nd]</a> in the declaration of binder2nd after:</p> +<p>In 20.3.6.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.binder.2nd"> [lib.binder.2nd]</a> in the declaration of binder2nd after:</p> <blockquote> <p><tt>typename Operation::result_type<br> operator()(const typename Operation::first_argument_type& x) const;</tt></p> @@ -2705,12 +2774,12 @@ Leave open - 1.]</i></p> <hr> <a name="110"><h3>110. istreambuf_iterator::equal not const</h3></a><p> -<b>Section:</b> 24.5.3 <a href="lib-iterators.html#lib.istreambuf.iterator"> [lib.istreambuf.iterator]</a>, 24.5.3.5 <a href="lib-iterators.html#lib.istreambuf.iterator::equal"> [lib.istreambuf.iterator::equal]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 15 Oct 1998</p> +<b>Section:</b> 24.5.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.istreambuf.iterator"> [lib.istreambuf.iterator]</a>, 24.5.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.istreambuf.iterator::equal"> [lib.istreambuf.iterator::equal]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nathan Myers <b>Date:</b> 15 Oct 1998</p> <p>Member istreambuf_iterator<>::equal is not declared -"const", yet 24.5.3.6 <a href="lib-iterators.html#lib.istreambuf.iterator::op=="> [lib.istreambuf.iterator::op==]</a> says that operator==, +"const", yet 24.5.3.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.istreambuf.iterator::op=="> [lib.istreambuf.iterator::op==]</a> says that operator==, which is const, calls it. This is contradictory. </p> <p><b>Proposed resolution:</b></p> -<p>In 24.5.3 <a href="lib-iterators.html#lib.istreambuf.iterator"> [lib.istreambuf.iterator]</a> and also in 24.5.3.5 <a href="lib-iterators.html#lib.istreambuf.iterator::equal"> [lib.istreambuf.iterator::equal]</a>, +<p>In 24.5.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.istreambuf.iterator"> [lib.istreambuf.iterator]</a> and also in 24.5.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.istreambuf.iterator::equal"> [lib.istreambuf.iterator::equal]</a>, replace:</p> <blockquote> @@ -2724,16 +2793,16 @@ replace:</p> </blockquote> <hr> <a name="112"><h3>112. Minor typo in <tt>ostreambuf_iterator</tt> constructor</h3></a><p> -<b>Section:</b> 24.5.4.1 <a href="lib-iterators.html#lib.ostreambuf.iter.cons"> [lib.ostreambuf.iter.cons]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 20 Oct 1998</p> +<b>Section:</b> 24.5.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.ostreambuf.iter.cons"> [lib.ostreambuf.iter.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 20 Oct 1998</p> <p>The <b>requires</b> clause for <tt>ostreambuf_iterator</tt>'s constructor from an <tt>ostream_type</tt> (24.5.4.1, paragraph 1) -reads "<i>s</i> is not null". However, <i>s</i> is a +reads "<i>s</i> is not null". However, <i>s</i> is a reference, and references can't be null. </p> <p><b>Proposed resolution:</b></p> -<p>In 24.5.4.1 <a href="lib-iterators.html#lib.ostreambuf.iter.cons"> [lib.ostreambuf.iter.cons]</a>:</p> +<p>In 24.5.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.ostreambuf.iter.cons"> [lib.ostreambuf.iter.cons]</a>:</p> -<p>Move the current paragraph 1, which reads "Requires: s is not -null.", from the first constructor to the second constructor.</p> +<p>Move the current paragraph 1, which reads "Requires: s is not +null.", from the first constructor to the second constructor.</p> <p>Insert a new paragraph 1 Requires clause for the first constructor reading:</p> @@ -2744,7 +2813,7 @@ reading:</p> </blockquote> <hr> <a name="114"><h3>114. Placement forms example in error twice</h3></a><p> -<b>Section:</b> 18.4.1.3 <a href="lib-support.html#lib.new.delete.placement"> [lib.new.delete.placement]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 28 Oct 1998</p> +<b>Section:</b> 18.4.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete.placement"> [lib.new.delete.placement]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 28 Oct 1998</p> <p>Section 18.4.1.3 contains the following example: </p> <pre>[Example: This can be useful for constructing an object at a known address: @@ -2752,7 +2821,7 @@ reading:</p> Something* p = new (place) Something(); -end example]</pre> -<p>First code line: "place" need not have any special alignment, and the +<p>First code line: "place" need not have any special alignment, and the following constructor could fail due to misaligned data.</p> <p>Second code line: Aren't the parens on Something() incorrect? [Dublin: the LWG @@ -2762,7 +2831,7 @@ believes the () are correct.]</p> likely to fail.</p> <p><b>Proposed resolution:</b></p> <p>Replace the <u> first line of code</u> in the example in -18.4.1.3 <a href="lib-support.html#lib.new.delete.placement"> [lib.new.delete.placement]</a> with: +18.4.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete.placement"> [lib.new.delete.placement]</a> with: </p> <blockquote> @@ -2770,7 +2839,7 @@ likely to fail.</p> </blockquote> <hr> <a name="115"><h3>115. Typo in strstream constructors</h3></a><p> -<b>Section:</b> D.7.4.1 <a href="future.html#depr.strstream.cons"> [depr.strstream.cons]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 2 Nov 1998</p> +<b>Section:</b> D.7.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.strstream.cons"> [depr.strstream.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 2 Nov 1998</p> <p>D.7.4.1 strstream constructors paragraph 2 says: </p> <blockquote> @@ -2784,15 +2853,15 @@ likely to fail.</p> </blockquote> <p>Notice the second condition is the same as the first. I think the second condition -should be "If mode&app==app", or "mode&app!=0", meaning that +should be "If mode&app==app", or "mode&app!=0", meaning that the append bit is set.</p> <p><b>Proposed resolution:</b></p> -<p>In D.7.3.1 <a href="future.html#depr.ostrstream.cons"> [depr.ostrstream.cons]</a> paragraph 2 and D.7.4.1 <a href="future.html#depr.strstream.cons"> [depr.strstream.cons]</a> +<p>In D.7.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.ostrstream.cons"> [depr.ostrstream.cons]</a> paragraph 2 and D.7.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.strstream.cons"> [depr.strstream.cons]</a> paragraph 2, change the first condition to <tt>(mode&app)==0</tt> and the second condition to <tt>(mode&app)!=0</tt>.</p> <hr> <a name="117"><h3>117. <tt>basic_ostream</tt> uses nonexistent <tt>num_put</tt> member functions</h3></a><p> -<b>Section:</b> 27.6.2.5.2 <a href="lib-iostreams.html#lib.ostream.inserters.arithmetic"> [lib.ostream.inserters.arithmetic]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 20 Nov 1998</p> +<b>Section:</b> 27.6.2.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.inserters.arithmetic"> [lib.ostream.inserters.arithmetic]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 20 Nov 1998</p> <p>The <b>effects</b> clause for numeric inserters says that insertion of a value <tt>x</tt>, whose type is either <tt>bool</tt>, <tt>short</tt>, <tt>unsigned short</tt>, <tt>int</tt>, <tt>unsigned @@ -2821,7 +2890,7 @@ functions that are actually there. I prefer the latter. </p> <blockquote> <p> -The classes num_get<> and num_put<> handle locale­dependent numeric +The classes num_get<> and num_put<> handle localedependent numeric formatting and parsing. These inserter functions use the imbued locale value to perform numeric formatting. When val is of type bool, long, unsigned long, double, long double, or const void*, the @@ -2829,8 +2898,7 @@ formatting conversion occurs as if it performed the following code fragment: </p> -<pre> -bool failed = use_facet< +<pre>bool failed = use_facet< num_put<charT,ostreambuf_iterator<charT,traits> > >(getloc()).put(*this, *this, fill(), val). failed(); </pre> @@ -2840,8 +2908,7 @@ When val is of type short the formatting conversion occurs as if it performed the following code fragment: </p> -<pre> -ios_base::fmtflags baseflags = ios_base::flags() & ios_base::basefield; +<pre>ios_base::fmtflags baseflags = ios_base::flags() & ios_base::basefield; bool failed = use_facet< num_put<charT,ostreambuf_iterator<charT,traits> > >(getloc()).put(*this, *this, fill(), @@ -2855,8 +2922,7 @@ When val is of type int the formatting conversion occurs as if it performed the following code fragment: </p> -<pre> -ios_base::fmtflags baseflags = ios_base::flags() & ios_base::basefield; +<pre>ios_base::fmtflags baseflags = ios_base::flags() & ios_base::basefield; bool failed = use_facet< num_put<charT,ostreambuf_iterator<charT,traits> > >(getloc()).put(*this, *this, fill(), @@ -2870,8 +2936,7 @@ When val is of type unsigned short or unsigned int the formatting conversion occurs as if it performed the following code fragment: </p> -<pre> -bool failed = use_facet< +<pre>bool failed = use_facet< num_put<charT,ostreambuf_iterator<charT,traits> > >(getloc()).put(*this, *this, fill(), static_cast<unsigned long>(val)). failed(); @@ -2882,8 +2947,7 @@ When val is of type float the formatting conversion occurs as if it performed the following code fragment: </p> -<pre> -bool failed = use_facet< +<pre>bool failed = use_facet< num_put<charT,ostreambuf_iterator<charT,traits> > >(getloc()).put(*this, *this, fill(), static_cast<double>(val)). failed(); @@ -2904,7 +2968,7 @@ of signed short and signed int. (On a system with 16-bit short, for example, printing short(-1) in hex format should yield 0xffff.)</p> <hr> <a name="118"><h3>118. <tt>basic_istream</tt> uses nonexistent <tt>num_get</tt> member functions</h3></a><p> -<b>Section:</b> 27.6.1.2.2 <a href="lib-iostreams.html#lib.istream.formatted.arithmetic"> [lib.istream.formatted.arithmetic]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 20 Nov 1998</p> +<b>Section:</b> 27.6.1.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted.arithmetic"> [lib.istream.formatted.arithmetic]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 20 Nov 1998</p> <p>Formatted input is defined for the types <tt>short</tt>, <tt>unsigned short</tt>, <tt>int</tt>, <tt>unsigned int</tt>, <tt>long</tt>, <tt>unsigned long</tt>, <tt>float</tt>, <tt>double</tt>, <tt>long double</tt>, <tt>bool</tt>, and <tt>void*</tt>. According to section 27.6.1.2.2, @@ -2915,7 +2979,7 @@ iostate err = 0; use_facet< numget >(loc).get(*this, 0, *this, err, val); setstate(err);</pre> -<p>According to section 22.2.2.1.1 <a href="lib-locales.html#lib.facet.num.get.members"> [lib.facet.num.get.members]</a>, however, +<p>According to section 22.2.2.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.members"> [lib.facet.num.get.members]</a>, however, <tt>num_get<>::get()</tt> is only overloaded for the types <tt>bool</tt>, <tt>long</tt>, <tt>unsigned short</tt>, <tt>unsigned int</tt>, <tt>unsigned long</tt>, <tt>unsigned long</tt>, @@ -2924,7 +2988,7 @@ int</tt>, <tt>unsigned long</tt>, <tt>unsigned long</tt>, that 27.6.1.2.2 is using a nonexistent function for types <tt>short</tt> and <tt>int</tt>. </p> <p><b>Proposed resolution:</b></p> -<p>In 27.6.1.2.2 <a href="lib-iostreams.html#lib.istream.formatted.arithmetic"> [lib.istream.formatted.arithmetic]</a> Arithmetic Extractors, remove the +<p>In 27.6.1.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted.arithmetic"> [lib.istream.formatted.arithmetic]</a> Arithmetic Extractors, remove the two lines (1st and 3rd) which read:</p> <blockquote> <pre>operator>>(short& val); @@ -2962,11 +3026,11 @@ operator>>(int& val);</pre> <p><i>[Post-Tokyo: PJP provided the above wording.]</i></p> <hr> <a name="119"><h3>119. Should virtual functions be allowed to strengthen the exception specification?</h3></a><p> -<b>Section:</b> 17.4.4.8 <a href="lib-intro.html#lib.res.on.exception.handling"> [lib.res.on.exception.handling]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> -<p>Section 17.4.4.8 <a href="lib-intro.html#lib.res.on.exception.handling"> [lib.res.on.exception.handling]</a> states: </p> +<b>Section:</b> 17.4.4.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.res.on.exception.handling"> [lib.res.on.exception.handling]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> +<p>Section 17.4.4.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.res.on.exception.handling"> [lib.res.on.exception.handling]</a> states: </p> -<p>"An implementation may strengthen the exception-specification -for a function by removing listed exceptions." </p> +<p>"An implementation may strengthen the exception-specification +for a function by removing listed exceptions." </p> <p>The problem is that if an implementation is allowed to do this for virtual functions, then a library user cannot write a class that @@ -2985,18 +3049,18 @@ public: // overridden virtual function ios_base::failure::~failure() };</pre> <p><b>Proposed resolution:</b></p> -<p>Change Section 17.4.4.8 <a href="lib-intro.html#lib.res.on.exception.handling"> [lib.res.on.exception.handling]</a> from:</p> +<p>Change Section 17.4.4.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.res.on.exception.handling"> [lib.res.on.exception.handling]</a> from:</p> -<p> "may strengthen the -exception-specification for a function"</p> +<p> "may strengthen the +exception-specification for a function"</p> <p>to:</p> -<p> "may strengthen the -exception-specification for a non-virtual function". </p> +<p> "may strengthen the +exception-specification for a non-virtual function". </p> <hr> <a name="122"><h3>122. streambuf/wstreambuf description should not say they are specializations</h3></a><p> -<b>Section:</b> 27.5.2 <a href="lib-iostreams.html#lib.streambuf"> [lib.streambuf]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> +<b>Section:</b> 27.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf"> [lib.streambuf]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> <p>Section 27.5.2 describes the streambuf classes this way: </p> <blockquote> @@ -3013,37 +3077,154 @@ specialized for the type wchar_t. </p> <p>It doesn't seem this was intended, since Section 27.5 has them declared as typedefs. </p> <p><b>Proposed resolution:</b></p> -<p>Remove 27.5.2 <a href="lib-iostreams.html#lib.streambuf"> [lib.streambuf]</a> paragraphs 2 and 3 (the above two +<p>Remove 27.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf"> [lib.streambuf]</a> paragraphs 2 and 3 (the above two sentences). </p> <p><b>Rationale:</b></p> <p>The <tt>streambuf</tt> synopsis already has a declaration for the typedefs and that is sufficient. </p> <hr> +<a name="123"><h3>123. Should valarray helper arrays fill functions be const?</h3></a><p> +<b>Section:</b> 26.3.5.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.slice.arr.fill"> [lib.slice.arr.fill]</a>, 26.3.7.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.gslice.array.fill"> [lib.gslice.array.fill]</a>, 26.3.8.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.mask.array.fill"> [lib.mask.array.fill]</a>, 26.3.9.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.indirect.array.fill"> [lib.indirect.array.fill]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998 </p> +<p>One of the operator= in the valarray helper arrays is const and one +is not. For example, look at slice_array. This operator= in Section +26.3.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.slice.arr.assign"> [lib.slice.arr.assign]</a> is const: </p> + +<p> <tt>void operator=(const valarray<T>&) const;</tt> </p> + +<p>but this one in Section 26.3.5.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.slice.arr.fill"> [lib.slice.arr.fill]</a> is not: </p> + +<p> <tt>void operator=(const T&); </tt> +</p> + +<p>The description of the semantics for these two functions is similar. </p> +<p><b>Proposed resolution:</b></p> + +<p>26.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.slice.array"> [lib.template.slice.array]</a> Template class slice_array</p> +<blockquote> + + <p>In the class template definition for slice_array, replace the member + function declaration</p> + <pre> void operator=(const T&); + </pre> + <p>with</p> + <pre> void operator=(const T&) const; + </pre> +</blockquote> + +<p>26.3.5.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.slice.arr.fill"> [lib.slice.arr.fill]</a> slice_array fill function</p> +<blockquote> + + <p>Change the function declaration</p> + <pre> void operator=(const T&); + </pre> + <p>to</p> + <pre> void operator=(const T&) const; + </pre> +</blockquote> + +<p>26.3.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.gslice.array"> [lib.template.gslice.array]</a> Template class gslice_array</p> +<blockquote> + + <p>In the class template definition for gslice_array, replace the member + function declaration</p> + <pre> void operator=(const T&); + </pre> + <p>with</p> + <pre> void operator=(const T&) const; + </pre> +</blockquote> + +<p>26.3.7.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.gslice.array.fill"> [lib.gslice.array.fill]</a> gslice_array fill function</p> +<blockquote> + + <p>Change the function declaration</p> + <pre> void operator=(const T&); + </pre> + <p>to</p> + <pre> void operator=(const T&) const; + </pre> +</blockquote> + +<p>26.3.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.mask.array"> [lib.template.mask.array]</a> Template class mask_array</p> +<blockquote> + + <p>In the class template definition for mask_array, replace the member + function declaration</p> + <pre> void operator=(const T&); + </pre> + <p>with</p> + <pre> void operator=(const T&) const; + </pre> +</blockquote> + +<p>26.3.8.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.mask.array.fill"> [lib.mask.array.fill]</a> mask_array fill function</p> +<blockquote> + + <p>Change the function declaration</p> + <pre> void operator=(const T&); + </pre> + <p>to</p> + <pre> void operator=(const T&) const; + </pre> +</blockquote> + +<p>26.3.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.indirect.array"> [lib.template.indirect.array]</a> Template class indirect_array</p> +<blockquote> + + <p>In the class template definition for indirect_array, replace the member + function declaration</p> + <pre> void operator=(const T&); + </pre> + <p>with</p> + <pre> void operator=(const T&) const; + </pre> +</blockquote> + +<p>26.3.9.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.indirect.array.fill"> [lib.indirect.array.fill]</a> indirect_array fill function</p> +<blockquote> + + <p>Change the function declaration</p> + <pre> void operator=(const T&); + </pre> + <p>to</p> + <pre> void operator=(const T&) const; + </pre> +</blockquote> + + +<p><i>[Redmond: Robert provided wording.]</i></p> + +<p><b>Rationale:</b></p> +<p>There's no good reason for one version of operator= being const and +another one not. Because of issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#253">253</a>, this now +matters: these functions are now callable in more circumstances. In +many existing implementations, both versions are already const.</p> +<hr> <a name="124"><h3>124. ctype_byname<charT>::do_scan_is & do_scan_not return type should be const charT*</h3></a><p> -<b>Section:</b> 22.2.1.2 <a href="lib-locales.html#lib.locale.ctype.byname"> [lib.locale.ctype.byname]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> -<p>In Section 22.2.1.2 <a href="lib-locales.html#lib.locale.ctype.byname"> [lib.locale.ctype.byname]</a> +<b>Section:</b> 22.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.byname"> [lib.locale.ctype.byname]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> +<p>In Section 22.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.byname"> [lib.locale.ctype.byname]</a> ctype_byname<charT>::do_scan_is() and do_scan_not() are declared to return a const char* not a const charT*. </p> <p><b>Proposed resolution:</b></p> -<p>Change Section 22.2.1.2 <a href="lib-locales.html#lib.locale.ctype.byname"> [lib.locale.ctype.byname]</a> <tt>do_scan_is()</tt> and +<p>Change Section 22.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.byname"> [lib.locale.ctype.byname]</a> <tt>do_scan_is()</tt> and <tt>do_scan_not()</tt> to return a <tt> const charT*</tt>. </p> <hr> <a name="125"><h3>125. valarray<T>::operator!() return type is inconsistent</h3></a><p> -<b>Section:</b> 26.3.2 <a href="lib-numerics.html#lib.template.valarray"> [lib.template.valarray]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> -<p>In Section 26.3.2 <a href="lib-numerics.html#lib.template.valarray"> [lib.template.valarray]</a> valarray<T>::operator!() is -declared to return a valarray<T>, but in Section 26.3.2.5 <a href="lib-numerics.html#lib.valarray.unary"> [lib.valarray.unary]</a> it is declared to return a valarray<bool>. The +<b>Section:</b> 26.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.valarray"> [lib.template.valarray]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> +<p>In Section 26.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.valarray"> [lib.template.valarray]</a> valarray<T>::operator!() is +declared to return a valarray<T>, but in Section 26.3.2.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.valarray.unary"> [lib.valarray.unary]</a> it is declared to return a valarray<bool>. The latter appears to be correct. </p> <p><b>Proposed resolution:</b></p> -<p>Change in Section 26.3.2 <a href="lib-numerics.html#lib.template.valarray"> [lib.template.valarray]</a> the declaration of +<p>Change in Section 26.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.template.valarray"> [lib.template.valarray]</a> the declaration of <tt>operator!()</tt> so that the return type is <tt>valarray<bool></tt>. </p> <hr> -<a name="126"><h3>126. typos in Effects clause of ctype::do_narrow()</h3></a><p> -<b>Section:</b> 22.2.1.1.2 <a href="lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> +<a name="126"></a><h3><a name="126">126. typos in Effects clause of ctype::do_narrow()</a></h3><p> +<b>Section:</b> 22.2.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 15 Dec 1998</p> <p>Typos in 22.2.1.1.2 need to be fixed.</p> <p><b>Proposed resolution:</b></p> -<p>In Section 22.2.1.1.2 <a href="lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a> change: </p> +<p>In Section 22.2.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a> change: </p> <pre> do_widen(do_narrow(c),0) == c</pre> @@ -3060,7 +3241,7 @@ latter appears to be correct. </p> <pre> (is(M,c) || !ctc.is(M, do_narrow(c,dfault)) )</pre> <hr> <a name="127"><h3>127. auto_ptr<> conversion issues</h3></a><p> -<b>Section:</b> 20.4.5 <a href="lib-utilities.html#lib.auto.ptr"> [lib.auto.ptr]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Greg Colvin <b>Date:</b> 17 Feb 1999</p> +<b>Section:</b> 20.4.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.auto.ptr"> [lib.auto.ptr]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Greg Colvin <b>Date:</b> 17 Feb 1999</p> <p>There are two problems with the current <tt>auto_ptr</tt> wording in the standard: </p> @@ -3080,8 +3261,8 @@ of the standard. </p> <p>25 Aug 1999: The proposed resolution now reflects changes suggested by Dave Abrahams, with Greg Colvin's concurrence; 1) changed -"assignment operator" to "public assignment -operator", 2) changed effects to specify use of release(), 3) +"assignment operator" to "public assignment +operator", 2) changed effects to specify use of release(), 3) made the conversion to auto_ptr_ref const. </p> <p>2 Feb 2000: Lisa Lippincott comments: [The resolution of] this issue @@ -3098,23 +3279,23 @@ object parameter may be bound to an rvalue [13.3.3.1.4/3] <p>Tokyo: The LWG removed the following from the proposed resolution:</p> - <p>In 20.4.5 <a href="lib-utilities.html#lib.auto.ptr"> [lib.auto.ptr]</a>, paragraph 2, and 20.4.5.3 <a href="lib-utilities.html#lib.auto.ptr.conv"> [lib.auto.ptr.conv]</a>, + <p>In 20.4.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.auto.ptr"> [lib.auto.ptr]</a>, paragraph 2, and 20.4.5.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.auto.ptr.conv"> [lib.auto.ptr.conv]</a>, paragraph 2, make the conversion to auto_ptr_ref const:</p> <blockquote> <pre>template<class Y> operator auto_ptr_ref<Y>() const throw();</pre> </blockquote> <p><b>Proposed resolution:</b></p> -<p>In 20.4.5 <a href="lib-utilities.html#lib.auto.ptr"> [lib.auto.ptr]</a>, paragraph 2, move +<p>In 20.4.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.auto.ptr"> [lib.auto.ptr]</a>, paragraph 2, move the <tt>auto_ptr_ref</tt> definition to namespace scope.</p> -<p>In 20.4.5 <a href="lib-utilities.html#lib.auto.ptr"> [lib.auto.ptr]</a>, paragraph 2, add +<p>In 20.4.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.auto.ptr"> [lib.auto.ptr]</a>, paragraph 2, add a public assignment operator to the <tt>auto_ptr</tt> definition: </p> <blockquote> <pre>auto_ptr& operator=(auto_ptr_ref<X> r) throw();</pre> </blockquote> -<p>Also add the assignment operator to 20.4.5.3 <a href="lib-utilities.html#lib.auto.ptr.conv"> [lib.auto.ptr.conv]</a>: </p> +<p>Also add the assignment operator to 20.4.5.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.auto.ptr.conv"> [lib.auto.ptr.conv]</a>: </p> <blockquote> <pre>auto_ptr& operator=(auto_ptr_ref<X> r) throw()</pre> @@ -3126,7 +3307,7 @@ a public assignment operator to the <tt>auto_ptr</tt> definition: </p> </blockquote> <hr> <a name="129"><h3>129. Need error indication from seekp() and seekg()</h3></a><p> -<b>Section:</b> 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>, 27.6.2.4 <a href="lib-iostreams.html#lib.ostream.seeks"> [lib.ostream.seeks]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 22 Feb 1999</p> +<b>Section:</b> 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>, 27.6.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.seeks"> [lib.ostream.seeks]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 22 Feb 1999</p> <p>Currently, the standard does not specify how seekg() and seekp() indicate failure. They are not required to set failbit, and they can't return an error indication because they must return *this, i.e. the @@ -3139,8 +3320,8 @@ stream must perform a state-dependent code conversion, etc. </p> stream state in case of failure.</p> <p><b>Proposed resolution:</b></p> <p>Add to the Effects: clause of seekg() in -27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> and to the Effects: clause of seekp() in -27.6.2.4 <a href="lib-iostreams.html#lib.ostream.seeks"> [lib.ostream.seeks]</a>: </p> +27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> and to the Effects: clause of seekp() in +27.6.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.seeks"> [lib.ostream.seeks]</a>: </p> <blockquote> <p>In case of failure, the function calls <tt>setstate(failbit)</tt> (which may throw <tt>ios_base::failure</tt>). @@ -3150,7 +3331,7 @@ stream state in case of failure.</p> <p>Setting failbit is the usual error reporting mechanism for streams</p> <hr> <a name="132"><h3>132. list::resize description uses random access iterators</h3></a><p> -<b>Section:</b> 23.2.2.2 <a href="lib-containers.html#lib.list.capacity"> [lib.list.capacity]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 6 Mar 1999</p> +<b>Section:</b> 23.2.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.capacity"> [lib.list.capacity]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 6 Mar 1999</p> <p>The description reads:</p> <p>-1- Effects:</p> @@ -3182,23 +3363,23 @@ with David Abrahams. They had a discussion and believe there is no issue of exception safety with the proposed resolution.]</i></p> <hr> <a name="133"><h3>133. map missing get_allocator()</h3></a><p> -<b>Section:</b> 23.3.1 <a href="lib-containers.html#lib.map"> [lib.map]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 6 Mar 1999</p> +<b>Section:</b> 23.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.map"> [lib.map]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 6 Mar 1999</p> <p>The title says it all.</p> <p><b>Proposed resolution:</b></p> -<p>Insert in 23.3.1 <a href="lib-containers.html#lib.map"> [lib.map]</a>, paragraph 2, +<p>Insert in 23.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.map"> [lib.map]</a>, paragraph 2, after operator= in the map declaration:</p> <pre> allocator_type get_allocator() const;</pre> <hr> <a name="134"><h3>134. vector constructors over specified</h3></a><p> -<b>Section:</b> 23.2.4.1 <a href="lib-containers.html#lib.vector.cons"> [lib.vector.cons]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 6 Mar 1999</p> -<p>The complexity description says: "It does at most 2N calls to the copy constructor -of T and logN reallocations if they are just input iterators ...".</p> +<b>Section:</b> 23.2.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.cons"> [lib.vector.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 6 Mar 1999</p> +<p>The complexity description says: "It does at most 2N calls to the copy constructor +of T and logN reallocations if they are just input iterators ...".</p> <p>This appears to be overly restrictive, dictating the precise memory/performance tradeoff for the implementor.</p> <p><b>Proposed resolution:</b></p> -<p>Change 23.2.4.1 <a href="lib-containers.html#lib.vector.cons"> [lib.vector.cons]</a>, paragraph 1 to:</p> +<p>Change 23.2.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.cons"> [lib.vector.cons]</a>, paragraph 1 to:</p> <p>-1- Complexity: The constructor template <class InputIterator> vector(InputIterator first, InputIterator last) @@ -3209,12 +3390,12 @@ categories. It makes order N calls to the copy constructor of T and order logN reallocations if they are just input iterators. </p> <p><b>Rationale:</b></p> -<p>"at most 2N calls" is correct only if the growth factor +<p>"at most 2N calls" is correct only if the growth factor is greater than or equal to 2. </p> <hr> <a name="136"><h3>136. seekp, seekg setting wrong streams?</h3></a><p> -<b>Section:</b> 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 6 Mar 1999</p> +<b>Section:</b> 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 6 Mar 1999</p> <p>I may be misunderstanding the intent, but should not seekg set only the input stream and seekp set only the output stream? The description seems to say that each should set both input and output streams. If @@ -3256,7 +3437,7 @@ Effects: If fail() != true, executes rdbuf()->pubseekoff(off, dir, ios_base:: <pre>-4- Effects: If fail() != true, executes rdbuf()->pubseekoff(off, dir, ios_base::out). </pre> -<p><i>[Dublin: Dietmar Kühl thinks this is probably correct, but would +<p><i>[Dublin: Dietmar Kühl thinks this is probably correct, but would like the opinion of more iostream experts before taking action.]</i></p> <p><i>[Tokyo: Reviewed by the LWG. PJP noted that although his docs are @@ -3269,15 +3450,15 @@ with basic_stringbuf? We could resolve the issue either by changing basic_istream and basic_ostream, or by changing basic_stringbuf. I prefer the latter change (or maybe both changes): I don't see any reason for the standard to -require that std::stringbuf s(std::string("foo"), std::ios_base::in); +require that std::stringbuf s(std::string("foo"), std::ios_base::in); s.pubseekoff(0, std::ios_base::beg); must fail.<br> This requirement is a bit weird. There's no similar requirement for basic_streambuf<>::seekpos, or for basic_filebuf<>::seekoff or basic_filebuf<>::seekpos.]</i></p> <hr> <a name="137"><h3>137. Do use_facet and has_facet look in the global locale?</h3></a><p> -<b>Section:</b> 22.1.1 <a href="lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 17 Mar 1999</p> -<p>Section 22.1.1 <a href="lib-locales.html#lib.locale"> [lib.locale]</a> says:</p> +<b>Section:</b> 22.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 17 Mar 1999</p> +<p>Section 22.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale"> [lib.locale]</a> says:</p> <p>-4- In the call to use_facet<Facet>(loc), the type argument chooses a facet, making available all members of the named type. If @@ -3287,7 +3468,7 @@ check if a locale implements a particular facet with the template function has_facet<Facet>(). </p> <p>This contradicts the specification given in section -22.1.2 <a href="lib-locales.html#lib.locale.global.templates"> [lib.locale.global.templates]</a>: +22.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.global.templates"> [lib.locale.global.templates]</a>: <br><br> template <class Facet> const Facet& use_facet(const locale& loc); <br> @@ -3298,14 +3479,14 @@ locale& loc); <br> -4- Notes: The reference returned remains valid at least as long as any copy of loc exists </p> <p><b>Proposed resolution:</b></p> -<p>Remove the phrase "(or, failing that, in the global locale)" +<p>Remove the phrase "(or, failing that, in the global locale)" from section 22.1.1. </p> <p><b>Rationale:</b></p> <p>Needed for consistency with the way locales are handled elsewhere in the standard.</p> <hr> <a name="139"><h3>139. Optional sequence operation table description unclear</h3></a><p> -<b>Section:</b> 23.1.1 <a href="lib-containers.html#lib.sequence.reqmts"> [lib.sequence.reqmts]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 30 Mar 1999</p> +<b>Section:</b> 23.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.sequence.reqmts"> [lib.sequence.reqmts]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 30 Mar 1999</p> <p>The sentence introducing the Optional sequence operation table (23.1.1 paragraph 12) has two problems:</p> @@ -3318,7 +3499,7 @@ cannot implement them in constant time.''<br> <br> B. That paragraph says nothing about amortized constant time, and it should. </p> <p><b>Proposed resolution:</b></p> -<p>Replace the wording in 23.1.1 paragraph 12 which begins ``The operations in table 68 are provided only..." +<p>Replace the wording in 23.1.1 paragraph 12 which begins ``The operations in table 68 are provided only..." with:</p> <blockquote> @@ -3329,11 +3510,11 @@ with:</p> </blockquote> <hr> <a name="141"><h3>141. basic_string::find_last_of, find_last_not_of say pos instead of xpos</h3></a><p> -<b>Section:</b> 21.3.6.4 <a href="lib-strings.html#lib.string::find.last.of"> [lib.string::find.last.of]</a>, 21.3.6.6 <a href="lib-strings.html#lib.string::find.last.not.of"> [lib.string::find.last.not.of]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Arch Robison <b>Date:</b> 28 Apr 1999</p> +<b>Section:</b> 21.3.6.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::find.last.of"> [lib.string::find.last.of]</a>, 21.3.6.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string::find.last.not.of"> [lib.string::find.last.not.of]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Arch Robison <b>Date:</b> 28 Apr 1999</p> <p>Sections 21.3.6.4 paragraph 1 and 21.3.6.6 paragraph 1 surely have misprints where they say:<br> <br> -— <tt>xpos <= pos</tt> and <tt>pos < size();</tt> +— <tt>xpos <= pos</tt> and <tt>pos < size();</tt> </p> <p>Surely the document meant to say ``<tt>xpos < size()</tt>'' in both places.</p> @@ -3343,19 +3524,19 @@ proposed resolution.]</i></p> <p><b>Proposed resolution:</b></p> <p>Change Sections 21.3.6.4 paragraph 1 and 21.3.6.6 paragraph 1, the line which says:<br> <br> -— <tt>xpos <= pos</tt> and <tt>pos < size();<br> +— <tt>xpos <= pos</tt> and <tt>pos < size();<br> <br> </tt>to:<br> <tt><br> -</tt>— <tt>xpos <= pos</tt> and <tt>xpos < size();</tt> +</tt>— <tt>xpos <= pos</tt> and <tt>xpos < size();</tt> </p> <hr> <a name="142"><h3>142. lexicographical_compare complexity wrong</h3></a><p> -<b>Section:</b> 25.3.8 <a href="lib-algorithms.html#lib.alg.lex.comparison"> [lib.alg.lex.comparison]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 20 Jun 1999</p> +<b>Section:</b> 25.3.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.lex.comparison"> [lib.alg.lex.comparison]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 20 Jun 1999</p> <p>The lexicographical_compare complexity is specified as:<br> <br> - "At most min((last1 - first1), (last2 - first2)) -applications of the corresponding comparison."<br> + "At most min((last1 - first1), (last2 - first2)) +applications of the corresponding comparison."<br> <br> The best I can do is twice that expensive.</p> @@ -3364,7 +3545,7 @@ equality you have to check both < and >? Yes, IMO you are right! (and Matt states this complexity in his book)</p> <p><b>Proposed resolution:</b></p> -<p>Change 25.3.8 <a href="lib-algorithms.html#lib.alg.lex.comparison"> [lib.alg.lex.comparison]</a> complexity to:</p> +<p>Change 25.3.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.lex.comparison"> [lib.alg.lex.comparison]</a> complexity to:</p> <blockquote> At most <tt>2*min((last1 - first1), (last2 - first2))</tt> applications of the corresponding comparison. @@ -3385,7 +3566,7 @@ right! (and Matt states this complexity in his book)</p> </blockquote> <hr> <a name="144"><h3>144. Deque constructor complexity wrong </h3></a><p> -<b>Section:</b> 23.2.1.1 <a href="lib-containers.html#lib.deque.cons"> [lib.deque.cons]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Herb Sutter <b>Date:</b> 9 May 1999</p> +<b>Section:</b> 23.2.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.deque.cons"> [lib.deque.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Herb Sutter <b>Date:</b> 9 May 1999</p> <p>In 23.2.1.1 paragraph 6, the deque ctor that takes an iterator range appears to have complexity requirements which are incorrect, and which contradict the complexity requirements for insert(). I suspect that the text in question, @@ -3396,7 +3577,7 @@ below, was taken from vector:</p> N calls to the copy constructor, and performs no reallocations, where N is last - first.</p> </blockquote> -<p>The word "reallocations" does not really apply to deque. Further, +<p>The word "reallocations" does not really apply to deque. Further, all of the following appears to be spurious:</p> <blockquote> <p>It makes at most 2N calls to the copy constructor of T and log N @@ -3410,14 +3591,14 @@ an efficiency advantage from knowing in advance the number of elements to insert?</p> <p><b>Proposed resolution:</b></p> <p>In 23.2.1.1 paragraph 6, replace the Complexity description, including the -footnote, with the following text (which also corrects the "abd" +footnote, with the following text (which also corrects the "abd" typo):</p> <blockquote> <p>Complexity: Makes last - first calls to the copy constructor of T.</p> </blockquote> <hr> <a name="146"><h3>146. complex<T> Inserter and Extractor need sentries</h3></a><p> -<b>Section:</b> 26.2.6 <a href="lib-numerics.html#lib.complex.ops"> [lib.complex.ops]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 12 May 1999</p> +<b>Section:</b> 26.2.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.ops"> [lib.complex.ops]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 12 May 1999</p> <p>The <u> extractor</u> for complex numbers is specified as: </p> <blockquote> @@ -3457,7 +3638,7 @@ Effects: inserts the complex number x onto the stream o as if it were implemente s.flags(o.flags()); <br> s.imbue(o.getloc()); <br> s.precision(o.precision()); <br> - s << '(' << x.real() << "," << x.imag() << ')'; <br> + s << '(' << x.real() << "," << x.imag() << ')'; <br> return o << s.str(); <br> }</p> @@ -3474,7 +3655,7 @@ consistency with the other inserters and extractors in the library. Regarding the issue of padding in the inserter, I don't know what the intent was. </p> <p><b>Proposed resolution:</b></p> -<p>After 26.2.6 <a href="lib-numerics.html#lib.complex.ops"> [lib.complex.ops]</a> paragraph 14 (operator>>), add a +<p>After 26.2.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.complex.ops"> [lib.complex.ops]</a> paragraph 14 (operator>>), add a Notes clause:</p> <blockquote> @@ -3486,13 +3667,13 @@ same for each of the simpler extractions.</p> </blockquote> <p><b>Rationale:</b></p> <p>For extractors, the note is added to make it clear that skipping whitespace -follows an "all-or-none" rule.</p> +follows an "all-or-none" rule.</p> <p>For inserters, the LWG believes there is no defect; the standard is correct as written.</p> <hr> <a name="147"><h3>147. Library Intro refers to global functions that aren't global</h3></a><p> -<b>Section:</b> 17.4.4.3 <a href="lib-intro.html#lib.global.functions"> [lib.global.functions]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Lois Goldthwaite <b>Date:</b> 4 Jun 1999</p> +<b>Section:</b> 17.4.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.global.functions"> [lib.global.functions]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Lois Goldthwaite <b>Date:</b> 4 Jun 1999</p> <p>The library had many global functions until 17.4.1.1 [lib.contents] paragraph 2 was added: </p> @@ -3504,7 +3685,7 @@ within namespace std. </p> </blockquote> -<p>It appears "global function" was never updated in the following: </p> +<p>It appears "global function" was never updated in the following: </p> <blockquote> @@ -3540,7 +3721,7 @@ virtual or global functions, however. </p> </blockquote> </blockquote> <p><b>Proposed resolution:</b></p> -<p> Change "global" to "global or non-member" in:</p> +<p> Change "global" to "global or non-member" in:</p> <blockquote> <p>17.4.4.3 [lib.global.functions] section title,<br> 17.4.4.3 [lib.global.functions] para 1,<br> @@ -3552,27 +3733,27 @@ virtual or global functions, however. </p> <p><b>Rationale:</b></p> <p> Because operator new and delete are global, the proposed resolution -was changed from "non-member" to "global or non-member. +was changed from "non-member" to "global or non-member. </p> <hr> <a name="148"><h3>148. Functions in the example facet BoolNames should be const</h3></a><p> -<b>Section:</b> 22.2.8 <a href="lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Jeremy Siek <b>Date:</b> 3 Jun 1999</p> -<p>In 22.2.8 <a href="lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> paragraph 13, the do_truename() and +<b>Section:</b> 22.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Jeremy Siek <b>Date:</b> 3 Jun 1999</p> +<p>In 22.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> paragraph 13, the do_truename() and do_falsename() functions in the example facet BoolNames should be const. The functions they are overriding in numpunct_byname<char> are const. </p> <p><b>Proposed resolution:</b></p> -<p>In 22.2.8 <a href="lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> paragraph 13, insert "const" in +<p>In 22.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> paragraph 13, insert "const" in two places:</p> <blockquote> - <p><tt>string do_truename() const { return "Oui Oui!"; }<br> - string do_falsename() const { return "Mais Non!"; }</tt></p> + <p><tt>string do_truename() const { return "Oui Oui!"; }<br> + string do_falsename() const { return "Mais Non!"; }</tt></p> </blockquote> <hr> <a name="150"><h3>150. Find_first_of says integer instead of iterator </h3></a><p> -<b>Section:</b> 25.1.4 <a href="lib-algorithms.html#lib.alg.find.first.of"> [lib.alg.find.first.of]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt McClure <b>Date:</b> 30 Jun 1999</p> +<b>Section:</b> 25.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.find.first.of"> [lib.alg.find.first.of]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt McClure <b>Date:</b> 30 Jun 1999</p> <p><b>Proposed resolution:</b></p> -<p>Change 25.1.4 <a href="lib-algorithms.html#lib.alg.find.first.of"> [lib.alg.find.first.of]</a> paragraph 2 from:</p> +<p>Change 25.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.find.first.of"> [lib.alg.find.first.of]</a> paragraph 2 from:</p> <blockquote> <p>Returns: The first iterator i in the range [first1, last1) such @@ -3587,7 +3768,7 @@ that for some iterator j in the range [first2, last2) ...</p> </blockquote> <hr> <a name="151"><h3>151. Can't currently clear() empty container</h3></a><p> -<b>Section:</b> 23.1.1 <a href="lib-containers.html#lib.sequence.reqmts"> [lib.sequence.reqmts]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Ed Brey <b>Date:</b> 21 Jun 1999</p> +<b>Section:</b> 23.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.sequence.reqmts"> [lib.sequence.reqmts]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Ed Brey <b>Date:</b> 21 Jun 1999</p> <p>For both sequences and associative containers, a.clear() has the semantics of erase(a.begin(),a.end()), which is undefined for an empty container since erase(q1,q2) requires that q1 be dereferenceable @@ -3625,24 +3806,24 @@ iterators or certain kinds of iterators is unnecessary. </p> </blockquote> <hr> -<a name="152"><h3>152. Typo in <tt>scan_is()</tt> semantics</h3></a><p> -<b>Section:</b> 22.2.1.1.2 <a href="lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<a name="152"></a><h3><a name="152">152. Typo in <tt>scan_is()</tt> semantics</a></h3><p> +<b>Section:</b> 22.2.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>The semantics of <tt>scan_is()</tt> (paragraphs 4 and 6) is not exactly described because there is no function <tt>is()</tt> which only takes a character as argument. Also, in the effects clause (paragraph 3), the semantic is also kept vague.</p> <p><b>Proposed resolution:</b></p> -<p>In 22.2.1.1.2 <a href="lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a> paragraphs 4 and 6, change the returns +<p>In 22.2.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.virtuals"> [lib.locale.ctype.virtuals]</a> paragraphs 4 and 6, change the returns clause from:</p> <blockquote> - <p>"... such that <tt>is(*p)</tt> -would..."</p> + <p>"... such that <tt>is(*p)</tt> +would..."</p> </blockquote> -<p>to: "... such that <tt>is(m, *p)</tt> - would...."</p> +<p>to: "... such that <tt>is(m, *p)</tt> + would...."</p> <hr> <a name="153"><h3>153. Typo in <tt>narrow()</tt> semantics</h3></a><p> -<b>Section:</b> 22.2.1.3.2 <a href="lib-locales.html#lib.facet.ctype.char.members"> [lib.facet.ctype.char.members]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<b>Section:</b> 22.2.1.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.ctype.char.members"> [lib.facet.ctype.char.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>The description of the array version of <tt>narrow()</tt> (in paragraph 11) is flawed: There is no member <tt>do_narrow()</tt> which takes only three arguments because in addition to the range a default @@ -3653,7 +3834,7 @@ two signatures followed by a <b>Returns</b> clause that only addresses one of them.</p> <p><b>Proposed resolution:</b></p> -<p>Change the returns clause in 22.2.1.3.2 <a href="lib-locales.html#lib.facet.ctype.char.members"> [lib.facet.ctype.char.members]</a> +<p>Change the returns clause in 22.2.1.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.ctype.char.members"> [lib.facet.ctype.char.members]</a> paragraph 10 from:</p> <p> Returns: do_widen(low, high, to).</p> @@ -3661,7 +3842,7 @@ paragraph 10 from:</p> <p> Returns: do_widen(c) or do_widen(low, high, to), respectively.</p> -<p>Change 22.2.1.3.2 <a href="lib-locales.html#lib.facet.ctype.char.members"> [lib.facet.ctype.char.members]</a> paragraph 10 and 11 from:</p> +<p>Change 22.2.1.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.ctype.char.members"> [lib.facet.ctype.char.members]</a> paragraph 10 and 11 from:</p> <pre> char narrow(char c, char /*dfault*/) const; const char* narrow(const char* low, const char* high, char /*dfault*/, char* to) const;</pre> @@ -3678,24 +3859,24 @@ defined version could be different.]</i></p> <p><i>[Post-Tokyo: Dietmar provided the above wording at the request of the LWG. He could find no other places the problem occurred. He -asks for clarification of the Kona "a user defined -version..." comment above. Perhaps it was a circuitous way of -saying "dfault" needed to be uncommented?]</i></p> +asks for clarification of the Kona "a user defined +version..." comment above. Perhaps it was a circuitous way of +saying "dfault" needed to be uncommented?]</i></p> <p><i>[Post-Toronto: the issues list maintainer has merged in the -proposed resolution from issue <a href="lwg-closed.html#207">207</a>, which addresses the +proposed resolution from issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#207">207</a>, which addresses the same paragraphs.]</i></p> <hr> <a name="154"><h3>154. Missing <tt>double</tt> specifier for <tt>do_get()</tt> </h3></a><p> -<b>Section:</b> 22.2.2.1.2 <a href="lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<b>Section:</b> 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>The table in paragraph 7 for the length modifier does not list the length modifier <tt>l</tt> to be applied if the type is <tt>double</tt>. Thus, the standard asks the implementation to do undefined things when using <tt>scanf()</tt> (the missing length modifier for <tt>scanf()</tt> when scanning <tt>double</tt>s is actually a problem I found quite often in production code, too).</p> <p><b>Proposed resolution:</b></p> -<p>In 22.2.2.1.2 <a href="lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a>, paragraph 7, add a row in the Length +<p>In 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a>, paragraph 7, add a row in the Length Modifier table to say that for <tt>double</tt> a length modifier <tt>l</tt> is to be used.</p> <p><b>Rationale:</b></p> @@ -3703,33 +3884,33 @@ Modifier table to say that for <tt>double</tt> a length modifier <hr> <a name="155"><h3>155. Typo in naming the class defining the class <tt>Init</tt> </h3></a><p> -<b>Section:</b> 27.3 <a href="lib-iostreams.html#lib.iostream.objects"> [lib.iostream.objects]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<b>Section:</b> 27.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostream.objects"> [lib.iostream.objects]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>There are conflicting statements about where the class -<tt>Init</tt> is defined. According to 27.3 <a href="lib-iostreams.html#lib.iostream.objects"> [lib.iostream.objects]</a> paragraph 2 -it is defined as <tt>basic_ios::Init</tt>, according to 27.4.2 <a href="lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> it is defined as <tt>ios_base::Init</tt>.</p> +<tt>Init</tt> is defined. According to 27.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostream.objects"> [lib.iostream.objects]</a> paragraph 2 +it is defined as <tt>basic_ios::Init</tt>, according to 27.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> it is defined as <tt>ios_base::Init</tt>.</p> <p><b>Proposed resolution:</b></p> -<p>Change 27.3 <a href="lib-iostreams.html#lib.iostream.objects"> [lib.iostream.objects]</a> paragraph 2 from -"<tt>basic_ios::Init"</tt> to -"<tt>ios_base::Init"</tt>.</p> +<p>Change 27.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostream.objects"> [lib.iostream.objects]</a> paragraph 2 from +"<tt>basic_ios::Init"</tt> to +"<tt>ios_base::Init"</tt>.</p> <p><b>Rationale:</b></p> <p>Although not strictly wrong, the standard was misleading enough to warrant the change.</p> <hr> -<a name="156"><h3>156. Typo in <tt>imbue()</tt> description</h3></a><p> -<b>Section:</b> 27.4.2.3 <a href="lib-iostreams.html#lib.ios.base.locales"> [lib.ios.base.locales]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<a name="156"></a><h3><a name="156">156. Typo in <tt>imbue()</tt> description</a></h3><p> +<b>Section:</b> 27.4.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base.locales"> [lib.ios.base.locales]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>There is a small discrepancy between the declarations of -<tt>imbue()</tt>: in 27.4.2 <a href="lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> the argument is passed as -<tt>locale const&</tt> (correct), in 27.4.2.3 <a href="lib-iostreams.html#lib.ios.base.locales"> [lib.ios.base.locales]</a> it +<tt>imbue()</tt>: in 27.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base"> [lib.ios.base]</a> the argument is passed as +<tt>locale const&</tt> (correct), in 27.4.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base.locales"> [lib.ios.base.locales]</a> it is passed as <tt>locale const</tt> (wrong).</p> <p><b>Proposed resolution:</b></p> -<p>In 27.4.2.3 <a href="lib-iostreams.html#lib.ios.base.locales"> [lib.ios.base.locales]</a> change the <tt>imbue</tt> argument -from "<tt>locale const" to "locale -const&".</tt> +<p>In 27.4.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base.locales"> [lib.ios.base.locales]</a> change the <tt>imbue</tt> argument +from "<tt>locale const" to "locale +const&".</tt> </p> <hr> <a name="158"><h3>158. Underspecified semantics for <tt>setbuf()</tt> </h3></a><p> -<b>Section:</b> 27.5.2.4.2 <a href="lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<b>Section:</b> 27.5.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>The default behavior of <tt>setbuf()</tt> is described only for the situation that <tt>gptr() != 0 && gptr() != egptr()</tt>: namely to do nothing. What has to be done in other situations @@ -3741,12 +3922,12 @@ buffer management of derived classes unless these classes do it themselves, the default behavior of <tt>setbuf()</tt> should always be to do nothing.</p> <p><b>Proposed resolution:</b></p> -<p>Change 27.5.2.4.2 <a href="lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a>, paragraph 3, Default behavior, -to: "Default behavior: Does nothing. Returns this."</p> +<p>Change 27.5.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a>, paragraph 3, Default behavior, +to: "Default behavior: Does nothing. Returns this."</p> <hr> <a name="159"><h3>159. Strange use of <tt>underflow()</tt> </h3></a><p> -<b>Section:</b> 27.5.2.4.3 <a href="lib-iostreams.html#lib.streambuf.virt.get"> [lib.streambuf.virt.get]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<b>Section:</b> 27.5.2.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.virt.get"> [lib.streambuf.virt.get]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>The description of the meaning of the result of <tt>showmanyc()</tt> seems to be rather strange: It uses calls to <tt>underflow()</tt>. Using <tt>underflow()</tt> is strange because @@ -3754,34 +3935,34 @@ this function only reads the current character but does not extract it, <tt>uflow()</tt> would extract the current character. This should be fixed to use <tt>sbumpc()</tt> instead.</p> <p><b>Proposed resolution:</b></p> -<p>Change 27.5.2.4.3 <a href="lib-iostreams.html#lib.streambuf.virt.get"> [lib.streambuf.virt.get]</a> paragraph 1, +<p>Change 27.5.2.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.virt.get"> [lib.streambuf.virt.get]</a> paragraph 1, <tt>showmanyc()</tt>returns clause, by replacing the word -"supplied" with the words "extracted from the -stream".</p> +"supplied" with the words "extracted from the +stream".</p> <hr> <a name="160"><h3>160. Typo: Use of non-existing function <tt>exception()</tt> </h3></a><p> -<b>Section:</b> 27.6.1.1 <a href="lib-iostreams.html#lib.istream"> [lib.istream]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<b>Section:</b> 27.6.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream"> [lib.istream]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>The paragraph 4 refers to the function <tt>exception()</tt> which is not defined. Probably, the referred function is <tt>basic_ios<>::exceptions()</tt>.</p> <p><b>Proposed resolution:</b></p> -<p>In 27.6.1.1 <a href="lib-iostreams.html#lib.istream"> [lib.istream]</a>, 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>, paragraph 1, -27.6.2.1 <a href="lib-iostreams.html#lib.ostream"> [lib.ostream]</a>, paragraph 3, and 27.6.2.5.1 <a href="lib-iostreams.html#lib.ostream.formatted.reqmts"> [lib.ostream.formatted.reqmts]</a>, -paragraph 1, change "<tt>exception()" to -"exceptions()"</tt>.</p> +<p>In 27.6.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream"> [lib.istream]</a>, 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>, paragraph 1, +27.6.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream"> [lib.ostream]</a>, paragraph 3, and 27.6.2.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.formatted.reqmts"> [lib.ostream.formatted.reqmts]</a>, +paragraph 1, change "<tt>exception()" to +"exceptions()"</tt>.</p> -<p><i>[Note to Editor: "exceptions" with an "s" +<p><i>[Note to Editor: "exceptions" with an "s" is the correct spelling.]</i></p> <hr> <a name="161"><h3>161. Typo: <tt>istream_iterator</tt> vs. <tt>istreambuf_iterator</tt> </h3></a><p> -<b>Section:</b> 27.6.1.2.2 <a href="lib-iostreams.html#lib.istream.formatted.arithmetic"> [lib.istream.formatted.arithmetic]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<b>Section:</b> 27.6.1.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted.arithmetic"> [lib.istream.formatted.arithmetic]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>The note in the second paragraph pretends that the first argument is an object of type <tt>istream_iterator</tt>. This is wrong: It is an object of type <tt>istreambuf_iterator</tt>.</p> <p><b>Proposed resolution:</b></p> -<p>Change 27.6.1.2.2 <a href="lib-iostreams.html#lib.istream.formatted.arithmetic"> [lib.istream.formatted.arithmetic]</a> from:</p> +<p>Change 27.6.1.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted.arithmetic"> [lib.istream.formatted.arithmetic]</a> from:</p> <blockquote> <p>The first argument provides an object of the istream_iterator class...</p> </blockquote> @@ -3791,8 +3972,8 @@ an object of type <tt>istreambuf_iterator</tt>.</p> </blockquote> <hr> <a name="164"><h3>164. do_put() has apparently unused fill argument</h3></a><p> -<b>Section:</b> 22.2.5.3.2 <a href="lib-locales.html#lib.locale.time.put.virtuals"> [lib.locale.time.put.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 23 Jul 1999</p> -<p>In 22.2.5.3.2 <a href="lib-locales.html#lib.locale.time.put.virtuals"> [lib.locale.time.put.virtuals]</a> the do_put() function is specified +<b>Section:</b> 22.2.5.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.time.put.virtuals"> [lib.locale.time.put.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> 23 Jul 1999</p> +<p>In 22.2.5.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.time.put.virtuals"> [lib.locale.time.put.virtuals]</a> the do_put() function is specified as taking a fill character as an argument, but the description of the function does not say whether the character is used at all and, if so, in which way. The same holds for any format control parameters that @@ -3802,7 +3983,7 @@ character in any way? In any case, the specification of time_put.do_put() looks inconsistent to me.<br> <br> Is the signature of do_put() wrong, or is the effects clause incomplete?</p> <p><b>Proposed resolution:</b></p> -<p>Add the following note after 22.2.5.3.2 <a href="lib-locales.html#lib.locale.time.put.virtuals"> [lib.locale.time.put.virtuals]</a> +<p>Add the following note after 22.2.5.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.time.put.virtuals"> [lib.locale.time.put.virtuals]</a> paragraph 2:</p> <blockquote> <p> [Note: the <tt>fill</tt> argument may be used in the implementation-defined formats, or by derivations. A space character is a reasonable default @@ -3814,10 +3995,10 @@ users need some guidance on what to pass for the <tt>fill</tt> argument since the standard doesn't say how it's used.</p> <hr> <a name="165"><h3>165. <tt>xsputn()</tt>, <tt>pubsync()</tt> never called by <tt>basic_ostream</tt> members?</h3></a><p> -<b>Section:</b> 27.6.2.1 <a href="lib-iostreams.html#lib.ostream"> [lib.ostream]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<b>Section:</b> 27.6.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream"> [lib.ostream]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>Paragraph 2 explicitly states that none of the <tt>basic_ostream</tt> -functions falling into one of the groups "formatted output functions" -and "unformatted output functions" calls any stream buffer function +functions falling into one of the groups "formatted output functions" +and "unformatted output functions" calls any stream buffer function which might call a virtual function other than <tt>overflow()</tt>. Basically this is fine but this implies that <tt>sputn()</tt> (this function would call the virtual function <tt>xsputn()</tt>) is never called by any of the standard @@ -3826,10 +4007,10 @@ call <tt>xsputn()</tt> for strings... Also, the statement that <tt>overflow()</t is the only virtual member of <tt>basic_streambuf</tt> called is in conflict with the definition of <tt>flush()</tt> which calls <tt>rdbuf()->pubsync()</tt> and thereby the virtual function <tt>sync()</tt> (<tt>flush()</tt> is listed -under "unformatted output functions").</p> -<p>In addition, I guess that the sentence starting with "They may use other -public members of <tt>basic_ostream</tt> ..." probably was intended to -start with "They may use other public members of <tt>basic_streamuf</tt>..." +under "unformatted output functions").</p> +<p>In addition, I guess that the sentence starting with "They may use other +public members of <tt>basic_ostream</tt> ..." probably was intended to +start with "They may use other public members of <tt>basic_streamuf</tt>..." although the problem with the virtual members exists in both cases.</p> <p>I see two obvious resolutions:</p> <ol> @@ -3861,34 +4042,34 @@ called from what functions and eg to state specifically that flush() is allowed to call sync() while other functions are not.]</i></p> <hr> <a name="168"><h3>168. Typo: formatted vs. unformatted</h3></a><p> -<b>Section:</b> 27.6.2.6 <a href="lib-iostreams.html#lib.ostream.unformatted"> [lib.ostream.unformatted]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<b>Section:</b> 27.6.2.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.unformatted"> [lib.ostream.unformatted]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>The first paragraph begins with a descriptions what has to be done in <i>formatted</i> output functions. Probably this is a typo and the paragraph really want to describe unformatted output functions...</p> <p><b>Proposed resolution:</b></p> -<p>In 27.6.2.6 <a href="lib-iostreams.html#lib.ostream.unformatted"> [lib.ostream.unformatted]</a> paragraph 1, the first and last -sentences, change the word "formatted" to -"unformatted":</p> +<p>In 27.6.2.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.unformatted"> [lib.ostream.unformatted]</a> paragraph 1, the first and last +sentences, change the word "formatted" to +"unformatted":</p> <blockquote> - <p>"Each <b>unformatted </b> output function begins ..."<br> - "... value specified for the <b>unformatted </b> output - function."</p> + <p>"Each <b>unformatted </b> output function begins ..."<br> + "... value specified for the <b>unformatted </b> output + function."</p> </blockquote> <hr> <a name="169"><h3>169. Bad efficiency of <tt>overflow()</tt> mandated</h3></a><p> -<b>Section:</b> 27.7.1.3 <a href="lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<b>Section:</b> 27.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> <p>Paragraph 8, Notes, of this section seems to mandate an extremely inefficient way of buffer handling for <tt>basic_stringbuf</tt>, especially in view of the restriction that <tt>basic_ostream</tt> -member functions are not allowed to use <tt>xsputn()</tt> (see 27.6.2.1 <a href="lib-iostreams.html#lib.ostream"> [lib.ostream]</a>): For each character to be inserted, a new buffer +member functions are not allowed to use <tt>xsputn()</tt> (see 27.6.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream"> [lib.ostream]</a>): For each character to be inserted, a new buffer is to be created.</p> <p>Of course, the resolution below requires some handling of simultaneous input and output since it is no longer possible to update <tt>egptr()</tt> whenever <tt>epptr()</tt> is changed. A possible solution is to handle this in <tt>underflow()</tt>.</p> <p><b>Proposed resolution:</b></p> -<p>In 27.7.1.3 <a href="lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a> paragraph 8, Notes, insert the words -"at least" as in the following:</p> +<p>In 27.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a> paragraph 8, Notes, insert the words +"at least" as in the following:</p> <blockquote> <p>To make a write position available, the function reallocates (or initially allocates) an array object with a sufficient number of elements to hold the @@ -3898,24 +4079,24 @@ solution is to handle this in <tt>underflow()</tt>.</p> <hr> <a name="170"><h3>170. Inconsistent definition of <tt>traits_type</tt> </h3></a><p> -<b>Section:</b> 27.7.4 <a href="lib-iostreams.html#lib.stringstream"> [lib.stringstream]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> -<p>The classes <tt>basic_stringstream</tt> (27.7.4 <a href="lib-iostreams.html#lib.stringstream"> [lib.stringstream]</a>), -<tt>basic_istringstream</tt> (27.7.2 <a href="lib-iostreams.html#lib.istringstream"> [lib.istringstream]</a>), and -<tt>basic_ostringstream</tt> (27.7.3 <a href="lib-iostreams.html#lib.ostringstream"> [lib.ostringstream]</a>) are inconsistent +<b>Section:</b> 27.7.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringstream"> [lib.stringstream]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<p>The classes <tt>basic_stringstream</tt> (27.7.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringstream"> [lib.stringstream]</a>), +<tt>basic_istringstream</tt> (27.7.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istringstream"> [lib.istringstream]</a>), and +<tt>basic_ostringstream</tt> (27.7.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostringstream"> [lib.ostringstream]</a>) are inconsistent in their definition of the type <tt>traits_type</tt>: For <tt>istringstream</tt>, this type is defined, for the other two it is not. This should be consistent.</p> <p><b>Proposed resolution:</b></p> <p><b>Proposed resolution:</b></p> <p>To the declarations of -<tt>basic_ostringstream</tt> (27.7.3 <a href="lib-iostreams.html#lib.ostringstream"> [lib.ostringstream]</a>) and -<tt>basic_stringstream</tt> (27.7.4 <a href="lib-iostreams.html#lib.stringstream"> [lib.stringstream]</a>) add:</p> +<tt>basic_ostringstream</tt> (27.7.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostringstream"> [lib.ostringstream]</a>) and +<tt>basic_stringstream</tt> (27.7.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringstream"> [lib.stringstream]</a>) add:</p> <blockquote> <pre>typedef traits traits_type;</pre> </blockquote> <hr> <a name="171"><h3>171. Strange <tt>seekpos()</tt> semantics due to joint position</h3></a><p> -<b>Section:</b> 27.8.1.4 <a href="lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> -<p>Overridden virtual functions, seekpos()</p> <p>In 27.8.1.1 <a href="lib-iostreams.html#lib.filebuf"> [lib.filebuf]</a> paragraph 3, it is stated that a joint input and +<b>Section:</b> 27.8.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Jul 1999</p> +<p>Overridden virtual functions, seekpos()</p> <p>In 27.8.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.filebuf"> [lib.filebuf]</a> paragraph 3, it is stated that a joint input and output position is maintained by <tt>basic_filebuf</tt>. Still, the description of <tt>seekpos()</tt> seems to talk about different file positions. In particular, it is unclear (at least to me) what is @@ -3968,10 +4149,10 @@ paragraph 14 from:</p> <hr> <a name="172"><h3>172. Inconsistent types for <tt>basic_istream::ignore()</tt> </h3></a><p> -<b>Section:</b> 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Greg Comeau, Dietmar Kühl <b>Date:</b> 23 Jul 1999</p> -<p>In 27.6.1.1 <a href="lib-iostreams.html#lib.istream"> [lib.istream]</a> the function +<b>Section:</b> 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Greg Comeau, Dietmar Kühl <b>Date:</b> 23 Jul 1999</p> +<p>In 27.6.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream"> [lib.istream]</a> the function <tt>ignore()</tt> gets an object of type <tt>streamsize</tt> as first -argument. However, in 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> +argument. However, in 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> paragraph 23 the first argument is of type <tt>int.</tt> </p> @@ -3979,7 +4160,7 @@ paragraph 23 the first argument is of type <tt>int.</tt> everything is consistent if <tt>streamsize</tt> is typedef to be <tt>int</tt>. However, this is almost certainly not what was intended. The same thing happened to <tt>basic_filebuf::setbuf()</tt>, -as described in issue <a href="lwg-defects.html#173">173</a>.</p> +as described in issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#173">173</a>.</p> <p>Darin Adler also submitted this issue, commenting: Either 27.6.1.1 should be modified @@ -3987,18 +4168,18 @@ to show a first parameter of type int, or 27.6.1.3 should be modified to show a first parameter of type streamsize and use numeric_limits<streamsize>::max.</p> <p><b>Proposed resolution:</b></p> -<p>In 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> paragraph 23 and 24, change both uses +<p>In 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> paragraph 23 and 24, change both uses of <tt>int</tt> in the description of <tt>ignore()</tt> to <tt>streamsize</tt>.</p> <hr> <a name="173"><h3>173. Inconsistent types for <tt>basic_filebuf::setbuf()</tt> </h3></a><p> -<b>Section:</b> 27.8.1.4 <a href="lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Greg Comeau, Dietmar Kühl <b>Date:</b> 23 Jul 1999</p> +<b>Section:</b> 27.8.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Greg Comeau, Dietmar Kühl <b>Date:</b> 23 Jul 1999</p> <p> -In 27.8.1.1 <a href="lib-iostreams.html#lib.filebuf"> [lib.filebuf]</a> the function <tt>setbuf()</tt> gets an +In 27.8.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.filebuf"> [lib.filebuf]</a> the function <tt>setbuf()</tt> gets an object of type <tt>streamsize</tt> as second argument. However, in -27.8.1.4 <a href="lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a> paragraph 9 the second argument is of type +27.8.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a> paragraph 9 the second argument is of type <tt>int</tt>. </p> @@ -4007,32 +4188,32 @@ As far as I can see this is not really a contradiction because everything is consistent if <tt>streamsize</tt> is typedef to be <tt>int</tt>. However, this is almost certainly not what was intended. The same thing happened to <tt>basic_istream::ignore()</tt>, -as described in issue <a href="lwg-defects.html#172">172</a>. +as described in issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#172">172</a>. </p> <p><b>Proposed resolution:</b></p> -<p>In 27.8.1.4 <a href="lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a> paragraph 9, change all uses of +<p>In 27.8.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.filebuf.virtuals"> [lib.filebuf.virtuals]</a> paragraph 9, change all uses of <tt>int</tt> in the description of <tt>setbuf()</tt> to <tt>streamsize</tt>.</p> <hr> <a name="174"><h3>174. Typo: <tt>OFF_T</tt> vs. <tt>POS_T</tt> </h3></a><p> -<b>Section:</b> D.6 <a href="future.html#depr.ios.members"> [depr.ios.members]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 23 Jul 1999</p> +<b>Section:</b> D.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.ios.members"> [depr.ios.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 23 Jul 1999</p> <p>According to paragraph 1 of this section, <tt>streampos</tt> is the type <tt>OFF_T</tt>, the same type as <tt>streamoff</tt>. However, in paragraph 6 the <tt>streampos</tt> gets the type <tt>POS_T</tt> </p> <p><b>Proposed resolution:</b></p> -<p>Change D.6 <a href="future.html#depr.ios.members"> [depr.ios.members]</a> paragraph 1 from "<tt>typedef -OFF_T streampos;</tt>" to "<tt>typedef POS_T -streampos;</tt>"</p> +<p>Change D.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.ios.members"> [depr.ios.members]</a> paragraph 1 from "<tt>typedef +OFF_T streampos;</tt>" to "<tt>typedef POS_T +streampos;</tt>"</p> <hr> <a name="175"><h3>175. Ambiguity for <tt>basic_streambuf::pubseekpos()</tt> and a few other functions.</h3></a><p> -<b>Section:</b> D.6 <a href="future.html#depr.ios.members"> [depr.ios.members]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 23 Jul 1999</p> +<b>Section:</b> D.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.ios.members"> [depr.ios.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 23 Jul 1999</p> <p>According to paragraph 8 of this section, the methods <tt>basic_streambuf::pubseekpos()</tt>, <tt>basic_ifstream::open()</tt>, and <tt>basic_ofstream::open</tt> -"may" be overloaded by a version of this function taking the +"may" be overloaded by a version of this function taking the type <tt>ios_base::open_mode</tt> as last argument argument instead of <tt>ios_base::openmode</tt> (<tt>ios_base::open_mode</tt> is defined in this section to be an alias for one of the integral types). The @@ -4041,29 +4222,137 @@ three cases. However, this generates an ambiguity with the overloaded version because now the arguments are absolutely identical if the last argument is not specified.</p> <p><b>Proposed resolution:</b></p> -<p>In D.6 <a href="future.html#depr.ios.members"> [depr.ios.members]</a> paragraph 8, remove the default arguments for +<p>In D.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.ios.members"> [depr.ios.members]</a> paragraph 8, remove the default arguments for <tt>basic_streambuf::pubseekpos()</tt>, <tt>basic_ifstream::open()</tt>, and <tt>basic_ofstream::open().</tt> </p> <hr> <a name="176"><h3>176. <tt>exceptions()</tt> in <tt>ios_base</tt>...?</h3></a><p> -<b>Section:</b> D.6 <a href="future.html#depr.ios.members"> [depr.ios.members]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 23 Jul 1999</p> -<p>The "overload" for the function <tt>exceptions()</tt> in +<b>Section:</b> D.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.ios.members"> [depr.ios.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 23 Jul 1999</p> +<p>The "overload" for the function <tt>exceptions()</tt> in paragraph 8 gives the impression that there is another function of this function defined in class <tt>ios_base</tt>. However, this is not the case. Thus, it is hard to tell how the semantics (paragraph 9) can -be implemented: "Call the corresponding member function specified -in clause 27 <a href="lib-iostreams.html#lib.input.output"> [lib.input.output]</a>."</p> +be implemented: "Call the corresponding member function specified +in clause 27 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.input.output"> [lib.input.output]</a>."</p> <p><b>Proposed resolution:</b></p> -<p>In D.6 <a href="future.html#depr.ios.members"> [depr.ios.members]</a> paragraph 8, move the declaration of the +<p>In D.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/future.html#depr.ios.members"> [depr.ios.members]</a> paragraph 8, move the declaration of the function <tt>exceptions()</tt>into class <tt>basic_ios</tt>.</p> <hr> +<a name="179"><h3>179. Comparison of const_iterators to iterators doesn't work</h3></a><p> +<b>Section:</b> 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 2 Jul 1998</p> +<p>Currently the following will not compile on two well-known standard +library implementations:</p> + +<blockquote> + <pre>#include <set> +using namespace std; + +void f(const set<int> &s) +{ + set<int>::iterator i; + if (i==s.end()); // s.end() returns a const_iterator +}</pre> +</blockquote> + +<p> +The reason this doesn't compile is because operator== was implemented +as a member function of the nested classes set:iterator and +set::const_iterator, and there is no conversion from const_iterator to +iterator. Surprisingly, (s.end() == i) does work, though, because of +the conversion from iterator to const_iterator. +</p> + +<p> +I don't see a requirement anywhere in the standard that this must +work. Should there be one? If so, I think the requirement would need +to be added to the tables in section 24.1.1. I'm not sure about the +wording. If this requirement existed in the standard, I would think +that implementors would have to make the comparison operators +non-member functions.</p> + +<p>This issues was also raised on comp.std.c++ by Darin +Adler. The example given was:</p> + +<blockquote> + <pre>bool check_equal(std::deque<int>::iterator i, +std::deque<int>::const_iterator ci) +{ +return i == ci; +}</pre> +</blockquote> + +<p>Comment from John Potter:</p> +<blockquote> + <p> + In case nobody has noticed, accepting it will break reverse_iterator. + </p> + + <p> + The fix is to make the comparison operators templated on two types. + </p> + + <pre> template <class Iterator1, class Iterator2> + bool operator== (reverse_iterator<Iterator1> const& x, + reverse_iterator<Iterator2> const& y); + </pre> + + <p> + Obviously: return x.base() == y.base(); + </p> + + <p> + Currently, no reverse_iterator to const_reverse_iterator compares are + valid. + </p> + + <p> + BTW, I think the issue is in support of bad code. Compares should be + between two iterators of the same type. All std::algorithms require + the begin and end iterators to be of the same type. + </p> +</blockquote> +<p><b>Proposed resolution:</b></p> +<p>Insert this paragraph after 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> paragraph 7:</p> +<blockquote> + <p>In the expressions</p> + <pre> i == j + i != j + i < j + i <= j + i >= j + i > j + i - j + </pre> + <p>Where i and j denote objects of a container's iterator type, + either or both may be replaced by an object of the container's + const_iterator type referring to the same element with no + change in semantics.</p> +</blockquote> + +<p><i>[post-Toronto: Judy supplied a proposed resolution saying that +<tt>iterator</tt> and <tt>const_iterator</tt> could be freely mixed in +iterator comparison and difference operations.]</i></p> + +<p><i>[Redmond: Dave and Howard supplied a new proposed resolution which +explicitly listed expressions; there was concern that the previous +proposed resolution was too informal.]</i></p> +<p><b>Rationale:</b></p> +<p> +The LWG believes it is clear that the above wording applies only to +the nested types <tt>X::iterator</tt> and <tt>X::const_iterator</tt>, +where <tt>X</tt> is a container. There is no requirement that +<tt>X::reverse_iterator</tt> and <tt>X::const_reverse_iterator</tt> +can be mixed. If mixing them is considered important, that's a +separate issue. (Issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#280">280</a>.) +</p> +<hr> <a name="181"><h3>181. make_pair() unintended behavior</h3></a><p> -<b>Section:</b> 20.2.2 <a href="lib-utilities.html#lib.pairs"> [lib.pairs]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 3 Aug 1999</p> +<b>Section:</b> 20.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.pairs"> [lib.pairs]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 3 Aug 1999</p> <p>The claim has surfaced in Usenet that expressions such as<br> <br> - <tt>make_pair("abc", 3)</tt><br> + <tt>make_pair("abc", 3)</tt><br> <br> are illegal, notwithstanding their use in examples, because template instantiation tries to bind the first template parameter to <tt> const char (&)[4]</tt>, which type is uncopyable.<br> @@ -4071,7 +4360,7 @@ parameter to <tt> const char (&)[4]</tt>, which type is uncopyable.<br> I doubt anyone intended that behavior... </p> <p><b>Proposed resolution:</b></p> -<p>In 20.2 <a href="lib-utilities.html#lib.utility"> [lib.utility]</a>, paragraph 1 change the following +<p>In 20.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.utility"> [lib.utility]</a>, paragraph 1 change the following declaration of make_pair():</p> <blockquote> <pre>template <class T1, class T2> pair<T1,T2> make_pair(const T1&, const T2&);</pre> @@ -4080,7 +4369,7 @@ declaration of make_pair():</p> <blockquote> <pre>template <class T1, class T2> pair<T1,T2> make_pair(T1, T2);</pre> </blockquote> -<p> In 20.2.2 <a href="lib-utilities.html#lib.pairs"> [lib.pairs]</a> paragraph 7 and the line before, change:</p> +<p> In 20.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.pairs"> [lib.pairs]</a> paragraph 7 and the line before, change:</p> <blockquote> <pre>template <class T1, class T2> pair<T1, T2> make_pair(const T1& x, const T2& y);</pre> @@ -4098,7 +4387,7 @@ pair<T1, T2> make_pair(T1 x, T2 y);</pre> </blockquote> <p><b>Rationale:</b></p> <p>Two potential fixes were suggested by Matt Austern and Dietmar -Kühl, respectively, 1) overloading with array arguments, and 2) use of +Kühl, respectively, 1) overloading with array arguments, and 2) use of a reference_traits class with a specialization for arrays. Andy Koenig suggested changing to pass by value. In discussion, it appeared that this was a much smaller change to the standard that the other two @@ -4107,18 +4396,18 @@ advantages of the solution. Two implementors reported that the proposed resolution passed their test suites.</p> <hr> <a name="182"><h3>182. Ambiguous references to size_t</h3></a><p> -<b>Section:</b> 17 <a href="lib-intro.html#lib.library"> [lib.library]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Al Stevens <b>Date:</b> 15 Aug 1999</p> +<b>Section:</b> 17 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.library"> [lib.library]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Al Stevens <b>Date:</b> 15 Aug 1999</p> <p>Many references to <tt> size_t</tt> throughout the document omit the <tt> std::</tt> namespace qualification.</p> <p>For -example, 17.4.3.4 <a href="lib-intro.html#lib.replacement.functions"> [lib.replacement.functions]</a> paragraph 2:</p> +example, 17.4.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.replacement.functions"> [lib.replacement.functions]</a> paragraph 2:</p> <blockquote> -<pre>— operator new(size_t) -— operator new(size_t, const std::nothrow_t&) -— operator new[](size_t) -— operator new[](size_t, const std::nothrow_t&)</pre> +<pre>— operator new(size_t) +— operator new(size_t, const std::nothrow_t&) +— operator new[](size_t) +— operator new[](size_t, const std::nothrow_t&)</pre> </blockquote> <p><b>Proposed resolution:</b></p> -<p> In 17.4.3.4 <a href="lib-intro.html#lib.replacement.functions"> [lib.replacement.functions]</a> paragraph 2: replace:</p> +<p> In 17.4.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.replacement.functions"> [lib.replacement.functions]</a> paragraph 2: replace:</p> <blockquote> <p><tt> - operator new(size_t)<br> - operator new(size_t, const std::nothrow_t&)<br> @@ -4176,12 +4465,13 @@ example, 17.4.3.4 <a href="lib-intro.html#lib.replacement.functions"> [lib.repla pos denotes a value of type X::pos_type; and state denotes a value of type X::state_type.</p> </blockquote> <p>In [lib.char.traits.require] 21.1.1, table 37: replace the return type of -X::length(p): "size_t" by "std::size_t".</p> +X::length(p): "size_t" by "std::size_t".</p> <p> In [lib.std.iterator.tags] 24.3.3, paragraph 2: replace:<br> typedef ptrdiff_t difference_type;<br> by:<br> typedef std::ptrdiff_t difference_type;</p> -<p> In [lib.locale.ctype] 22.2.1.1 put namespace std { ...} around the declaration of template <class charT> class ctype.<br> +<p> In [lib.locale.ctype] 22.2.1.1 put namespace std { ...} around the +declaration of template <class charT> class ctype.<br> <br> In [lib.iterator.traits] 24.3.1, paragraph 2 put namespace std { ...} around the declaration of:<br> <br> @@ -4192,7 +4482,7 @@ X::length(p): "size_t" by "std::size_t".</p> <p>The LWG believes correcting names like <tt>size_t</tt> and <tt>ptrdiff_t</tt> to <tt>std::size_t</tt> and <tt>std::ptrdiff_t</tt> to be essentially editorial. There there can't be another size_t or -ptrdiff_t meant anyway because, according to 17.4.3.1.4 <a href="lib-intro.html#lib.extern.types"> [lib.extern.types]</a>,</p> +ptrdiff_t meant anyway because, according to 17.4.3.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.extern.types"> [lib.extern.types]</a>,</p> <blockquote> For each type T from the Standard C library, the types ::T and std::T @@ -4206,7 +4496,7 @@ Editor's authority to make this change.</p> <p><i>[Post-Tokyo: Nico Josuttis provided the above wording at the request of the LWG.]</i></p> -<p><i>[Toronto: This is tangentially related to issue <a href="lwg-active.html#229">229</a>, but only tangentially: the intent of this issue is to +<p><i>[Toronto: This is tangentially related to issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#229">229</a>, but only tangentially: the intent of this issue is to address use of the name <tt>size_t</tt> in contexts outside of namespace std, such as in the description of <tt>::operator new</tt>. The proposed changes should be reviewed to make sure they are @@ -4217,8 +4507,8 @@ them to be correct.]</i></p> <hr> <a name="183"><h3>183. I/O stream manipulators don't work for wide character streams</h3></a><p> -<b>Section:</b> 27.6.3 <a href="lib-iostreams.html#lib.std.manip"> [lib.std.manip]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 7 Jul 1999</p> -<p>27.6.3 <a href="lib-iostreams.html#lib.std.manip"> [lib.std.manip]</a> paragraph 3 says (clause numbering added for +<b>Section:</b> 27.6.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.std.manip"> [lib.std.manip]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 7 Jul 1999</p> +<p>27.6.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.std.manip"> [lib.std.manip]</a> paragraph 3 says (clause numbering added for exposition):</p> <blockquote> <p>Returns: An object s of unspecified type such that if [1] out is an (instance @@ -4231,36 +4521,46 @@ out<<s has type ostream& and value out. [4] The expression in>>s has type istream& and value in.</p> </blockquote> <p>Given the definitions [1] and [2] for out and in, surely [3] should read: -"The expression out << s has type basic_ostream& ..." and -[4] should read: "The expression in >> s has type basic_istream& -..."</p> +"The expression out << s has type basic_ostream& ..." and +[4] should read: "The expression in >> s has type basic_istream& +..."</p> <p>If the wording in the standard is correct, I can see no way of implementing any of the manipulators so that they will work with wide character streams.</p> <p>e.g. wcout << setbase( 16 );</p> <p>Must have value 'wcout' (which makes sense) and type 'ostream&' (which doesn't).</p> -<p>The same "cut'n'paste" type also seems to occur in Paras 4,5,7 and +<p>The same "cut'n'paste" type also seems to occur in Paras 4,5,7 and 8. In addition, Para 6 [setfill] has a similar error, but relates only to ostreams.</p> <p>I'd be happier if there was a better way of saying this, to make it clear -that the value of the expression is "the same specialization of -basic_ostream as out"&</p> +that the value of the expression is "the same specialization of +basic_ostream as out"&</p> <p><b>Proposed resolution:</b></p> -<p>Replace section 27.6.3 <a href="lib-iostreams.html#lib.std.manip"> [lib.std.manip]</a> except paragraph 1 with the +<p>Replace section 27.6.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.std.manip"> [lib.std.manip]</a> except paragraph 1 with the following:</p> <blockquote> -<p>2- The type designated smanip in each of the following function descriptions is implementation-specified and may be different for each +<p>2- The type designated smanip in each of the following function +descriptions is implementation-specified and may be different for each function.<br> <br> <tt>smanip resetiosflags(ios_base::fmtflags mask);</tt><br> <br> --3- Returns: An object s of unspecified type such that if out is an instance of basic_ostream<charT,traits> then the expression out<<s behaves -as if f(s, mask) were called, or if in is an instance of basic_istream<charT,traits> then the expression in>>s behaves as if +-3- Returns: An object s of unspecified type such that if out is an +instance of basic_ostream<charT,traits> then the expression +out<<s behaves +as if f(s, mask) were called, or if in is an instance of +basic_istream<charT,traits> then the expression in>>s +behaves as if f(s, mask) were called. The function f can be defined as:*<br> <br> -[Footnote: The expression cin >> resetiosflags(ios_base::skipws) clears ios_base::skipws in the format flags stored in the -basic_istream<charT,traits> object cin (the same as cin >> noskipws), and the expression cout << resetiosflags(ios_base::showbase) clears -ios_base::showbase in the format flags stored in the basic_ostream<charT,traits> object cout (the same as cout << +[Footnote: The expression cin >> resetiosflags(ios_base::skipws) +clears ios_base::skipws in the format flags stored in the +basic_istream<charT,traits> object cin (the same as cin >> +noskipws), and the expression cout << +resetiosflags(ios_base::showbase) clears +ios_base::showbase in the format flags stored in the +basic_ostream<charT,traits> object cout (the same as cout +<< noshowbase). --- end footnote]<br> <br> <tt>ios_base& f(ios_base& str, ios_base::fmtflags mask)<br> @@ -4275,8 +4575,12 @@ The expression in>>s has type basic_istream<charT,traits>& and v <br> <tt>smanip setiosflags(ios_base::fmtflags mask);</tt><br> <br> --4- Returns: An object s of unspecified type such that if out is an instance of basic_ostream<charT,traits> then the expression out<<s behaves -as if f(s, mask) were called, or if in is an instance of basic_istream<charT,traits> then the expression in>>s behaves as if f(s, +-4- Returns: An object s of unspecified type such that if out is an +instance of basic_ostream<charT,traits> then the expression +out<<s behaves +as if f(s, mask) were called, or if in is an instance of +basic_istream<charT,traits> then the expression in>>s +behaves as if f(s, mask) were called. The function f can be defined as:<br> <br> <tt>ios_base& f(ios_base& str, ios_base::fmtflags mask)<br> @@ -4291,8 +4595,12 @@ The expression in>>s has type basic_istream<charT,traits>& and v <br> <tt>smanip setbase(int base);</tt><br> <br> --5- Returns: An object s of unspecified type such that if out is an instance of basic_ostream<charT,traits> then the expression out<<s behaves -as if f(s, base) were called, or if in is an instance of basic_istream<charT,traits> then the expression in>>s behaves as if f(s, +-5- Returns: An object s of unspecified type such that if out is an +instance of basic_ostream<charT,traits> then the expression +out<<s behaves +as if f(s, base) were called, or if in is an instance of +basic_istream<charT,traits> then the expression in>>s +behaves as if f(s, base) were called. The function f can be defined as:<br> <br> <tt>ios_base& f(ios_base& str, int base)<br> @@ -4310,8 +4618,11 @@ The expression in>>s has type basic_istream<charT,traits>& and v <br> <tt>smanip setfill(char_type c);<br> </tt><br> --6- Returns: An object s of unspecified type such that if out is (or is derived from) basic_ostream<charT,traits> and c has type charT then the -expression out<<s behaves as if f(s, c) were called. The function f can be +-6- Returns: An object s of unspecified type such that if out is (or is +derived from) basic_ostream<charT,traits> and c has type charT +then the +expression out<<s behaves as if f(s, c) were called. The function +f can be defined as:<br> <br> <tt>template<class charT, class traits><br> @@ -4326,8 +4637,12 @@ The expression out<<s has type basic_ostream<charT,traits>& and <br> <tt>smanip setprecision(int n);</tt><br> <br> --7- Returns: An object s of unspecified type such that if out is an instance of basic_ostream<charT,traits> then the expression out<<s behaves -as if f(s, n) were called, or if in is an instance of basic_istream<charT,traits> then the expression in>>s behaves as if f(s, n) +-7- Returns: An object s of unspecified type such that if out is an +instance of basic_ostream<charT,traits> then the expression +out<<s behaves +as if f(s, n) were called, or if in is an instance of +basic_istream<charT,traits> then the expression in>>s +behaves as if f(s, n) were called. The function f can be defined as:<br> <br> <tt>ios_base& f(ios_base& str, int n)<br> @@ -4342,8 +4657,12 @@ The expression in>>s has type basic_istream<charT,traits>& and v .<br> <tt>smanip setw(int n);<br> </tt><br> --8- Returns: An object s of unspecified type such that if out is an instance of basic_ostream<charT,traits> then the expression out<<s behaves -as if f(s, n) were called, or if in is an instance of basic_istream<charT,traits> then the expression in>>s behaves as if f(s, n) +-8- Returns: An object s of unspecified type such that if out is an +instance of basic_ostream<charT,traits> then the expression +out<<s behaves +as if f(s, n) were called, or if in is an instance of +basic_istream<charT,traits> then the expression in>>s +behaves as if f(s, n) were called. The function f can be defined as:<br> <br> <tt>ios_base& f(ios_base& str, int n)<br> @@ -4363,20 +4682,20 @@ in. <p><i>[Kona: Andy Sawyer and Beman Dawes will work to improve the wording of the proposed resolution.]</i></p> -<p><i>[Tokyo - The LWG noted that issue <a href="lwg-closed.html#216">216</a> involves +<p><i>[Tokyo - The LWG noted that issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#216">216</a> involves the same paragraphs.]</i></p> <p><i>[Post-Tokyo: The issues list maintainer combined the proposed -resolution of this issue with the proposed resolution for issue <a href="lwg-closed.html#216">216</a> as they both involved the same paragraphs, and were so +resolution of this issue with the proposed resolution for issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#216">216</a> as they both involved the same paragraphs, and were so intertwined that dealing with them separately appear fraught with error. The full text was supplied by Bill Plauger; it was cross checked against changes supplied by Andy Sawyer. It should be further checked by the LWG.]</i></p> <hr> <a name="184"><h3>184. numeric_limits<bool> wording problems</h3></a><p> -<b>Section:</b> 18.2.1.5 <a href="lib-support.html#lib.numeric.special"> [lib.numeric.special]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Gabriel Dos Reis <b>Date:</b> 21 Jul 1999</p> +<b>Section:</b> 18.2.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.numeric.special"> [lib.numeric.special]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Gabriel Dos Reis <b>Date:</b> 21 Jul 1999</p> <p>bools are defined by the standard to be of integer types, as per -3.9.1 <a href="basic.html#basic.fundamental"> [basic.fundamental]</a> paragraph 7. However "integer types" +3.9.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/basic.html#basic.fundamental"> [basic.fundamental]</a> paragraph 7. However "integer types" seems to have a special meaning for the author of 18.2. The net effect is an unclear and confusing specification for numeric_limits<bool> as evidenced below.</p> @@ -4404,17 +4723,17 @@ to be meaningful.</p> </blockquote> <p>This disposition is at best misleading and confusing for the standard -requires a "pure binary numeration system" for integer types as per +requires a "pure binary numeration system" for integer types as per 3.9.1/7</p> -<p>The footnote 186) says: "Distinguishes types with base other than 2 (e.g -BCD)." This also erroneous as the standard never defines any integer +<p>The footnote 186) says: "Distinguishes types with base other than 2 (e.g +BCD)." This also erroneous as the standard never defines any integer types with base representation other than 2.</p> <p>Furthermore, numeric_limits<bool>::is_modulo and numeric_limits<bool>::is_signed have similar problems.</p> <p><b>Proposed resolution:</b></p> -<p>Append to the end of 18.2.1.5 <a href="lib-support.html#lib.numeric.special"> [lib.numeric.special]</a>:</p> +<p>Append to the end of 18.2.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.numeric.special"> [lib.numeric.special]</a>:</p> <blockquote> <p>The specialization for bool shall be provided as follows:</p> <pre> namespace std { @@ -4466,17 +4785,17 @@ resolution.]</i></p> <p><i>[Post-Tokyo: At the request of the LWG in Tokyo, Nico Josuttis provided the above wording.]</i></p> <hr> -<a name="185"><h3>185. Questionable use of term "inline"</h3></a><p> -<b>Section:</b> 20.3 <a href="lib-utilities.html#lib.function.objects"> [lib.function.objects]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> UK Panel <b>Date:</b> 26 Jul 1999</p> -<p>Paragraph 4 of 20.3 <a href="lib-utilities.html#lib.function.objects"> [lib.function.objects]</a> says:</p> +<a name="185"><h3>185. Questionable use of term "inline"</h3></a><p> +<b>Section:</b> 20.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.function.objects"> [lib.function.objects]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> UK Panel <b>Date:</b> 26 Jul 1999</p> +<p>Paragraph 4 of 20.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.function.objects"> [lib.function.objects]</a> says:</p> <blockquote> <p> [Example: To negate every element of a: transform(a.begin(), a.end(), a.begin(), negate<double>()); The corresponding functions will inline the addition and the negation. end example]</p> </blockquote> -<p>(Note: The "addition" referred to in the above is in para 3) we can +<p>(Note: The "addition" referred to in the above is in para 3) we can find no other wording, except this (non-normative) example which suggests that -any "inlining" will take place in this case.</p> +any "inlining" will take place in this case.</p> <p>Indeed both:</p> <blockquote> <p>17.4.4.3 Global Functions [lib.global.functions] 1 It is @@ -4490,20 +4809,20 @@ any "inlining" will take place in this case.</p> are defined as inline (7.1.2).</p> </blockquote> <p>take care to state that this may indeed NOT be the case.</p> -<p>Thus the example "mandates" behavior that is explicitly +<p>Thus the example "mandates" behavior that is explicitly not required elsewhere.</p> <p><b>Proposed resolution:</b></p> -<p>In 20.3 <a href="lib-utilities.html#lib.function.objects"> [lib.function.objects]</a> paragraph 1, remove the sentence:</p> +<p>In 20.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.function.objects"> [lib.function.objects]</a> paragraph 1, remove the sentence:</p> <blockquote> <p>They are important for the effective use of the library.</p> </blockquote> -<p>Remove 20.3 <a href="lib-utilities.html#lib.function.objects"> [lib.function.objects]</a> paragraph 2, which reads:</p> +<p>Remove 20.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.function.objects"> [lib.function.objects]</a> paragraph 2, which reads:</p> <blockquote> <p> Using function objects together with function templates increases the expressive power of the library as well as making the resulting code much more efficient.</p> </blockquote> -<p>In 20.3 <a href="lib-utilities.html#lib.function.objects"> [lib.function.objects]</a> paragraph 4, remove the sentence:</p> +<p>In 20.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.function.objects"> [lib.function.objects]</a> paragraph 4, remove the sentence:</p> <blockquote> <p>The corresponding functions will inline the addition and the negation.</p> @@ -4513,8 +4832,8 @@ not required elsewhere.</p> <p><i>[Tokyo: The LWG crafted the proposed resolution.]</i></p> <hr> <a name="186"><h3>186. bitset::set() second parameter should be bool</h3></a><p> -<b>Section:</b> 23.3.5.2 <a href="lib-containers.html#lib.bitset.members"> [lib.bitset.members]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Darin Adler <b>Date:</b> 13 Aug 1999</p> -<p>In section 23.3.5.2 <a href="lib-containers.html#lib.bitset.members"> [lib.bitset.members]</a>, paragraph 13 defines the +<b>Section:</b> 23.3.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.bitset.members"> [lib.bitset.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Darin Adler <b>Date:</b> 13 Aug 1999</p> +<p>In section 23.3.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.bitset.members"> [lib.bitset.members]</a>, paragraph 13 defines the bitset::set operation to take a second parameter of type int. The function tests whether this value is non-zero to determine whether to set the bit to true or false. The type of this second parameter should @@ -4524,7 +4843,7 @@ possible to slice an integer that's larger than an int. This can't happen with bool, since conversion to bool has the semantic of translating 0 to false and any non-zero value to true.</p> <p><b>Proposed resolution:</b></p> -<p>In 23.3.5 <a href="lib-containers.html#lib.template.bitset"> [lib.template.bitset]</a> Para 1 Replace:</p> +<p>In 23.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.template.bitset"> [lib.template.bitset]</a> Para 1 Replace:</p> <blockquote> <pre>bitset<N>& set(size_t pos, int val = true ); </pre> </blockquote> @@ -4532,7 +4851,7 @@ translating 0 to false and any non-zero value to true.</p> <blockquote> <pre>bitset<N>& set(size_t pos, bool val = true );</pre> </blockquote> -<p>In 23.3.5.2 <a href="lib-containers.html#lib.bitset.members"> [lib.bitset.members]</a> Para 12(.5) Replace:</p> +<p>In 23.3.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.bitset.members"> [lib.bitset.members]</a> Para 12(.5) Replace:</p> <blockquote> <pre>bitset<N>& set(size_t pos, int val = 1 );</pre> </blockquote> @@ -4552,8 +4871,66 @@ usually implemented as <tt>inline</tt>, and because it is already the case that users cannot rely on the type of a pointer to a nonvirtual member of a standard library class.</p> <hr> +<a name="187"><h3>187. iter_swap underspecified</h3></a><p> +<b>Section:</b> 25.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.swap"> [lib.alg.swap]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 14 Aug 1999</p> +<p>The description of iter_swap in 25.2.2 paragraph 7,says that it +``exchanges the values'' of the objects to which two iterators +refer.<br> <br> What it doesn't say is whether it does so using swap +or using the assignment operator and copy constructor.<br> <br> This +question is an important one to answer, because swap is specialized to +work efficiently for standard containers.<br> For example:</p> +<blockquote> +<pre>vector<int> v1, v2; +iter_swap(&v1, &v2);</pre> +</blockquote> +<p>Is this call to iter_swap equivalent to calling swap(v1, v2)? +Or is it equivalent to</p> +<blockquote> +<pre>{ +vector<int> temp = v1; +v1 = v2; +v2 = temp; +}</pre> +</blockquote> +<p>The first alternative is O(1); the second is O(n).</p> +<p>A LWG member, Dave Abrahams, comments:</p> +<blockquote> +<p>Not an objection necessarily, but I want to point out the cost of +that requirement:</p> + <blockquote> +<p><tt>iter_swap(list<T>::iterator, list<T>::iterator)</tt></p> + </blockquote> +<p>can currently be specialized to be more efficient than +iter_swap(T*,T*) for many T (by using splicing). Your proposal would +make that optimization illegal. </p> +</blockquote> + +<p><i>[Kona: The LWG notes the original need for iter_swap was proxy iterators +which are no longer permitted.]</i></p> +<p><b>Proposed resolution:</b></p> +<p>Change the effect clause of iter_swap in 25.2.2 paragraph 7 from:</p> +<blockquote> +<p>Exchanges the values pointed to by the two iterators a and b.</p> +</blockquote> +<p>to</p> +<blockquote> +<p> +<tt>swap(*a, *b)</tt>.</p> +</blockquote> + +<p><b>Rationale:</b></p> +<p>It's useful to say just what <tt>iter_swap</tt> does. There may be + some iterators for which we want to specialize <tt>iter_swap</tt>, + but the fully general version should have a general specification.</p> + +<p>Note that in the specific case of <tt>list<T>::iterator</tt>, +iter_swap should not be specialized as suggested above. That would do +much more than exchanging the two iterators' values: it would change +predecessor/successor relationships, possibly moving the iterator from +one list to another. That would surely be inappropriate.</p> +<hr> <a name="189"><h3>189. setprecision() not specified correctly</h3></a><p> -<b>Section:</b> 27.4.2.2 <a href="lib-iostreams.html#lib.fmtflags.state"> [lib.fmtflags.state]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 25 Aug 1999</p> +<b>Section:</b> 27.4.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.fmtflags.state"> [lib.fmtflags.state]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 25 Aug 1999</p> <p>27.4.2.2 paragraph 9 claims that setprecision() sets the precision, and includes a parenthetical note saying that it is the number of digits after the decimal point.<br> @@ -4566,27 +4943,30 @@ point.<br> I would like the committee to look at the definition carefully and correct the statement in 27.4.2.2</p> <p><b>Proposed resolution:</b></p> -<p>Remove from 27.4.2.2 <a href="lib-iostreams.html#lib.fmtflags.state"> [lib.fmtflags.state]</a>, paragraph 9, the text -"(number of digits after the decimal point)".</p> +<p>Remove from 27.4.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.fmtflags.state"> [lib.fmtflags.state]</a>, paragraph 9, the text +"(number of digits after the decimal point)".</p> <hr> <a name="193"><h3>193. Heap operations description incorrect</h3></a><p> -<b>Section:</b> 25.3.6 <a href="lib-algorithms.html#lib.alg.heap.operations"> [lib.alg.heap.operations]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Markus Mauhart <b>Date:</b> 24 Sep 1999</p> +<b>Section:</b> 25.3.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.heap.operations"> [lib.alg.heap.operations]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Markus Mauhart <b>Date:</b> 24 Sep 1999</p> <p>25.3.6 [lib.alg.heap.operations] states two key properties of a heap [a,b), the first of them is<br> <br> - `"(1) *a is the largest element"<br> + `"(1) *a is the largest element"<br> <br> I think this is incorrect and should be changed to the wording in the proposed resolution.</p> <p>Actually there are two independent changes:</p> <blockquote> - <p>A-"part of largest equivalence class" instead of "largest", cause 25.3 - [lib.alg.sorting] asserts "strict weak ordering" for all its sub clauses.</p> - <p>B-Take 'an oldest' from that equivalence class, otherwise the heap functions could not be used for a - priority queue as explained in 23.2.3.2.2 [lib.priqueue.members] (where I assume that a "priority queue" respects priority AND time).</p> + <p>A-"part of largest equivalence class" instead of "largest", cause 25.3 + [lib.alg.sorting] asserts "strict weak ordering" for all its sub clauses.</p> + <p>B-Take +'an oldest' from that equivalence class, otherwise the heap functions +could not be used for a priority queue as explained in 23.2.3.2.2 +[lib.priqueue.members] (where I assume that a "priority queue" respects +priority AND time).</p> </blockquote> <p><b>Proposed resolution:</b></p> -<p>Change 25.3.6 <a href="lib-algorithms.html#lib.alg.heap.operations"> [lib.alg.heap.operations]</a> property (1) from:</p> +<p>Change 25.3.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.heap.operations"> [lib.alg.heap.operations]</a> property (1) from:</p> <blockquote> <p>(1) *a is the largest element</p> </blockquote> @@ -4597,20 +4977,20 @@ resolution.</p> </blockquote> <hr> <a name="195"><h3>195. Should <tt>basic_istream::sentry</tt>'s constructor ever set eofbit?</h3></a><p> -<b>Section:</b> 27.6.1.1.2 <a href="lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 13 Oct 1999</p> +<b>Section:</b> 27.6.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 13 Oct 1999</p> <p>Suppose that <tt>is.flags() & ios_base::skipws</tt> is nonzero. What should <tt>basic_istream<>::sentry</tt>'s constructor do if it reaches eof while skipping whitespace? 27.6.1.1.2/5 suggests it should set failbit. Should it set eofbit as well? The standard doesn't seem to answer that question.</p> -<p>On the one hand, nothing in 27.6.1.1.2 <a href="lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a> says that +<p>On the one hand, nothing in 27.6.1.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream::sentry"> [lib.istream::sentry]</a> says that <tt>basic_istream<>::sentry</tt> should ever set eofbit. On the -other hand, 27.6.1.1 <a href="lib-iostreams.html#lib.istream"> [lib.istream]</a> paragraph 4 says that if -extraction from a <tt>streambuf</tt> "returns +other hand, 27.6.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream"> [lib.istream]</a> paragraph 4 says that if +extraction from a <tt>streambuf</tt> "returns <tt>traits::eof()</tt>, then the input function, except as explicitly noted otherwise, completes its actions and does -<tt>setstate(eofbit)"</tt>. So the question comes down to +<tt>setstate(eofbit)"</tt>. So the question comes down to whether <tt>basic_istream<>::sentry</tt>'s constructor is an input function.</p> @@ -4626,12 +5006,12 @@ signaled eof.</p> <p> The classic case is a streambuf reading from a UNIX file. EOF isn't really a state for UNIX file descriptors. The convention is that a -read on UNIX returns 0 bytes to indicate "EOF", but the file +read on UNIX returns 0 bytes to indicate "EOF", but the file descriptor isn't shut down in any way and future reads do not necessarily also return 0 bytes. In particular, you can read from -tty's on UNIX even after they have signaled "EOF". (It +tty's on UNIX even after they have signaled "EOF". (It isn't always understood that a ^D on UNIX is not an EOF indicator, but -an EOL indicator. By typing a "line" consisting solely of +an EOL indicator. By typing a "line" consisting solely of ^D you cause a read to return 0 bytes, and by convention this is interpreted as end of file.)</p> </blockquote> @@ -4646,7 +5026,7 @@ returns <tt>traits::eof()</tt>, the function calls </blockquote> <hr> <a name="198"><h3>198. Validity of pointers and references unspecified after iterator destruction</h3></a><p> -<b>Section:</b> 24.1 <a href="lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 3 Nov 1999</p> +<b>Section:</b> 24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 3 Nov 1999</p> <p> Is a pointer or reference obtained from an iterator still valid after destruction of the iterator? @@ -4656,8 +5036,7 @@ Is a pointer or reference obtained from an iterator still valid after the value of the iterator changes? </p> <blockquote> -<pre> -#include <iostream> +<pre>#include <iostream> #include <vector> #include <iterator> @@ -4694,14 +5073,14 @@ elements of containers.</p> <p>The standard itself assumes that pointers and references obtained from an iterator are still valid after iterator destruction or -change. The definition of reverse_iterator::operator*(), 24.4.1.3.3 <a href="lib-iterators.html#lib.reverse.iter.op.star"> [lib.reverse.iter.op.star]</a>, which returns a reference, defines +change. The definition of reverse_iterator::operator*(), 24.4.1.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.reverse.iter.op.star"> [lib.reverse.iter.op.star]</a>, which returns a reference, defines effects:</p> <blockquote> <pre>Iterator tmp = current; return *--tmp;</pre> </blockquote> -<p>The definition of reverse_iterator::operator->(), 24.4.1.3.4 <a href="lib-iterators.html#lib.reverse.iter.opref"> [lib.reverse.iter.opref]</a>, which returns a pointer, defines effects:</p> +<p>The definition of reverse_iterator::operator->(), 24.4.1.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.reverse.iter.opref"> [lib.reverse.iter.opref]</a>, which returns a pointer, defines effects:</p> <blockquote> <pre>return &(operator*());</pre> </blockquote> @@ -4712,18 +5091,17 @@ explicitly. This will also reduce the chance of user code breaking unexpectedly when porting to a different standard library implementation.</p> <p><b>Proposed resolution:</b></p> -<p>Add a new paragraph to 24.1 <a href="lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a>:</p> +<p>Add a new paragraph to 24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a>:</p> <blockquote> Destruction of an iterator may invalidate pointers and references previously obtained from that iterator. </blockquote> -<p>Replace paragraph 1 of 24.4.1.3.3 <a href="lib-iterators.html#lib.reverse.iter.op.star"> [lib.reverse.iter.op.star]</a> with:</p> +<p>Replace paragraph 1 of 24.4.1.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.reverse.iter.op.star"> [lib.reverse.iter.op.star]</a> with:</p> <blockquote> <p><b>Effects:</b></p> -<pre> - this->tmp = current; +<pre> this->tmp = current; --this->tmp; return *this->tmp; </pre> @@ -4732,7 +5110,7 @@ previously obtained from that iterator. [<i>Note:</i> This operation must use an auxiliary member variable, rather than a temporary variable, to avoid returning a reference that persists beyond the lifetime of its associated iterator. (See -24.1 <a href="lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a>.) The name of this member variable is shown for +24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a>.) The name of this member variable is shown for exposition only. <i>--end note</i>] </p> </blockquote> @@ -4748,7 +5126,7 @@ reformulated yet again to reflect this reality.]</i></p> assumes its underlying iterator has persistent pointers and references. Andy Koenig pointed out that it is possible to rewrite reverse_iterator so that it no longer makes such an assupmption. -However, this issue is related to issue <a href="lwg-active.html#299">299</a>. If we +However, this issue is related to issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#299">299</a>. If we decide it is intentional that <tt>p[n]</tt> may return by value instead of reference when <tt>p</tt> is a Random Access Iterator, other changes in reverse_iterator will be necessary.]</i></p> @@ -4758,7 +5136,7 @@ other changes in reverse_iterator will be necessary.]</i></p> asking whether or not user-defined iterators are permitted to have transient pointers and references. Several people presented examples of useful user-defined iterators that have such a property; examples -include a B-tree iterator, and an "iota iterator" that doesn't point +include a B-tree iterator, and an "iota iterator" that doesn't point to memory. Library implementors already seem to be able to cope with such iterators: they take pains to avoid forming references to memory that gets iterated past. The only place where this is a problem is @@ -4772,7 +5150,7 @@ predefined iterators are as strong as users expect.</p> <hr> <a name="199"><h3>199. What does <tt>allocate(0)</tt> return?</h3></a><p> -<b>Section:</b> 20.1.5 <a href="lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 19 Nov 1999</p> +<b>Section:</b> 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 19 Nov 1999</p> <p> Suppose that <tt>A</tt> is a class that conforms to the Allocator requirements of Table 32, and <tt>a</tt> is an @@ -4785,7 +5163,7 @@ unique non-null pointer. <p><b>Proposed resolution:</b></p> <p> Add a note to the <tt>allocate</tt> row of Table 32: -"[<i>Note:</i> If <tt>n == 0</tt>, the return value is unspecified. <i>--end note</i>]"</p> +"[<i>Note:</i> If <tt>n == 0</tt>, the return value is unspecified. <i>--end note</i>]"</p> <p><b>Rationale:</b></p> <p>A key to understanding this issue is that the ultimate use of allocate() is to construct an iterator, and that iterator for zero @@ -4794,20 +5172,175 @@ representation. Since this already implies special case code, it would be over-specification to mandate the return value. </p> <hr> +<a name="200"><h3>200. Forward iterator requirements don't allow constant iterators</h3></a><p> +<b>Section:</b> 24.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.forward.iterators"> [lib.forward.iterators]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 19 Nov 1999</p> +<p> +In table 74, the return type of the expression <tt>*a</tt> is given +as <tt>T&</tt>, where <tt>T</tt> is the iterator's value type. +For constant iterators, however, this is wrong. ("Value type" +is never defined very precisely, but it is clear that the value type +of, say, <tt>std::list<int>::const_iterator</tt> is supposed to be +<tt>int</tt>, not <tt>const int</tt>.) +</p> +<p><b>Proposed resolution:</b></p> +<p> +In table 74, in the <tt>*a</tt> and <tt>*r++</tt> rows, change the +return type from "<tt>T&</tt>" to "<tt>T&</tt> +if <tt>X</tt> is mutable, otherwise <tt>const T&</tt>". +In the <tt>a->m</tt> row, change the return type from +"<tt>U&</tt>" to "<tt>U&</tt> if <tt>X</tt> is mutable, +otherwise <tt>const U&</tt>". +</p> + +<p><i>[Tokyo: The LWG believes this is the tip of a larger iceberg; +there are multiple const problems with the STL portion of the library +and that these should be addressed as a single package. Note +that issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#180">180</a> has already been declared NAD Future for +that very reason.]</i></p> + +<p><i>[Redmond: the LWG thinks this is separable from other constness +issues. This issue is just cleanup; it clarifies language that was +written before we had iterator_traits. Proposed resolution was +modified: the original version only discussed *a. It was pointed out +that we also need to worry about *r++ and a->m.]</i></p> + +<hr> +<a name="202"><h3>202. unique() effects unclear when predicate not an equivalence relation</h3></a><p> +<b>Section:</b> 25.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Andrew Koenig <b>Date:</b> 13 Jan 2000</p> +<p> +What should unique() do if you give it a predicate that is not an +equivalence relation? There are at least two plausible answers: +</p> + +<blockquote> + +<p> + 1. You can't, because 25.2.8 says that it it "eliminates all but + the first element from every consecutive group of equal + elements..." and it wouldn't make sense to interpret "equal" as + meaning anything but an equivalence relation. [It also doesn't + make sense to interpret "equal" as meaning ==, because then there + would never be any sense in giving a predicate as an argument at + all.] +</p> + +<p> + 2. The word "equal" should be interpreted to mean whatever the + predicate says, even if it is not an equivalence relation + (and in particular, even if it is not transitive). +</p> + +</blockquote> + +<p> +The example that raised this question is from Usenet: +</p> + +<blockquote> + +<pre>int f[] = { 1, 3, 7, 1, 2 }; +int* z = unique(f, f+5, greater<int>());</pre> + +</blockquote> + +<p> +If one blindly applies the definition using the predicate +greater<int>, and ignore the word "equal", you get: +</p> + +<blockquote> + +<p> + Eliminates all but the first element from every consecutive group + of elements referred to by the iterator i in the range [first, last) + for which *i > *(i - 1). +</p> + +</blockquote> + +<p> +The first surprise is the order of the comparison. If we wanted to +allow for the predicate not being an equivalence relation, then we +should surely compare elements the other way: pred(*(i - 1), *i). If +we do that, then the description would seem to say: "Break the +sequence into subsequences whose elements are in strictly increasing +order, and keep only the first element of each subsequence". So the +result would be 1, 1, 2. If we take the description at its word, it +would seem to call for strictly DEcreasing order, in which case the +result should be 1, 3, 7, 2.<br> +<br> +In fact, the SGI implementation of unique() does neither: It yields 1, +3, 7. +</p> +<p><b>Proposed resolution:</b></p> +<p>Change 25.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> paragraph 1 to:</p> +<blockquote> +For a nonempty range, eliminates all but the first element from every +consecutive group of equivalent elements referred to by the iterator +<tt>i</tt> in the range [first+1, last) for which the following +conditions hold: <tt>*(i-1) == *i</tt> or <tt>pred(*(i-1), *i) != +false</tt>. +</blockquote> + +<p> +Also insert a new paragraph, paragraph 2a, that reads: "Requires: The +comparison function must be an equivalence relation." +</p> + +<p><i>[Redmond: discussed arguments for and against requiring the +comparison function to be an equivalence relation. Straw poll: +14-2-5. First number is to require that it be an equivalence +relation, second number is to explicitly not require that it be an +equivalence relation, third number is people who believe they need +more time to consider the issue. A separate issue: Andy Sawyer +pointed out that "i-1" is incorrect, since "i" can refer to the first +iterator in the range. Matt provided wording to address this +problem.]</i></p> + +<p><i>[Curaçao: The LWG changed "... the range (first, +last)..." to "... the range [first+1, last)..." for +clarity. They considered this change close enough to editorial to not +require another round of review.]</i></p> + +<p><b>Rationale:</b></p> +<p>The LWG also considered an alternative resolution: change +25.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> paragraph 1 to:</p> + +<blockquote> +For a nonempty range, eliminates all but the first element from every +consecutive group of elements referred to by the iterator +<tt>i</tt> in the range (first, last) for which the following +conditions hold: <tt>*(i-1) == *i</tt> or <tt>pred(*(i-1), *i) != +false</tt>. +</blockquote> + +<p> +Also insert a new paragraph, paragraph 1a, that reads: "Notes: The +comparison function need not be an equivalence relation." +</p> + + +<p>Informally: the proposed resolution imposes an explicit requirement +that the comparison function be an equivalence relation. The +alternative resolution does not, and it gives enough information so +that the behavior of unique() for a non-equivalence relation is +specified. Both resolutions are consistent with the behavior of +existing implementations.</p> +<hr> <a name="208"><h3>208. Unnecessary restriction on past-the-end iterators</h3></a><p> -<b>Section:</b> 24.1 <a href="lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Stephen Cleary <b>Date:</b> 02 Feb 2000</p> -<p>In 24.1 paragraph 5, it is stated ". . . Dereferenceable and -past-the-end values are always non-singular."</p> +<b>Section:</b> 24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Stephen Cleary <b>Date:</b> 02 Feb 2000</p> +<p>In 24.1 paragraph 5, it is stated ". . . Dereferenceable and +past-the-end values are always non-singular."</p> <p>This places an unnecessary restriction on past-the-end iterators for containers with forward iterators (for example, a singly-linked list). If the past-the-end value on such a container was a well-known singular value, it would still satisfy all forward iterator requirements.</p> <p>Removing this restriction would allow, for example, a singly-linked list -without a "footer" node.</p> +without a "footer" node.</p> <p>This would have an impact on existing code that expects past-the-end iterators obtained from different (generic) containers being not equal.</p> <p><b>Proposed resolution:</b></p> -<p>Change 24.1 <a href="lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> paragraph 5, the last sentence, from:</p> +<p>Change 24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> paragraph 5, the last sentence, from:</p> <blockquote> <p>Dereferenceable and past-the-end values are always non-singular.</p> </blockquote> @@ -4822,8 +5355,8 @@ iterators. Null pointers are singular. </p> <hr> <a name="209"><h3>209. basic_string declarations inconsistent</h3></a><p> -<b>Section:</b> 21.3 <a href="lib-strings.html#lib.basic.string"> [lib.basic.string]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Igor Stauder <b>Date:</b> 11 Feb 2000</p> -<p>In Section 21.3 <a href="lib-strings.html#lib.basic.string"> [lib.basic.string]</a> the basic_string member function +<b>Section:</b> 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Igor Stauder <b>Date:</b> 11 Feb 2000</p> +<p>In Section 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a> the basic_string member function declarations use a consistent style except for the following functions:</p> <blockquote> <pre>void push_back(const charT); @@ -4836,7 +5369,7 @@ not by reference - should be charT or const charT& )<br> - swap: redundant use of template parameters in argument basic_string<charT,traits,Allocator>&</p> <p><b>Proposed resolution:</b></p> -<p>In Section 21.3 <a href="lib-strings.html#lib.basic.string"> [lib.basic.string]</a> change the basic_string member +<p>In Section 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a> change the basic_string member function declarations push_back, assign, and swap to:</p> <blockquote> <pre>void push_back(charT c); @@ -4852,8 +5385,8 @@ change. </p> <hr> <a name="210"><h3>210. distance first and last confused</h3></a><p> -<b>Section:</b> 25 <a href="lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Lisa Lippincott <b>Date:</b> 15 Feb 2000</p> -<p>In paragraph 9 of section 25 <a href="lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a>, it is written:</p> +<b>Section:</b> 25 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Lisa Lippincott <b>Date:</b> 15 Feb 2000</p> +<p>In paragraph 9 of section 25 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a>, it is written:</p> <blockquote> <p> In the description of the algorithms operators + and - are used for some of the iterator categories for which they do not have to @@ -4864,8 +5397,8 @@ change. </p> </blockquote> <p><b>Proposed resolution:</b></p> -<p>On the last line of paragraph 9 of section 25 <a href="lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a> change -<tt>"a-b"</tt> to <tt>"b-a".</tt> +<p>On the last line of paragraph 9 of section 25 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.algorithms"> [lib.algorithms]</a> change +<tt>"a-b"</tt> to <tt>"b-a".</tt> </p> <p><b>Rationale:</b></p> <p>There are two ways to fix the defect; change the description to b-a @@ -4873,7 +5406,7 @@ or change the return to distance(b,a). The LWG preferred the former for consistency.</p> <hr> <a name="211"><h3>211. operator>>(istream&, string&) doesn't set failbit</h3></a><p> -<b>Section:</b> 21.3.7.9 <a href="lib-strings.html#lib.string.io"> [lib.string.io]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Scott Snyder <b>Date:</b> 4 Feb 2000</p> +<b>Section:</b> 21.3.7.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.io"> [lib.string.io]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Scott Snyder <b>Date:</b> 4 Feb 2000</p> <p>The description of the stream extraction operator for std::string (section 21.3.7.9 [lib.string.io]) does not contain a requirement that failbit be set in the case that the operator fails to extract any characters from the input @@ -4887,12 +5420,12 @@ while (is >> str) ... ;</pre> </blockquote> <p>(which tests failbit) is not required to terminate at EOF.</p> <p>Furthermore, this is inconsistent with other extraction operators, -which do include this requirement. (See sections 27.6.1.2 <a href="lib-iostreams.html#lib.istream.formatted"> [lib.istream.formatted]</a> and 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>), where this +which do include this requirement. (See sections 27.6.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted"> [lib.istream.formatted]</a> and 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>), where this requirement is present, either explicitly or implicitly, for the extraction operators. It is also present explicitly in the description -of getline (istream&, string&, charT) in section 21.3.7.9 <a href="lib-strings.html#lib.string.io"> [lib.string.io]</a> paragraph 8.)</p> +of getline (istream&, string&, charT) in section 21.3.7.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.io"> [lib.string.io]</a> paragraph 8.)</p> <p><b>Proposed resolution:</b></p> -<p>Insert new paragraph after paragraph 2 in section 21.3.7.9 <a href="lib-strings.html#lib.string.io"> [lib.string.io]</a>:</p> +<p>Insert new paragraph after paragraph 2 in section 21.3.7.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.io"> [lib.string.io]</a>:</p> <blockquote> <p>If the function extracts no characters, it calls @@ -4901,13 +5434,13 @@ is.setstate(ios::failbit) which may throw ios_base::failure </blockquote> <hr> <a name="212"><h3>212. Empty range behavior unclear for several algorithms</h3></a><p> -<b>Section:</b> 25.3.7 <a href="lib-algorithms.html#lib.alg.min.max"> [lib.alg.min.max]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 26 Feb 2000</p> +<b>Section:</b> 25.3.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.min.max"> [lib.alg.min.max]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Nico Josuttis <b>Date:</b> 26 Feb 2000</p> <p>The standard doesn't specify what min_element() and max_element() shall return if the range is empty (first equals last). The usual implementations return last. This problem seems also apply to partition(), stable_partition(), next_permutation(), and prev_permutation().</p> <p><b>Proposed resolution:</b></p> -<p>In 25.3.7 <a href="lib-algorithms.html#lib.alg.min.max"> [lib.alg.min.max]</a> - Minimum and maximum, paragraphs 7 and +<p>In 25.3.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.min.max"> [lib.alg.min.max]</a> - Minimum and maximum, paragraphs 7 and 9, append: Returns last if first==last.</p> <p><b>Rationale:</b></p> <p>The LWG looked in some detail at all of the above mentioned @@ -4916,10 +5449,10 @@ max_element() it is already clear that last is returned if first == last.</p> <hr> <a name="214"><h3>214. set::find() missing const overload</h3></a><p> -<b>Section:</b> 23.3.3 <a href="lib-containers.html#lib.set"> [lib.set]</a>, 23.3.4 <a href="lib-containers.html#lib.multiset"> [lib.multiset]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 28 Feb 2000</p> +<b>Section:</b> 23.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.set"> [lib.set]</a>, 23.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.multiset"> [lib.multiset]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 28 Feb 2000</p> <p>The specification for the associative container requirements in -Table 69 state that the find member function should "return -iterator; const_iterator for constant a". The map and multimap +Table 69 state that the find member function should "return +iterator; const_iterator for constant a". The map and multimap container descriptions have two overloaded versions of find, but set and multiset do not, all they have is:</p> <blockquote> @@ -4927,7 +5460,7 @@ and multiset do not, all they have is:</p> </blockquote> <p><b>Proposed resolution:</b></p> <p>Change the prototypes for find(), lower_bound(), upper_bound(), and -equal_range() in section 23.3.3 <a href="lib-containers.html#lib.set"> [lib.set]</a> and section 23.3.4 <a href="lib-containers.html#lib.multiset"> [lib.multiset]</a> to each have two overloads:</p> +equal_range() in section 23.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.set"> [lib.set]</a> and section 23.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.multiset"> [lib.multiset]</a> to each have two overloads:</p> <blockquote> <pre>iterator find(const key_type & x); const_iterator find(const key_type & x) const;</pre> @@ -4944,7 +5477,7 @@ extending the proposed resolution to lower_bound, upper_bound, and equal_range.]</i></p> <hr> <a name="217"><h3>217. Facets example (Classifying Japanese characters) contains errors</h3></a><p> -<b>Section:</b> 22.2.8 <a href="lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 29 Feb 2000</p> +<b>Section:</b> 22.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facets.examples"> [lib.facets.examples]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 29 Feb 2000</p> <p>The example in 22.2.8, paragraph 11 contains the following errors:</p> <p>1) The member function `My::JCtype::is_kanji()' is non-const; the function must be const in order for it to be callable on a const object (a reference to @@ -4955,7 +5488,7 @@ name of the namespace `My'.</p> in main(), the name of the facet is misspelled: it should read `My::JCtype' rather than `My::JCType'.</p> <p><b>Proposed resolution:</b></p> -<p>Replace the "Classifying Japanese characters" example in 22.2.8, +<p>Replace the "Classifying Japanese characters" example in 22.2.8, paragraph 11 with the following:</p> <pre>#include <locale></pre> <pre>namespace My { @@ -4972,23 +5505,23 @@ paragraph 11 with the following:</p> <pre>// file: filt.C #include <iostream> #include <locale> -#include "jctype" // above +#include "jctype" // above std::locale::id My::JCtype::id; // the static JCtype member declared above.</pre> <pre>int main() { using namespace std; typedef ctype<wchar_t> wctype; - locale loc(locale(""), // the user's preferred locale... + locale loc(locale(""), // the user's preferred locale... new My::JCtype); // and a new feature ... wchar_t c = use_facet<wctype>(loc).widen('!'); if (!use_facet<My::JCtype>(loc).is_kanji(c)) - cout << "no it isn't!" << endl; + cout << "no it isn't!" << endl; return 0; }</pre> <hr> <a name="220"><h3>220. ~ios_base() usage valid?</h3></a><p> -<b>Section:</b> 27.4.2.7 <a href="lib-iostreams.html#lib.ios.base.cons"> [lib.ios.base.cons]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Jonathan Schilling, Howard Hinnant <b>Date:</b> 13 Mar 2000</p> +<b>Section:</b> 27.4.2.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios.base.cons"> [lib.ios.base.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Jonathan Schilling, Howard Hinnant <b>Date:</b> 13 Mar 2000</p> <p>The pre-conditions for the ios_base destructor are described in 27.4.2.7 paragraph 2:</p> <blockquote> @@ -5024,13 +5557,14 @@ behavior.</p> </blockquote> <p>to</p> <blockquote> - <p>Effects: Each ios_base member has an indeterminate value after - construction. These members must be initialized by calling basic_ios::init. If an ios_base object is destroyed before these initializations - have taken place, the behavior is undefined.</p> + <p>Effects: Each ios_base member has an indeterminate +value after construction. These members must be initialized by calling +basic_ios::init. If an ios_base object is destroyed before these +initializations have taken place, the behavior is undefined.</p> </blockquote> <hr> <a name="221"><h3>221. num_get<>::do_get stage 2 processing broken</h3></a><p> -<b>Section:</b> 22.2.2.1.2 <a href="lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 14 Mar 2000</p> +<b>Section:</b> 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 14 Mar 2000</p> <p>Stage 2 processing of numeric conversion is broken.</p> <p>Table 55 in 22.2.2.1.2 says that when basefield is 0 the integral @@ -5038,23 +5572,23 @@ conversion specifier is %i. A %i specifier determines a number's base by its prefix (0 for octal, 0x for hex), so the intention is clearly that a 0x prefix is allowed. Paragraph 8 in the same section, however, describes very precisely how characters are processed. (It -must be done "as if" by a specified code fragment.) That +must be done "as if" by a specified code fragment.) That description does not allow a 0x prefix to be recognized.</p> <p>Very roughly, stage 2 processing reads a char_type ct. It converts ct to a char, not by using narrow but by looking it up in a translation table that was created by widening the string literal -"0123456789abcdefABCDEF+-". The character "x" is +"0123456789abcdefABCDEF+-". The character "x" is not found in that table, so it can't be recognized by stage 2 processing.</p> <p><b>Proposed resolution:</b></p> <p>In 22.2.2.1.2 paragraph 8, replace the line:</p> <blockquote> - <pre>static const char src[] = "0123456789abcdefABCDEF+-";</pre> + <pre>static const char src[] = "0123456789abcdefABCDEF+-";</pre> </blockquote> <p>with the line:</p> <blockquote> - <pre>static const char src[] = "0123456789abcdefxABCDEFX+-";</pre> + <pre>static const char src[] = "0123456789abcdefxABCDEFX+-";</pre> </blockquote> <p><b>Rationale:</b></p> <p>If we're using the technique of widening a string literal, the @@ -5064,7 +5598,7 @@ of digits will not be recognized. This design decision was made deliberately, with full knowledge of that limitation.</p> <hr> <a name="222"><h3>222. Are throw clauses necessary if a throw is already implied by the effects clause?</h3></a><p> -<b>Section:</b> 17.3.1.3 <a href="lib-intro.html#lib.structure.specifications"> [lib.structure.specifications]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 17 Mar 2000</p> +<b>Section:</b> 17.3.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.structure.specifications"> [lib.structure.specifications]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 17 Mar 2000</p> <p>Section 21.3.6.8 describes the basic_string::compare function this way:</p> <blockquote> <pre>21.3.6.8 - basic_string::compare [lib.string::compare] @@ -5080,23 +5614,23 @@ int compare(size_type pos1, size_type n1, </blockquote> <p>and the constructor that's implicitly called by the above is defined to throw an out-of-range exception if pos > str.size(). See -section 21.3.1 <a href="lib-strings.html#lib.string.cons"> [lib.string.cons]</a> paragraph 4.</p> +section 21.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.cons"> [lib.string.cons]</a> paragraph 4.</p> <p>On the other hand, the compare function descriptions themselves don't have -"Throws: " clauses and according to 17.3.1.3, paragraph 3, elements +"Throws: " clauses and according to 17.3.1.3, paragraph 3, elements that do not apply to a function are omitted.</p> <p>So it seems there is an inconsistency in the standard -- are the -"Effects" clauses correct, or are the "Throws" clauses +"Effects" clauses correct, or are the "Throws" clauses missing?</p> <p><b>Proposed resolution:</b></p> -<p>In 17.3.1.3 <a href="lib-intro.html#lib.structure.specifications"> [lib.structure.specifications]</a> paragraph 3, the footnote 148 attached to -the sentence "Descriptions of function semantics contain the -following elements (as appropriate):", insert the word -"further" so that the foot note reads:</p> +<p>In 17.3.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.structure.specifications"> [lib.structure.specifications]</a> paragraph 3, the footnote 148 attached to +the sentence "Descriptions of function semantics contain the +following elements (as appropriate):", insert the word +"further" so that the foot note reads:</p> <blockquote> <p>To save space, items that do not apply to a function are omitted. For example, if a function does not specify any further - preconditions, there will be no "Requires" paragraph.</p> + preconditions, there will be no "Requires" paragraph.</p> </blockquote> <p><b>Rationale:</b></p> <p>The standard is somewhat inconsistent, but a failure to note a @@ -5105,11 +5639,11 @@ throw. The inconsistent wording is in a footnote, and thus non-normative. The proposed resolution from the LWG clarifies the footnote.</p> <hr> -<a name="223"><h3>223. reverse algorithm should use iter_swap rather than swap</h3></a><p> -<b>Section:</b> 25.2.9 <a href="lib-algorithms.html#lib.alg.reverse"> [lib.alg.reverse]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 21 Mar 2000</p> -<p>Shouldn't the effects say "applies iter_swap to all pairs..."?</p> +<a name="223"></a><h3><a name="223">223. reverse algorithm should use iter_swap rather than swap</a></h3><p> +<b>Section:</b> 25.2.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.reverse"> [lib.alg.reverse]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 21 Mar 2000</p> +<p>Shouldn't the effects say "applies iter_swap to all pairs..."?</p> <p><b>Proposed resolution:</b></p> -<p>In 25.2.9 <a href="lib-algorithms.html#lib.alg.reverse"> [lib.alg.reverse]</a>, replace:</p> +<p>In 25.2.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.reverse"> [lib.alg.reverse]</a>, replace:</p> <blockquote> Effects: For each non-negative integer i <= (last - first)/2, applies swap to all pairs of iterators first + i, (last - i) - 1. @@ -5121,22 +5655,139 @@ footnote.</p> </blockquote> <hr> <a name="224"><h3>224. clear() complexity for associative containers refers to undefined N</h3></a><p> -<b>Section:</b> 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Ed Brey <b>Date:</b> 23 Mar 2000</p> +<b>Section:</b> 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Ed Brey <b>Date:</b> 23 Mar 2000</p> <p>In the associative container requirements table in 23.1.2 paragraph 7, -a.clear() has complexity "log(size()) + N". However, the meaning of N +a.clear() has complexity "log(size()) + N". However, the meaning of N is not defined.</p> <p><b>Proposed resolution:</b></p> <p>In the associative container requirements table in 23.1.2 paragraph -7, the complexity of a.clear(), change "log(size()) + N" to -"linear in <tt>size()</tt>".</p> +7, the complexity of a.clear(), change "log(size()) + N" to +"linear in <tt>size()</tt>".</p> <p><b>Rationale:</b></p> -<p>It's the "log(size())", not the "N", that is in +<p>It's the "log(size())", not the "N", that is in error: there's no difference between <i>O(N)</i> and <i>O(N + log(N))</i>. The text in the standard is probably an incorrect cut-and-paste from the range version of <tt>erase</tt>.</p> <hr> +<a name="225"><h3>225. std:: algorithms use of other unqualified algorithms</h3></a><p> +<b>Section:</b> 17.4.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.global.functions"> [lib.global.functions]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 01 Apr 2000</p> +<p>Are algorithms in std:: allowed to use other algorithms without qualification, so functions in +user namespaces might be found through Koenig lookup?</p> +<p>For example, a popular standard library implementation includes this +implementation of std::unique:</p> +<blockquote> +<pre>namespace std { + template <class _ForwardIter> + _ForwardIter unique(_ForwardIter __first, _ForwardIter __last) { + __first = adjacent_find(__first, __last); + return unique_copy(__first, __last, __first); + } + }</pre> +</blockquote> +<p>Imagine two users on opposite sides of town, each using unique on his own +sequences bounded by my_iterators . User1 looks at his standard library +implementation and says, "I know how to implement a more efficient +unique_copy for my_iterators", and writes:</p> +<blockquote> +<pre>namespace user1 { + class my_iterator; + // faster version for my_iterator + my_iterator unique_copy(my_iterator, my_iterator, my_iterator); + }</pre> +</blockquote> +<p>user1::unique_copy() is selected by Koenig lookup, as he intended.</p> +<p>User2 has other needs, and writes:</p> +<blockquote> +<pre>namespace user2 { + class my_iterator; + // Returns true iff *c is a unique copy of *a and *b. + bool unique_copy(my_iterator a, my_iterator b, my_iterator c); + }</pre> +</blockquote> +<p>User2 is shocked to find later that his fully-qualified use of +std::unique(user2::my_iterator, user2::my_iterator, user2::my_iterator) fails to +compile (if he's lucky). Looking in the standard, he sees the following Effects +clause for unique():</p> +<blockquote> + <p>Effects: Eliminates all but the first element from every consecutive group + of equal elements referred to by the iterator i in the range [first, last) for + which the following corresponding conditions hold: *i == *(i - 1) or pred(*i, + *(i - 1)) != false</p> +</blockquote> +<p>The standard gives user2 absolutely no reason to think he can interfere with +std::unique by defining names in namespace user2. His standard library has been +built with the template export feature, so he is unable to inspect the +implementation. User1 eventually compiles his code with another compiler, and +his version of unique_copy silently stops being called. Eventually, he realizes +that he was depending on an implementation detail of his library and had no +right to expect his unique_copy() to be called portably.</p> +<p>On the face of it, and given above scenario, it may seem obvious that the +implementation of unique() shown is non-conforming because it uses unique_copy() +rather than ::std::unique_copy(). Most standard library implementations, +however, seem to disagree with this notion.</p> +<p> <i>[Tokyo: Steve Adamczyk from +the core working group indicates that "std::" is sufficient; +leading "::" qualification is not required because any namespace +qualification is sufficient to suppress Koenig lookup.]</i> +</p> +<p><b>Proposed resolution:</b></p> +<p>Add a paragraph and a note at the end of +17.4.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.global.functions"> [lib.global.functions]</a>:</p> +<blockquote> + +<p>Unless otherwise specified, no global or non-member function in the +standard library shall use a function from another namespace which is +found through <i>argument-dependent name lookup</i> (3.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/basic.html#basic.lookup.koenig"> [basic.lookup.koenig]</a>).</p> + +<p>[Note: the phrase "unless otherwise specified" is intended to +allow Koenig lookup in cases like that of ostream_iterators:<br> + +<br> + Effects:</p> + <blockquote> +<p>*out_stream << value;<br> + if(delim != 0) *out_stream << delim;<br> + return (*this);</p> + <p>--end note]</p> + </blockquote> +</blockquote> + +<p><i>[Tokyo: The LWG agrees that this is a defect in the standard, but +is as yet unsure if the proposed resolution is the best +solution. Furthermore, the LWG believes that the same problem of +unqualified library names applies to wording in the standard itself, +and has opened issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#229">229</a> accordingly. Any resolution of +issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#225">225</a> should be coordinated with the resolution of +issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#229">229</a>.]</i></p> + +<p><i>[Toronto: The LWG is not sure if this is a defect in the +standard. Most LWG members believe that an implementation of +<tt>std::unique</tt> like the one quoted in this issue is already +illegal, since, under certain circumstances, its semantics are not +those specified in the standard. The standard's description of +<tt>unique</tt> does not say that overloading <tt>adjacent_find</tt> +should have any effect.]</i></p> + +<p><i>[Curaçao: An LWG-subgroup spent an afternoon working on issues +225, 226, and 229. Their conclusion was that the issues should be +separated into an LWG portion (Howard's paper, N1387=02-0045), and a +EWG portion (Dave will write a proposal). The LWG and EWG had +(separate) discussions of this plan the next day. The proposed +resolution for this issue is in accordance with Howard's paper.]</i></p> + +<p><b>Rationale:</b></p> +<p>It could be argued that this proposed isn't strictly necessary, + that the Standard doesn't grant implementors license to write a + standard function that behaves differently than specified in the + Standard just because of an unrelated user-defined name in some + other namespace. However, this is at worst a clarification. It is + surely right that algorithsm shouldn't pick up random names, that + user-defined names should have no effect unless otherwise specified. + Issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#226">226</a> deals with the question of when it is + appropriate for the standard to explicitly specify otherwise.</p> +<hr> <a name="227"><h3>227. std::swap() should require CopyConstructible or DefaultConstructible arguments</h3></a><p> -<b>Section:</b> 25.2.2 <a href="lib-algorithms.html#lib.alg.swap"> [lib.alg.swap]</a> <b>Status:</b> <a href="lwg-active.html#TC">TC</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 09 Apr 2000</p> +<b>Section:</b> 25.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.swap"> [lib.alg.swap]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#TC">TC</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 09 Apr 2000</p> <p>25.2.2 reads:</p> <blockquote> <p> @@ -5178,16 +5829,16 @@ cut-and-paste from the range version of <tt>erase</tt>.</p> <p> Requires: Type T is CopyConstructible (20.1.3) and Assignable (23.1)</p> </blockquote> <hr> -<a name="228"><h3>228. Incorrect specification of "..._byname" facets</h3></a><p> -<b>Section:</b> 22.2 <a href="lib-locales.html#lib.locale.categories"> [lib.locale.categories]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Apr 2000</p> -<p>The sections 22.2.1.2 <a href="lib-locales.html#lib.locale.ctype.byname"> [lib.locale.ctype.byname]</a>, 22.2.1.4 <a href="lib-locales.html#lib.locale.ctype.byname.special"> [lib.locale.ctype.byname.special]</a>, -22.2.1.6 <a href="lib-locales.html#lib.locale.codecvt.byname"> [lib.locale.codecvt.byname]</a>, 22.2.3.2 <a href="lib-locales.html#lib.locale.numpunct.byname"> [lib.locale.numpunct.byname]</a>, 22.2.4.2 <a href="lib-locales.html#lib.locale.collate.byname"> [lib.locale.collate.byname]</a>, 22.2.5.4 <a href="lib-locales.html#lib.locale.time.put.byname"> [lib.locale.time.put.byname]</a>, 22.2.6.4 <a href="lib-locales.html#lib.locale.moneypunct.byname"> [lib.locale.moneypunct.byname]</a>, and 22.2.7.2 <a href="lib-locales.html#lib.locale.messages.byname"> [lib.locale.messages.byname]</a> overspecify the -definitions of the "..._byname" classes by listing a bunch +<a name="228"><h3>228. Incorrect specification of "..._byname" facets</h3></a><p> +<b>Section:</b> 22.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.categories"> [lib.locale.categories]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 20 Apr 2000</p> +<p>The sections 22.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.byname"> [lib.locale.ctype.byname]</a>, 22.2.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.byname.special"> [lib.locale.ctype.byname.special]</a>, +22.2.1.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.byname"> [lib.locale.codecvt.byname]</a>, 22.2.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.numpunct.byname"> [lib.locale.numpunct.byname]</a>, 22.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.collate.byname"> [lib.locale.collate.byname]</a>, 22.2.5.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.time.put.byname"> [lib.locale.time.put.byname]</a>, 22.2.6.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.moneypunct.byname"> [lib.locale.moneypunct.byname]</a>, and 22.2.7.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.messages.byname"> [lib.locale.messages.byname]</a> overspecify the +definitions of the "..._byname" classes by listing a bunch of virtual functions. At the same time, no semantics of these functions are defined. Real implementations do not define these functions because the functional part of the facets is actually implemented in the corresponding base classes and the constructor of -the "..._byname" version just provides suitable date used by +the "..._byname" version just provides suitable date used by these implementations. For example, the 'numpunct' methods just return values from a struct. The base class uses a statically initialized struct while the derived version reads the contents of this struct @@ -5275,7 +5926,7 @@ specialization it is not virtual.</p> protected: ~time_put_byname(); // virtual }; - }"</pre> + }"</pre> <p> Change section 22.2.6.4 (lib.locale.moneypunct.byname) to become:</p> <pre> namespace std { template <class charT, bool Intl = false> @@ -5300,20 +5951,72 @@ specialization it is not virtual.</p> ~messages_byname(); // virtual }; }</pre> -<p>Remove section 22.2.1.4 <a href="lib-locales.html#lib.locale.ctype.byname.special"> [lib.locale.ctype.byname.special]</a> completely (because in +<p>Remove section 22.2.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.ctype.byname.special"> [lib.locale.ctype.byname.special]</a> completely (because in this case only those members are defined to be virtual which are defined to be virtual in 'ctype<cT>'.)</p> -<p><i>[Post-Tokyo: Dietmar Kühl submitted this issue at the request of -the LWG to solve the underlying problems raised by issue <a href="lwg-closed.html#138">138</a>.]</i></p> +<p><i>[Post-Tokyo: Dietmar Kühl submitted this issue at the request of +the LWG to solve the underlying problems raised by issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#138">138</a>.]</i></p> <p><i>[Copenhagen: proposed resolution was revised slightly, to remove three last virtual functions from <tt>messages_byname</tt>.]</i></p> <hr> +<a name="229"><h3>229. Unqualified references of other library entities</h3></a><p> +<b>Section:</b> 17.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.contents"> [lib.contents]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 19 Apr 2000</p> +<p>Throughout the library chapters, the descriptions of library entities refer +to other library entities without necessarily qualifying the names.</p> + +<p>For example, section 25.2.2 "Swap" describes the effect of +swap_ranges in terms of the unqualified name "swap". This section +could reasonably be interpreted to mean that the library must be implemented so +as to do a lookup of the unqualified name "swap", allowing users to +override any ::std::swap function when Koenig lookup applies.</p> + +<p>Although it would have been best to use explicit qualification with +"::std::" throughout, too many lines in the standard would have to be +adjusted to make that change in a Technical Corrigendum.</p> + +<p>Issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#182">182</a>, which addresses qualification of +<tt>size_t</tt>, is a special case of this. +</p> +<p><b>Proposed resolution:</b></p> +<p>To section 17.4.1.1 "Library contents" Add the following paragraph:</p> +<blockquote> + <p>Whenever a name x defined in the standard library is mentioned, the name x + is assumed to be fully qualified as ::std::x, unless explicitly described + otherwise. For example, if the Effects section for library function F is + described as calling library function G, the function ::std::G is meant.</p> +</blockquote> + +<p><i>[Post-Tokyo: Steve Clamage submitted this issue at the request of +the LWG to solve a problem in the standard itself similar to the +problem within implementations of library identified by issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#225">225</a>. Any resolution of issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#225">225</a> should be +coordinated with the resolution of this issue.]</i></p> + +<p><i>[post-Toronto: Howard is undecided about whether it is +appropriate for all standard library function names referred to in +other standard library functions to be explicitly qualified by +<tt>std</tt>: it is common advice that users should define global +functions that operate on their class in the same namespace as the +class, and this requires argument-dependent lookup if those functions +are intended to be called by library code. Several LWG members are +concerned that valarray appears to require argument-dependent lookup, +but that the wording may not be clear enough to fall under +"unless explicitly described otherwise".]</i></p> + +<p><i>[Curaçao: An LWG-subgroup spent an afternoon working on issues +225, 226, and 229. Their conclusion was that the issues should be +separated into an LWG portion (Howard's paper, N1387=02-0045), and a +EWG portion (Dave will write a proposal). The LWG and EWG had +(separate) discussions of this plan the next day. This paper resolves +issues 225 and 226. In light of that resolution, the proposed +resolution for the current issue makes sense.]</i></p> + +<hr> <a name="230"><h3>230. Assignable specified without also specifying CopyConstructible</h3></a><p> -<b>Section:</b> 17 <a href="lib-intro.html#lib.library"> [lib.library]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 26 Apr 2000</p> -<p>Issue <a href="lwg-defects.html#227">227</a> identified an instance (std::swap) where +<b>Section:</b> 17 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.library"> [lib.library]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 26 Apr 2000</p> +<p>Issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#227">227</a> identified an instance (std::swap) where Assignable was specified without also specifying CopyConstructible. The LWG asked that the standard be searched to determine if the same defect existed elsewhere.</p> @@ -5321,19 +6024,19 @@ determine if the same defect existed elsewhere.</p> <p>There are a number of places (see proposed resolution below) where Assignable is specified without also specifying CopyConstructible. There are also several cases where both are -specified. For example, 26.4.1 <a href="lib-numerics.html#lib.accumulate"> [lib.accumulate]</a>.</p> +specified. For example, 26.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.accumulate"> [lib.accumulate]</a>.</p> <p><b>Proposed resolution:</b></p> -<p>In 23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> table 65 for value_type: -change "T is Assignable" to "T is CopyConstructible and -Assignable" +<p>In 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> table 65 for value_type: +change "T is Assignable" to "T is CopyConstructible and +Assignable" </p> -<p>In 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> table 69 X::key_type; change -"Key is Assignable" to "Key is -CopyConstructible and Assignable"<br> +<p>In 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> table 69 X::key_type; change +"Key is Assignable" to "Key is +CopyConstructible and Assignable"<br> </p> -<p>In 24.1.2 <a href="lib-iterators.html#lib.output.iterators"> [lib.output.iterators]</a> paragraph 1, change: +<p>In 24.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.output.iterators"> [lib.output.iterators]</a> paragraph 1, change: </p> <blockquote> <p> A class or a built-in type X satisfies the requirements of an @@ -5352,7 +6055,7 @@ Table 73: </blockquote> <p><i>[Post-Tokyo: Beman Dawes submitted this issue at the request of -the LWG. He asks that the 25.2.4 <a href="lib-algorithms.html#lib.alg.replace"> [lib.alg.replace]</a> and 25.2.5 <a href="lib-algorithms.html#lib.alg.fill"> [lib.alg.fill]</a> changes be studied carefully, as it is not clear that +the LWG. He asks that the 25.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.replace"> [lib.alg.replace]</a> and 25.2.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.fill"> [lib.alg.fill]</a> changes be studied carefully, as it is not clear that CopyConstructible is really a requirement and may be overspecification.]</i></p> <p><b>Rationale:</b></p> @@ -5363,11 +6066,80 @@ Assignable type was also required to be Copy Constructible, but decided against this because fill and replace really don't require the Copy Constructible property.</p> <hr> -<a name="232"><h3>232. "depends" poorly defined in 17.4.3.1</h3></a><p> -<b>Section:</b> 17.4.3.1 <a href="lib-intro.html#lib.reserved.names"> [lib.reserved.names]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Peter Dimov <b>Date:</b> 18 Apr 2000</p> -<p>17.4.3.1/1 uses the term "depends" to limit the set of allowed -specializations of standard templates to those that "depend on a -user-defined name of external linkage."</p> +<a name="231"><h3>231. Precision in iostream?</h3></a><p> +<b>Section:</b> 22.2.2.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> James Kanze, Stephen Clamage <b>Date:</b> 25 Apr 2000</p> +<p>What is the following program supposed to output?</p> +<pre>#include <iostream> + + int + main() + { + std::cout.setf( std::ios::scientific , std::ios::floatfield ) ; + std::cout.precision( 0 ) ; + std::cout << 1.00 << '\n' ; + return 0 ; + }</pre> +<p>From my C experience, I would expect "1e+00"; this is what +<tt>printf("%.0e" , 1.00 );</tt> does. G++ outputs +"1.000000e+00".</p> + +<p>The only indication I can find in the standard is 22.2.2.2.2/11, +where it says "For conversion from a floating-point type, if +(flags & fixed) != 0 or if str.precision() > 0, then +str.precision() is specified in the conversion specification." +This is an obvious error, however, fixed is not a mask for a field, +but a value that a multi-bit field may take -- the results of and'ing +fmtflags with ios::fixed are not defined, at least not if +ios::scientific has been set. G++'s behavior corresponds to what might +happen if you do use (flags & fixed) != 0 with a typical +implementation (floatfield == 3 << something, fixed == 1 +<< something, and scientific == 2 << something).</p> + +<p>Presumably, the intent is either (flags & floatfield) != 0, or +(flags & floatfield) == fixed; the first gives something more or +less like the effect of precision in a printf floating point +conversion. Only more or less, of course. In order to implement printf +formatting correctly, you must know whether the precision was +explicitly set or not. Say by initializing it to -1, instead of 6, and +stating that for floating point conversions, if precision < -1, 6 +will be used, for fixed point, if precision < -1, 1 will be used, +etc. Plus, of course, if precision == 0 and flags & floatfield == +0, 1 should be = used. But it probably isn't necessary to emulate all +of the anomalies of printf:-).</p> +<p><b>Proposed resolution:</b></p> +<p> +Replace 22.2.2.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a>, paragraph 11, with the following +sentence: +</p> +<blockquote> +For conversion from a floating-point type, +<tt><i>str</i>.precision()</tt> is specified in the conversion +specification. +</blockquote> +<p><b>Rationale:</b></p> +<p>The floatfield determines whether numbers are formatted as if +with %f, %e, or %g. If the <tt>fixed</tt> bit is set, it's %f, +if <tt>scientific</tt> it's %e, and if both bits are set, or +neither, it's %g.</p> +<p>Turning to the C standard, a precision of 0 is meaningful +for %f and %e. For %g, precision 0 is taken to be the same as +precision 1.</p> +<p>The proposed resolution has the effect that if neither +<tt>fixed</tt> nor <tt>scientific</tt> is set we'll be +specifying a precision of 0, which will be internally +turned into 1. There's no need to call it out as a special +case.</p> +<p>The output of the above program will be "1e+00".</p> + +<p><i>[Post-Curaçao: Howard provided improved wording covering the case +where precision is 0 and mode is %g.]</i></p> + +<hr> +<a name="232"><h3>232. "depends" poorly defined in 17.4.3.1</h3></a><p> +<b>Section:</b> 17.4.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.reserved.names"> [lib.reserved.names]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Peter Dimov <b>Date:</b> 18 Apr 2000</p> +<p>17.4.3.1/1 uses the term "depends" to limit the set of allowed +specializations of standard templates to those that "depend on a +user-defined name of external linkage."</p> <p>This term, however, is not adequately defined, making it possible to construct a specialization that is, I believe, technically legal according to 17.4.3.1/1, but that specializes a standard template for a built-in type such as @@ -5385,8 +6157,8 @@ construct a specialization that is, I believe, technically legal according to }</pre> </blockquote> <p><b>Proposed resolution:</b></p> -<p>Change "user-defined name" to "user-defined -type".</p> +<p>Change "user-defined name" to "user-defined +type".</p> <p><b>Rationale:</b></p> <p>This terminology is used in section 2.5.2 and 4.1.1 of <i>The C++ Programming Language</i>. It disallows the example in the issue, @@ -5396,26 +6168,26 @@ possible way for a user to come up with a specialization for bitset, for example, that might not have already been specialized by the implementor?</p> -<p><i>[Toronto: this may be related to issue <a href="lwg-active.html#120">120</a>.]</i></p> +<p><i>[Toronto: this may be related to issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#120">120</a>.]</i></p> <p><i>[post-Toronto: Judy provided the above proposed resolution and rationale.]</i></p> <hr> <a name="234"><h3>234. Typos in allocator definition</h3></a><p> -<b>Section:</b> 20.4.1.1 <a href="lib-utilities.html#lib.allocator.members"> [lib.allocator.members]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 24 Apr 2000</p> +<b>Section:</b> 20.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.members"> [lib.allocator.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 24 Apr 2000</p> <p>In paragraphs 12 and 13 the effects of <tt>construct()</tt> and <tt>destruct()</tt> are described as returns but the functions actually return <tt>void</tt>.</p> <p><b>Proposed resolution:</b></p> -<p>Substitute "Returns" by "Effect".</p> +<p>Substitute "Returns" by "Effect".</p> <hr> <a name="235"><h3>235. No specification of default ctor for reverse_iterator</h3></a><p> -<b>Section:</b> 24.4.1.1 <a href="lib-iterators.html#lib.reverse.iterator"> [lib.reverse.iterator]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 24 Apr 2000</p> +<b>Section:</b> 24.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.reverse.iterator"> [lib.reverse.iterator]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 24 Apr 2000</p> <p>The declaration of <tt>reverse_iterator</tt> lists a default constructor. However, no specification is given what this constructor should do.</p> <p><b>Proposed resolution:</b></p> - <p>In section 24.4.1.3.1 <a href="lib-iterators.html#lib.reverse.iter.cons"> [lib.reverse.iter.cons]</a> add the following + <p>In section 24.4.1.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.reverse.iter.cons"> [lib.reverse.iter.cons]</a> add the following paragraph:</p> <blockquote> <p><tt>reverse_iterator()</tt></p> @@ -5429,7 +6201,7 @@ should do.</p> resolution.]</i></p> <hr> <a name="237"><h3>237. Undefined expression in complexity specification</h3></a><p> -<b>Section:</b> 23.2.2.1 <a href="lib-containers.html#lib.list.cons"> [lib.list.cons]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 24 Apr 2000</p> +<b>Section:</b> 23.2.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.cons"> [lib.list.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 24 Apr 2000</p> <p>The complexity specification in paragraph 6 says that the complexity is linear in <tt>first - last</tt>. Even if <tt>operator-()</tt> is defined on iterators this term is in general undefined because it @@ -5441,14 +6213,13 @@ would have to be <tt>last - first</tt>.</p> <blockquote>Linear in <i>distance(first, last)</i>.</blockquote> <hr> <a name="238"><h3>238. Contradictory results of stringbuf initialization.</h3></a><p> -<b>Section:</b> 27.7.1.1 <a href="lib-iostreams.html#lib.stringbuf.cons"> [lib.stringbuf.cons]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 11 May 2000</p> +<b>Section:</b> 27.7.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringbuf.cons"> [lib.stringbuf.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Dietmar Kühl <b>Date:</b> 11 May 2000</p> <p>In 27.7.1.1 paragraph 4 the results of calling the constructor of 'basic_stringbuf' are said to be <tt>str() == str</tt>. This is fine that far but consider this code:</p> -<pre> - std::basic_stringbuf<char> sbuf("hello, world", std::ios_base::openmode(0)); - std::cout << "'" << sbuf.str() << "'\n"; +<pre> std::basic_stringbuf<char> sbuf("hello, world", std::ios_base::openmode(0)); + std::cout << "'" << sbuf.str() << "'\n"; </pre> <p>Paragraph 3 of 27.7.1.1 basically says that in this case neither @@ -5459,7 +6230,7 @@ ie. both are empty, in which case the return from <tt>str()</tt> is defined to be <tt>basic_string<cT>()</tt>.</p> <p>However, probably only test cases in some testsuites will detect this -"problem"...</p> +"problem"...</p> <p><b>Proposed resolution:</b></p> <p>Remove 27.7.1.1 paragraph 4.</p> <p><b>Rationale:</b></p> @@ -5468,7 +6239,7 @@ we fixed it, it would say just the same thing as text that's already in the standard.</p> <hr> <a name="239"><h3>239. Complexity of unique() and/or unique_copy incorrect</h3></a><p> -<b>Section:</b> 25.2.8 <a href="lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> May 15 2000</p> +<b>Section:</b> 25.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> May 15 2000</p> <p>The complexity of unique and unique_copy are inconsistent with each other and inconsistent with the implementations. The standard specifies:</p> @@ -5495,19 +6266,18 @@ applying the predicate last-first times, especially since it is not specified to which pair in the sequence the predicate is applied twice.</p> <p><b>Proposed resolution:</b></p> -<p>Change both complexity sections in 25.2.8 <a href="lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> to:</p> +<p>Change both complexity sections in 25.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> to:</p> <blockquote>Complexity: For nonempty ranges, exactly last - first - 1 applications of the corresponding predicate.</blockquote> <hr> <a name="240"><h3>240. Complexity of adjacent_find() is meaningless</h3></a><p> -<b>Section:</b> 25.1.5 <a href="lib-algorithms.html#lib.alg.adjacent.find"> [lib.alg.adjacent.find]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> May 15 2000</p> +<b>Section:</b> 25.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.adjacent.find"> [lib.alg.adjacent.find]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> May 15 2000</p> <p>The complexity section of adjacent_find is defective:</p> <blockquote> -<pre> -template <class ForwardIterator> +<pre>template <class ForwardIterator> ForwardIterator adjacent_find(ForwardIterator first, ForwardIterator last BinaryPredicate pred); </pre> @@ -5522,8 +6292,8 @@ of the corresponding predicate. </p> </blockquote> -<p>In the Complexity section, it is not defined what "value" -is supposed to mean. My best guess is that "value" means an +<p>In the Complexity section, it is not defined what "value" +is supposed to mean. My best guess is that "value" means an object for which one of the conditions pred(*i,value) or pred(value,*i) is true, where i is the iterator defined in the Returns section. However, the value type of the input sequence need not be @@ -5536,9 +6306,9 @@ the intended specification. Binders can only be applied to function objects that have the function call operator declared const, which is not required of predicates because they can have non-const data members. For this reason, a specification using a binder could only be -an "as-if" specification.</p> +an "as-if" specification.</p> <p><b>Proposed resolution:</b></p> -<p>Change the complexity section in 25.1.5 <a href="lib-algorithms.html#lib.alg.adjacent.find"> [lib.alg.adjacent.find]</a> to:</p> +<p>Change the complexity section in 25.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.adjacent.find"> [lib.alg.adjacent.find]</a> to:</p> <blockquote> For a nonempty range, exactly <tt>min((<i>i</i> - <i>first</i>) + 1, (<i>last</i> - <i>first</i>) - 1)</tt> applications of the @@ -5550,13 +6320,68 @@ return value. bound. The LWG preferred an exact count.]</i></p> <hr> +<a name="241"><h3>241. Does unique_copy() require CopyConstructible and Assignable?</h3></a><p> +<b>Section:</b> 25.2.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.unique"> [lib.alg.unique]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> May 15 2000</p> + +<p>Some popular implementations of unique_copy() create temporary +copies of values in the input sequence, at least if the input iterator +is a pointer. Such an implementation is built on the assumption that +the value type is CopyConstructible and Assignable.</p> + +<p>It is common practice in the standard that algorithms explicitly +specify any additional requirements that they impose on any of the +types used by the algorithm. An example of an algorithm that creates +temporary copies and correctly specifies the additional requirements +is accumulate(), 26.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.accumulate"> [lib.accumulate]</a>.</p> + +<p>Since the specifications of unique() and unique_copy() do not +require CopyConstructible and Assignable of the InputIterator's value +type the above mentioned implementations are not standard-compliant. I +cannot judge whether this is a defect in the standard or a defect in +the implementations.</p> +<p><b>Proposed resolution:</b></p> +<p>In 25.2.8 change:</p> + +<blockquote> +-4- Requires: The ranges [first, last) and [result, result+(last-first)) +shall not overlap. +</blockquote> + +<p>to:</p> + +<blockquote> + <p>-4- Requires: The ranges [first, last) and [result, + result+(last-first)) shall not overlap. The expression *result = + *first must be valid. If neither InputIterator nor OutputIterator + meets the requirements of forward iterator then the value type of + InputIterator must be copy constructible. Otherwise copy + constructible is not required. </p> +</blockquote> + +<p><i>[Redmond: the original proposed resolution didn't impose an +explicit requirement that the iterator's value type must be copy +constructible, on the grounds that an input iterator's value type must +always be copy constructible. Not everyone in the LWG thought that +this requirement was clear from table 72. It has been suggested that +it might be possible to implement <tt>unique_copy</tt> without +requiring assignability, although current implementations do impose +that requirement. Howard provided new wording.]</i></p> + +<p><i>[ +Curaçao: The LWG changed the PR editorially to specify +"neither...nor...meet..." as clearer than +"both...and...do not meet...". Change believed to be so +minor as not to require re-review. +]</i></p> + +<hr> <a name="242"><h3>242. Side effects of function objects</h3></a><p> -<b>Section:</b> 25.2.3 <a href="lib-algorithms.html#lib.alg.transform"> [lib.alg.transform]</a>, 26.4 <a href="lib-numerics.html#lib.numeric.ops"> [lib.numeric.ops]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> May 15 2000</p> +<b>Section:</b> 25.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.transform"> [lib.alg.transform]</a>, 26.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.numeric.ops"> [lib.numeric.ops]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Angelika Langer <b>Date:</b> May 15 2000</p> <p>The algorithms transform(), accumulate(), inner_product(), partial_sum(), and adjacent_difference() require that the function object supplied to them shall not have any side effects.</p> -<p>The standard defines a side effect in 1.9 <a href="intro.html#intro.execution"> [intro.execution]</a> as:</p> +<p>The standard defines a side effect in 1.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/intro.html#intro.execution"> [intro.execution]</a> as:</p> <blockquote>-7- Accessing an object designated by a volatile lvalue (basic.lval), modifying an object, calling a library I/O function, or calling a function that does any of those operations are all side effects, which are changes @@ -5598,7 +6423,7 @@ a defect.</p> <p><i>Things to notice about these changes:</i></p> <ol> -<li> <i>The fully-closed ("[]" as opposed to half-closed "[)" ranges +<li> <i>The fully-closed ("[]" as opposed to half-closed "[)" ranges are intentional. we want to prevent side-effects from invalidating the end iterators.</i> </li> @@ -5730,43 +6555,43 @@ intentional.]</i></p> <hr> <a name="243"><h3>243. <tt>get</tt> and <tt>getline</tt> when sentry reports failure</h3></a><p> -<b>Section:</b> 27.6.1.3 <a href="lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> May 15 2000</p> +<b>Section:</b> 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> May 15 2000</p> <p>basic_istream<>::get(), and basic_istream<>::getline(), are unclear with respect to the behavior and side-effects of the named functions in case of an error.</p> -<p>27.6.1.3, p1 states that "... If the sentry object returns +<p>27.6.1.3, p1 states that "... If the sentry object returns true, when converted to a value of type bool, the function endeavors -to obtain the requested input..." It is not clear from this (or +to obtain the requested input..." It is not clear from this (or the rest of the paragraph) what precisely the behavior should be when the sentry ctor exits by throwing an exception or when the sentry object returns false. In particular, what is the number of characters extracted that gcount() returns supposed to be?</p> <p>27.6.1.3 p8 and p19 say about the effects of get() and getline(): -"... In any case, it then stores a null character (using -charT()) into the next successive location of the array." Is not +"... In any case, it then stores a null character (using +charT()) into the next successive location of the array." Is not clear whether this sentence applies if either of the conditions above holds (i.e., when sentry fails).</p> <p><b>Proposed resolution:</b></p> <p>Add to 27.6.1.3, p1 after the sentence</p> <blockquote> -"... If the sentry object returns true, when converted to a value of -type bool, the function endeavors to obtain the requested input." +"... If the sentry object returns true, when converted to a value of +type bool, the function endeavors to obtain the requested input." </blockquote> <p>the following</p> <blockquote> -"Otherwise, if the sentry constructor exits by throwing an exception or +"Otherwise, if the sentry constructor exits by throwing an exception or if the sentry object returns false, when converted to a value of type bool, the function returns without attempting to obtain any input. In either case the number of extracted characters is set to 0; unformatted input functions taking a character array of non-zero size as an argument shall also store a null character (using charT()) in the first location -of the array." +of the array." </blockquote> <p><b>Rationale:</b></p> <p>Although the general philosophy of the input functions is that the @@ -5777,8 +6602,8 @@ had language that made this an unambiguous requirement; those words were moved to a place where their context made them less clear. See Jerry Schwarz's message c++std-lib-7618.</p> <hr> -<a name="248"><h3>248. time_get fails to set eofbit</h3></a><p> -<b>Section:</b> 22.2.5 <a href="lib-locales.html#lib.category.time"> [lib.category.time]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 22 June 2000</p> +<a name="248"></a><h3><a name="248">248. time_get fails to set eofbit</a></h3><p> +<b>Section:</b> 22.2.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.category.time"> [lib.category.time]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 22 June 2000</p> <p>There is no requirement that any of time_get member functions set ios::eofbit when they reach the end iterator while parsing their input. Since members of both the num_get and money_get facets are required to @@ -5797,12 +6622,11 @@ because it was more consistent with the way eof is described for other input facets.</p> <hr> <a name="250"><h3>250. splicing invalidates iterators</h3></a><p> -<b>Section:</b> 23.2.2.4 <a href="lib-containers.html#lib.list.ops"> [lib.list.ops]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Brian Parker <b>Date:</b> 14 Jul 2000</p> +<b>Section:</b> 23.2.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.ops"> [lib.list.ops]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Brian Parker <b>Date:</b> 14 Jul 2000</p> <p> Section 23.2.2.4 [lib.list.ops] states that </p> -<pre> - void splice(iterator position, list<T, Allocator>& x); +<pre> void splice(iterator position, list<T, Allocator>& x); </pre> <p> <i>invalidates</i> all iterators and references to list <tt>x</tt>. @@ -5815,14 +6639,14 @@ after <tt>splice</tt>. </p> <p><b>Proposed resolution:</b></p> -<p>Add a footnote to 23.2.2.4 <a href="lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, paragraph 1:</p> +<p>Add a footnote to 23.2.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, paragraph 1:</p> <blockquote> -[<i>Footnote:</i> As specified in 20.1.5 <a href="lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a>, paragraphs +[<i>Footnote:</i> As specified in 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a>, paragraphs 4-5, the semantics described in this clause applies only to the case where allocators compare equal. --end footnote] </blockquote> -<p>In 23.2.2.4 <a href="lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, replace paragraph 4 with:</p> +<p>In 23.2.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, replace paragraph 4 with:</p> <blockquote> Effects: Inserts the contents of x before position and x becomes empty. Pointers and references to the moved elements of x now refer to @@ -5831,7 +6655,7 @@ moved elements will continue to refer to their elements, but they now behave as iterators into *this, not into x. </blockquote> -<p>In 23.2.2.4 <a href="lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, replace paragraph 7 with:</p> +<p>In 23.2.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, replace paragraph 7 with:</p> <blockquote> Effects: Inserts an element pointed to by i from list x before position and removes the element from x. The result is unchanged if @@ -5841,7 +6665,7 @@ to refer to this same element but as a member of *this. Iterators to *i behave as iterators into *this, not into x. </blockquote> -<p>In 23.2.2.4 <a href="lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, replace paragraph 12 with:</p> +<p>In 23.2.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, replace paragraph 12 with:</p> <blockquote> Requires: [first, last) is a valid range in x. The result is undefined if position is an iterator in the range [first, last). @@ -5854,13 +6678,13 @@ iterators into *this, not into x. <p><i>[pre-Copenhagen: Howard provided wording.]</i></p> <p><b>Rationale:</b></p> <p>The original proposed resolution said that iterators and references -would remain "valid". The new proposed resolution clarifies what that +would remain "valid". The new proposed resolution clarifies what that means. Note that this only applies to the case of equal allocators. -From 20.1.5 <a href="lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> paragraph 4, the behavior of list when +From 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> paragraph 4, the behavior of list when allocators compare nonequal is outside the scope of the standard.</p> <hr> <a name="251"><h3>251. basic_stringbuf missing allocator_type</h3></a><p> -<b>Section:</b> 27.7.1 <a href="lib-iostreams.html#lib.stringbuf"> [lib.stringbuf]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 28 Jul 2000</p> +<b>Section:</b> 27.7.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringbuf"> [lib.stringbuf]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 28 Jul 2000</p> <p>The synopsis for the template class <tt>basic_stringbuf</tt> doesn't list a typedef for the template parameter <tt>Allocator</tt>. This makes it impossible to determine the type of @@ -5871,12 +6695,11 @@ template classes in the library that do provide a typedef for the <p>Add to the synopses of the class templates basic_stringbuf (27.7.1), basic_istringstream (27.7.2), basic_ostringstream (27.7.3), and basic_stringstream (27.7.4) the typedef:</p> -<pre> - typedef Allocator allocator_type; +<pre> typedef Allocator allocator_type; </pre> <hr> <a name="252"><h3>252. missing casts/C-style casts used in iostreams</h3></a><p> -<b>Section:</b> 27.7 <a href="lib-iostreams.html#lib.string.streams"> [lib.string.streams]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 28 Jul 2000</p> +<b>Section:</b> 27.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.string.streams"> [lib.string.streams]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 28 Jul 2000</p> <p>27.7.2.2, p1 uses a C-style cast rather than the more appropriate const_cast<> in the Returns clause for basic_istringstream<>::rdbuf(). The same C-style cast is being used in 27.7.3.2, p1, D.7.2.2, p1, and @@ -5912,7 +6735,7 @@ issue is stylistic rather than a matter of correctness.</p> <pre> -2- Returns: const_cast<strstreambuf*>(&sb).</pre> <hr> <a name="256"><h3>256. typo in 27.4.4.2, p17: copy_event does not exist</h3></a><p> -<b>Section:</b> 27.4.4.2 <a href="lib-iostreams.html#lib.basic.ios.members"> [lib.basic.ios.members]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 21 Aug 2000</p> +<b>Section:</b> 27.4.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.basic.ios.members"> [lib.basic.ios.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 21 Aug 2000</p> <p> 27.4.4.2, p17 says </p> @@ -5932,7 +6755,7 @@ copyfmt_event. <p>Replace copy_event with copyfmt_event in the named paragraph.</p> <hr> <a name="259"><h3>259. <tt>basic_string::operator[]</tt> and const correctness</h3></a><p> -<b>Section:</b> 21.3.4 <a href="lib-strings.html#lib.string.access"> [lib.string.access]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Chris Newton <b>Date:</b> 27 Aug 2000</p> +<b>Section:</b> 21.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.access"> [lib.string.access]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Chris Newton <b>Date:</b> 27 Aug 2000</p> <p> <i>Paraphrased from a message that Chris Newton posted to comp.std.c++:</i> </p> @@ -5943,21 +6766,21 @@ seems to violate const correctness. </p> <p> -The standard (21.3.4/1) says that "If <tt>pos < size()</tt>, -returns <tt>data()[pos]</tt>." The types don't work. The +The standard (21.3.4/1) says that "If <tt>pos < size()</tt>, +returns <tt>data()[pos]</tt>." The types don't work. The return value of <tt>data()</tt> is <tt>const charT*</tt>, but <tt>operator[]</tt> has a non-const version whose return type is <tt>reference</tt>. </p> <p><b>Proposed resolution:</b></p> <p> In section 21.3.4, paragraph 1, change -"<tt>data()[<i>pos</i>]</tt>" to "<tt>*(begin() + -<i>pos</i>)</tt>". +"<tt>data()[<i>pos</i>]</tt>" to "<tt>*(begin() + +<i>pos</i>)</tt>". </p> <hr> <a name="260"><h3>260. Inconsistent return type of <tt>istream_iterator::operator++(int)</tt> </h3></a><p> -<b>Section:</b> 24.5.1.2 <a href="lib-iterators.html#lib.istream.iterator.ops"> [lib.istream.iterator.ops]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 27 Aug 2000</p> +<b>Section:</b> 24.5.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.istream.iterator.ops"> [lib.istream.iterator.ops]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 27 Aug 2000</p> <p>The synopsis of istream_iterator::operator++(int) in 24.5.1 shows it as returning the iterator by value. 24.5.1.2, p5 shows the same operator as returning the iterator by reference. That's incorrect @@ -5965,24 +6788,21 @@ given the Effects clause below (since a temporary is returned). The `&' is probably just a typo.</p> <p><b>Proposed resolution:</b></p> <p>Change the declaration in 24.5.1.2, p5 from</p> - <pre> - istream_iterator<T,charT,traits,Distance>& operator++(int); + <pre> istream_iterator<T,charT,traits,Distance>& operator++(int); </pre> <p>to</p> - <pre> - istream_iterator<T,charT,traits,Distance> operator++(int); + <pre> istream_iterator<T,charT,traits,Distance> operator++(int); </pre> <p>(that is, remove the `&').</p> <hr> -<a name="261"><h3>261. Missing description of <tt>istream_iterator::operator!=</tt> -</h3></a><p> -<b>Section:</b> 24.5.1.2 <a href="lib-iterators.html#lib.istream.iterator.ops"> [lib.istream.iterator.ops]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 27 Aug 2000</p> +<a name="261"></a><h3><a name="261">261. Missing description of <tt>istream_iterator::operator!=</tt> +</a></h3><p> +<b>Section:</b> 24.5.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.istream.iterator.ops"> [lib.istream.iterator.ops]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 27 Aug 2000</p> <p> 24.5.1, p3 lists the synopsis for </p> -<pre> - template <class T, class charT, class traits, class Distance> +<pre> template <class T, class charT, class traits, class Distance> bool operator!=(const istream_iterator<T,charT,traits,Distance>& x, const istream_iterator<T,charT,traits,Distance>& y); </pre> @@ -5996,16 +6816,15 @@ or Returns clause) in 24.5.1.2. Add paragraph 7 to the end of section 24.5.1.2 with the following text: </p> -<pre> - template <class T, class charT, class traits, class Distance> +<pre> template <class T, class charT, class traits, class Distance> bool operator!=(const istream_iterator<T,charT,traits,Distance>& x, const istream_iterator<T,charT,traits,Distance>& y); </pre> <p>-7- Returns: !(x == y).</p> <hr> -<a name="262"><h3>262. Bitmask operator ~ specified incorrectly</h3></a><p> -<b>Section:</b> 17.3.2.1.2 <a href="lib-intro.html#lib.bitmask.types"> [lib.bitmask.types]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 03 Sep 2000</p> +<a name="262"></a><h3><a name="262">262. Bitmask operator ~ specified incorrectly</a></h3><p> +<b>Section:</b> 17.3.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.bitmask.types"> [lib.bitmask.types]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 03 Sep 2000</p> <p> The ~ operation should be applied after the cast to int_type. </p> @@ -6014,8 +6833,7 @@ The ~ operation should be applied after the cast to int_type. Change 17.3.2.1.2 [lib.bitmask.types] operator~ from: </p> -<pre> - bitmask operator~ ( bitmask X ) +<pre> bitmask operator~ ( bitmask X ) { return static_cast< bitmask>(static_cast<int_type>(~ X)); } </pre> @@ -6023,18 +6841,17 @@ Change 17.3.2.1.2 [lib.bitmask.types] operator~ from: to: </p> -<pre> - bitmask operator~ ( bitmask X ) +<pre> bitmask operator~ ( bitmask X ) { return static_cast< bitmask>(~static_cast<int_type>(X)); } </pre> <hr> <a name="263"><h3>263. Severe restriction on <tt>basic_string</tt> reference counting</h3></a><p> -<b>Section:</b> 21.3 <a href="lib-strings.html#lib.basic.string"> [lib.basic.string]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Kevlin Henney <b>Date:</b> 04 Sep 2000</p> +<b>Section:</b> 21.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.basic.string"> [lib.basic.string]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Kevlin Henney <b>Date:</b> 04 Sep 2000</p> <p> The note in paragraph 6 suggests that the invalidation rules for references, pointers, and iterators in paragraph 5 permit a reference- counted implementation (actually, according to paragraph 6, they permit -a "reference counted implementation", but this is a minor editorial fix). +a "reference counted implementation", but this is a minor editorial fix). </p> <p> @@ -6043,9 +6860,8 @@ implementation unviable. In the following example none of the conditions for iterator invalidation are satisfied: </p> -<pre> - // first example: "*******************" should be printed twice - string original = "some arbitrary text", copy = original; +<pre> // first example: "*******************" should be printed twice + string original = "some arbitrary text", copy = original; const string & alias = original; string::const_iterator i = alias.begin(), e = alias.end(); @@ -6061,9 +6877,8 @@ conditions for iterator invalidation are satisfied: Similarly, in the following example: </p> -<pre> - // second example: "some arbitrary text" should be printed out - string original = "some arbitrary text", copy = original; +<pre> // second example: "some arbitrary text" should be printed out + string original = "some arbitrary text", copy = original; const string & alias = original; string::const_iterator i = alias.begin(); @@ -6075,7 +6890,7 @@ Similarly, in the following example: <p> I have tested this on three string implementations, two of which were reference counted. The reference-counted implementations gave -"surprising behavior" because they invalidated iterators on +"surprising behavior" because they invalidated iterators on the first call to non-const begin since construction. The current wording does not permit such invalidation because it does not take into account the first call since construction, only the first call @@ -6102,21 +6917,21 @@ Change the following sentence in 21.3 paragraph 5 from </blockquote> <hr> <a name="264"><h3>264. Associative container <tt>insert(i, j)</tt> complexity requirements are not feasible.</h3></a><p> -<b>Section:</b> 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> John Potter <b>Date:</b> 07 Sep 2000</p> +<b>Section:</b> 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> John Potter <b>Date:</b> 07 Sep 2000</p> <p> Table 69 requires linear time if [i, j) is sorted. Sorted is necessary but not sufficient. Consider inserting a sorted range of even integers into a set<int> containing the odd integers in the same range. </p> -<p><i>Related issue: <a href="lwg-closed.html#102">102</a></i></p> +<p><i>Related issue: <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#102">102</a></i></p> <p><b>Proposed resolution:</b></p> <p> In Table 69, in section 23.1.2, change the complexity clause for -insertion of a range from "N log(size() + N) (N is the distance +insertion of a range from "N log(size() + N) (N is the distance from i to j) in general; linear if [i, j) is sorted according to -value_comp()" to "N log(size() + N), where N is the distance -from i to j". +value_comp()" to "N log(size() + N), where N is the distance +from i to j". </p> <p><i>[Copenhagen: Minor fix in proposed resolution: fixed unbalanced @@ -6142,7 +6957,7 @@ linear in some special cases. </p> <hr> <a name="265"><h3>265. std::pair::pair() effects overly restrictive</h3></a><p> -<b>Section:</b> 20.2.2 <a href="lib-utilities.html#lib.pairs"> [lib.pairs]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 11 Sep 2000</p> +<b>Section:</b> 20.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.pairs"> [lib.pairs]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 11 Sep 2000</p> <p> I don't see any requirements on the types of the elements of the std::pair container in 20.2.2. From the descriptions of the member @@ -6180,7 +6995,7 @@ clarified by core issue 178, and there is no longer any doubt that the straightforward implementation is correct.</p> <hr> <a name="266"><h3>266. bad_exception::~bad_exception() missing Effects clause</h3></a><p> -<b>Section:</b> 18.6.2.1 <a href="lib-support.html#lib.bad.exception"> [lib.bad.exception]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 24 Sep 2000</p> +<b>Section:</b> 18.6.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.bad.exception"> [lib.bad.exception]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 24 Sep 2000</p> <p> The synopsis for std::bad_exception lists the function ~bad_exception() but there is no description of what the function does (the Effects @@ -6189,10 +7004,10 @@ clause is missing). <p><b>Proposed resolution:</b></p> <p> Remove the destructor from the class synopses of -<tt>bad_alloc</tt> (18.4.2.1 <a href="lib-support.html#lib.bad.alloc"> [lib.bad.alloc]</a>), -<tt>bad_cast</tt> (18.5.2 <a href="lib-support.html#lib.bad.cast"> [lib.bad.cast]</a>), -<tt>bad_typeid</tt> (18.5.3 <a href="lib-support.html#lib.bad.typeid"> [lib.bad.typeid]</a>), -and <tt>bad_exception</tt> (18.6.2.1 <a href="lib-support.html#lib.bad.exception"> [lib.bad.exception]</a>). +<tt>bad_alloc</tt> (18.4.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.bad.alloc"> [lib.bad.alloc]</a>), +<tt>bad_cast</tt> (18.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.bad.cast"> [lib.bad.cast]</a>), +<tt>bad_typeid</tt> (18.5.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.bad.typeid"> [lib.bad.typeid]</a>), +and <tt>bad_exception</tt> (18.6.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.bad.exception"> [lib.bad.exception]</a>). </p> <p><b>Rationale:</b></p> <p> @@ -6204,7 +7019,7 @@ described in clause 19. </p> <hr> <a name="268"><h3>268. Typo in locale synopsis</h3></a><p> -<b>Section:</b> 22.1.1 <a href="lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 5 Oct 2000</p> +<b>Section:</b> 22.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 5 Oct 2000</p> <p>The synopsis of the class std::locale in 22.1.1 contains two typos: the semicolons after the declarations of the default ctor locale::locale() and the copy ctor locale::locale(const locale&) @@ -6212,22 +7027,20 @@ are missing.</p> <p><b>Proposed resolution:</b></p> <p>Add the missing semicolons, i.e., change</p> -<pre> - // construct/copy/destroy: +<pre> // construct/copy/destroy: locale() throw() locale(const locale& other) throw() </pre> <p>in the synopsis in 22.1.1 to</p> -<pre> - // construct/copy/destroy: +<pre> // construct/copy/destroy: locale() throw(); locale(const locale& other) throw(); </pre> <hr> <a name="270"><h3>270. Binary search requirements overly strict</h3></a><p> -<b>Section:</b> 25.3.3 <a href="lib-algorithms.html#lib.alg.binary.search"> [lib.alg.binary.search]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 18 Oct 2000</p> +<b>Section:</b> 25.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.binary.search"> [lib.alg.binary.search]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 18 Oct 2000</p> <p> Each of the four binary search algorithms (lower_bound, upper_bound, equal_range, binary_search) has a form that allows the user to pass a @@ -6242,8 +7055,7 @@ large record with an integer key. We might reasonably want to look up a record by key, in which case we would want to write something like this: </p> -<pre> - struct key_comp { +<pre> struct key_comp { bool operator()(const X& x, int n) const { return x.key() < n; } @@ -6297,8 +7109,8 @@ operator(), where the version that's actually called does something completely inappropriate. (Such as returning a random value.)</li> <li>An alternative formulation was presented in a paper distributed by -David Abrahams at the meeting, "Binary Search with Heterogeneous -Comparison", J16-01/0027 = WG21 N1313: Instead of viewing the +David Abrahams at the meeting, "Binary Search with Heterogeneous +Comparison", J16-01/0027 = WG21 N1313: Instead of viewing the predicate as a Strict Weak Ordering acting on a sorted sequence, view the predicate/value pair as something that partitions a sequence. This is almost equivalent to saying that we should view binary search @@ -6436,8 +7248,7 @@ The proposed resolution is based on that alternative formulation.</li> <p>to:</p> -<pre> - -2- Returns: +<pre> -2- Returns: make_pair(lower_bound(first, last, value), upper_bound(first, last, value)) or @@ -6464,9 +7275,9 @@ The proposed resolution is based on that alternative formulation.</li> <p><i>[Copenhagen: Dave Abrahams provided this wording]</i></p> -<p><i>[Redmond: Minor changes in wording. (Removed "non-negative", and -changed the "other than those described in" wording.) Also, the LWG -decided to accept the "optional" part.]</i></p> +<p><i>[Redmond: Minor changes in wording. (Removed "non-negative", and +changed the "other than those described in" wording.) Also, the LWG +decided to accept the "optional" part.]</i></p> <p><b>Rationale:</b></p> <p>The proposed resolution reinterprets binary search. Instead of @@ -6480,7 +7291,7 @@ the pair returned by equal_range is a valid range, and that the first part of that pair is the lower bound.</p> <hr> <a name="271"><h3>271. basic_iostream missing typedefs</h3></a><p> -<b>Section:</b> 27.6.1.5 <a href="lib-iostreams.html#lib.iostreamclass"> [lib.iostreamclass]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Nov 2000</p> +<b>Section:</b> 27.6.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostreamclass"> [lib.iostreamclass]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Nov 2000</p> <p> Class template basic_iostream has no typedefs. The typedefs it inherits from its base classes can't be used, since (for example) @@ -6489,10 +7300,9 @@ basic_iostream<T>::traits_type is ambiguous. <p><b>Proposed resolution:</b></p> <p>Add the following to basic_iostream's class synopsis in -27.6.1.5 <a href="lib-iostreams.html#lib.iostreamclass"> [lib.iostreamclass]</a>, immediately after <tt>public</tt>:</p> +27.6.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostreamclass"> [lib.iostreamclass]</a>, immediately after <tt>public</tt>:</p> -<pre> - // types: +<pre> // types: typedef charT char_type; typedef typename traits::int_type int_type; typedef typename traits::pos_type pos_type; @@ -6501,7 +7311,7 @@ basic_iostream<T>::traits_type is ambiguous. </pre> <hr> <a name="272"><h3>272. Missing parentheses around subexpression</h3></a><p> -<b>Section:</b> 27.4.4.3 <a href="lib-iostreams.html#lib.iostate.flags"> [lib.iostate.flags]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Nov 2000</p> +<b>Section:</b> 27.4.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.iostate.flags"> [lib.iostate.flags]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Nov 2000</p> <p> 27.4.4.3, p4 says about the postcondition of the function: If rdbuf()!=0 then state == rdstate(); otherwise @@ -6519,7 +7329,7 @@ Add parentheses like so: rdstate()==(state|ios_base::badbit). </p> <hr> <a name="273"><h3>273. Missing ios_base qualification on members of a dependent class</h3></a><p> -<b>Section:</b> 27 <a href="lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Nov 2000</p> +<b>Section:</b> 27 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Nov 2000</p> <p>27.5.2.4.2, p4, and 27.8.1.6, p2, 27.8.1.7, p3, 27.8.1.9, p2, 27.8.1.10, p3 refer to in and/or out w/o ios_base:: qualification. That's incorrect since the names are members of a dependent base @@ -6529,7 +7339,7 @@ class (14.6.2 [temp.dep]) and thus not visible.</p> members, i.e., ios_base.</p> <hr> <a name="274"><h3>274. a missing/impossible allocator requirement</h3></a><p> -<b>Section:</b> 20.1.5 <a href="lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Nov 2000</p> +<b>Section:</b> 20.1.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.allocator.requirements"> [lib.allocator.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Nov 2000</p> <p> I see that table 31 in 20.1.5, p3 allows T in std::allocator<T> to be of any type. But the synopsis in 20.4.1 calls for allocator<>::address() to @@ -6562,8 +7372,8 @@ provided. any non-const, non-reference type </blockquote> -<p><i>[Redmond: previous proposed resolution was "any non-const, -non-volatile, non-reference type". Got rid of the "non-volatile".]</i></p> +<p><i>[Redmond: previous proposed resolution was "any non-const, +non-volatile, non-reference type". Got rid of the "non-volatile".]</i></p> <p><b>Rationale:</b></p> <p> @@ -6580,12 +7390,12 @@ The original text for proposed resolution 2 was modified so that it also forbids volatile types and reference types. </p> -<p><i>[Curaçao: LWG double checked and believes volatile is correctly +<p><i>[Curaçao: LWG double checked and believes volatile is correctly excluded from the PR.]</i></p> <hr> <a name="275"><h3>275. Wrong type in num_get::get() overloads</h3></a><p> -<b>Section:</b> 22.2.2.1.1 <a href="lib-locales.html#lib.facet.num.get.members"> [lib.facet.num.get.members]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 02 Nov 2000</p> +<b>Section:</b> 22.2.2.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.members"> [lib.facet.num.get.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 02 Nov 2000</p> <p> In 22.2.2.1.1, we have a list of overloads for num_get<>::get(). There are eight overloads, all of which are identical except for the @@ -6624,22 +7434,20 @@ These two lists are not identical. They should be, since the arguments it was given. </p> <p><b>Proposed resolution:</b></p> -<p>In 22.2.2.1.1 <a href="lib-locales.html#lib.facet.num.get.members"> [lib.facet.num.get.members]</a>, change</p> -<pre> - iter_type get(iter_type in, iter_type end, ios_base& str, +<p>In 22.2.2.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.members"> [lib.facet.num.get.members]</a>, change</p> +<pre> iter_type get(iter_type in, iter_type end, ios_base& str, ios_base::iostate& err, short& val) const; </pre> <p>to</p> -<pre> - iter_type get(iter_type in, iter_type end, ios_base& str, +<pre> iter_type get(iter_type in, iter_type end, ios_base& str, ios_base::iostate& err, float& val) const; </pre> <hr> <a name="276"><h3>276. Assignable requirement for container value type overly strict</h3></a><p> -<b>Section:</b> 23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Peter Dimov <b>Date:</b> 07 Nov 2000</p> +<b>Section:</b> 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Peter Dimov <b>Date:</b> 07 Nov 2000</p> <p> 23.1/3 states that the objects stored in a container must be -Assignable. 23.3.1 <a href="lib-containers.html#lib.map"> [lib.map]</a>, paragraph 2, +Assignable. 23.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.map"> [lib.map]</a>, paragraph 2, states that map satisfies all requirements for a container, while in the same time defining value_type as pair<const Key, T> - a type that is not Assignable. @@ -6648,8 +7456,8 @@ that is not Assignable. <p> It should be noted that there exists a valid and non-contradictory interpretation of the current text. The wording in 23.1/3 avoids -mentioning value_type, referring instead to "objects stored in a -container." One might argue that map does not store objects of +mentioning value_type, referring instead to "objects stored in a +container." One might argue that map does not store objects of type map::value_type, but of map::mapped_type instead, and that the Assignable requirement applies to map::mapped_type, not map::value_type. @@ -6663,14 +7471,14 @@ general. <p> For example, the proposed resolution of active library issue -<a href="lwg-defects.html#103">103</a> is to make set::iterator a constant iterator; this +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#103">103</a> is to make set::iterator a constant iterator; this means that no set operations can exploit the fact that the stored objects are Assignable. </p> <p> This is related to, but slightly broader than, closed issue -<a href="lwg-closed.html#140">140</a>. +<a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#140">140</a>. </p> <p><b>Proposed resolution:</b></p> <p>23.1/3: Strike the trailing part of the sentence:</p> @@ -6693,8 +7501,8 @@ the type used to instantiate the container. t is a value of T, and u is a value of (possibly const) T. </blockquote> -<p>23.1, Table 65: in the first row, change "T is Assignable" to "T is -CopyConstructible".</p> +<p>23.1, Table 65: in the first row, change "T is Assignable" to "T is +CopyConstructible".</p> <p>23.2.1/2: Add sentence for Assignable requirement. Change to:</p> @@ -6730,8 +7538,7 @@ following methods are instantiated: [Footnote: Implementors are permitted but not required to take advantage of T's Assignable properties for these methods. -- end foonote] </p> -<pre> - list<T,Allocator>& operator=(const list<T,Allocator>& x ); +<pre> list<T,Allocator>& operator=(const list<T,Allocator>& x ); template <class InputIterator> void assign(InputIterator first, InputIterator last); void assign(size_type n, const T& t); @@ -6767,11 +7574,11 @@ to forbid such implementations.</p> <p>Note that the type stored in a standard container must still satisfy the requirements of the container's allocator; this rules out, for -example, such types as "const int". See issue <a href="lwg-defects.html#274">274</a> +example, such types as "const int". See issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#274">274</a> for more details. </p> -<p>In principle we could also relax the "Assignable" requirement for +<p>In principle we could also relax the "Assignable" requirement for individual <tt>vector</tt> member functions, such as <tt>push_back</tt>. However, the LWG did not see great value in such selective relaxation. Doing so would remove implementors' freedom to @@ -6779,11 +7586,66 @@ implement <tt>vector::push_back</tt> in terms of <tt>vector::insert</tt>.</p> <hr> +<a name="278"><h3>278. What does iterator validity mean?</h3></a><p> +<b>Section:</b> 23.2.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.ops"> [lib.list.ops]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> P.J. Plauger <b>Date:</b> 27 Nov 2000</p> +<p> +Section 23.2.2.4 [lib.list.ops] states that +</p> +<pre> void splice(iterator position, list<T, Allocator>& x); +</pre> +<p> +<i>invalidates</i> all iterators and references to list <tt>x</tt>. +</p> + +<p> +But what does the C++ Standard mean by "invalidate"? You +can still dereference the iterator to a spliced list element, but +you'd better not use it to delimit a range within the original +list. For the latter operation, it has definitely lost some of its +validity. +</p> + +<p> +If we accept the proposed resolution to issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#250">250</a>, +then we'd better clarify that a "valid" iterator need no +longer designate an element within the same container as it once did. +We then have to clarify what we mean by invalidating a past-the-end +iterator, as when a vector or string grows by reallocation. Clearly, +such an iterator has a different kind of validity. Perhaps we should +introduce separate terms for the two kinds of "validity." +</p> +<p><b>Proposed resolution:</b></p> +<p>Add the following text to the end of section 24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a>, +after paragraph 5:</p> +<blockquote> +An <i>invalid</i> iterator is an iterator that may be +singular. [Footnote: This definition applies to pointers, since +pointers are iterators. The effect of dereferencing an iterator that +has been invalidated is undefined.] +</blockquote> + +<p><i>[post-Copenhagen: Matt provided wording.]</i></p> + +<p><i>[Redmond: General agreement with the intent, some objections to +the wording. Dave provided new wording.]</i></p> +<p><b>Rationale:</b></p> +<p>This resolution simply defines a term that the Standard uses but + never defines, "invalid", in terms of a term that is defined, + "singular".</p> + +<p>Why do we say "may be singular", instead of "is singular"? That's + becuase a valid iterator is one that is known to be nonsingular. + Invalidating an iterator means changing it in such a way that it's + no longer known to be nonsingular. An example: inserting an + element into the middle of a vector is correctly said to invalidate + all iterators pointing into the vector. That doesn't necessarily + mean they all become singular.</p> +<hr> <a name="281"><h3>281. std::min() and max() requirements overly restrictive</h3></a><p> -<b>Section:</b> 25.3.7 <a href="lib-algorithms.html#lib.alg.min.max"> [lib.alg.min.max]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Dec 2000</p> +<b>Section:</b> 25.3.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.min.max"> [lib.alg.min.max]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Dec 2000</p> <p>The requirements in 25.3.7, p1 and 4 call for T to satisfy the -requirements of <tt>LessThanComparable</tt> (20.1.2 <a href="lib-utilities.html#lib.lessthancomparable"> [lib.lessthancomparable]</a>) -and <tt>CopyConstructible</tt> (20.1.3 <a href="lib-utilities.html#lib.copyconstructible"> [lib.copyconstructible]</a>). +requirements of <tt>LessThanComparable</tt> (20.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.lessthancomparable"> [lib.lessthancomparable]</a>) +and <tt>CopyConstructible</tt> (20.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.copyconstructible"> [lib.copyconstructible]</a>). Since the functions take and return their arguments and result by const reference, I believe the <tt>CopyConstructible</tt> requirement is unnecessary. @@ -6793,32 +7655,76 @@ is unnecessary. 25.3.7, p1 with</p> <p> <b>-1- Requires:</b> Type T is <tt>LessThanComparable</tt> -(20.1.2 <a href="lib-utilities.html#lib.lessthancomparable"> [lib.lessthancomparable]</a>). +(20.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.lessthancomparable"> [lib.lessthancomparable]</a>). </p> <p>and replace 25.3.7, p4 with</p> <p> <b>-4- Requires:</b> Type T is <tt>LessThanComparable</tt> -(20.1.2 <a href="lib-utilities.html#lib.lessthancomparable"> [lib.lessthancomparable]</a>). +(20.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.lessthancomparable"> [lib.lessthancomparable]</a>). </p> <hr> +<a name="282"><h3>282. What types does numpunct grouping refer to?</h3></a><p> +<b>Section:</b> 22.2.2.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.put.virtuals"> [lib.facet.num.put.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 5 Dec 2000</p> +<p> +Paragraph 16 mistakenly singles out integral types for inserting +thousands_sep() characters. This conflicts with the syntax for floating +point numbers described under 22.2.3.1/2. +</p> +<p><b>Proposed resolution:</b></p> +<p>Change paragraph 16 from:</p> + +<blockquote> +For integral types, punct.thousands_sep() characters are inserted into +the sequence as determined by the value returned by punct.do_grouping() +using the method described in 22.2.3.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.numpunct.virtuals"> [lib.facet.numpunct.virtuals]</a>. +</blockquote> + +<p>To:</p> + +<blockquote> +For arithmetic types, punct.thousands_sep() characters are inserted into +the sequence as determined by the value returned by punct.do_grouping() +using the method described in 22.2.3.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.numpunct.virtuals"> [lib.facet.numpunct.virtuals]</a>. +</blockquote> + +<p><i>[ +Copenhagen: Opinions were divided about whether this is actually an +inconsistency, but at best it seems to have been unintentional. This +is only an issue for floating-point output: The standard is +unambiguous that implementations must parse thousands_sep characters +when performing floating-point. The standard is also unambiguous that +this requirement does not apply to the "C" locale. +]</i></p> + +<p><i>[ +A survey of existing practice is needed; it is believed that some +implementations do insert thousands_sep characters for floating-point +output and others fail to insert thousands_sep characters for +floating-point input even though this is unambiguously required by the +standard. +]</i></p> + +<p><i>[Post-Curaçao: the above proposed resolution is the consensus of +Howard, Bill, Pete, Benjamin, Nathan, Dietmar, Boris, and Martin.]</i></p> + +<hr> <a name="284"><h3>284. unportable example in 20.3.7, p6</h3></a><p> -<b>Section:</b> 20.3.7 <a href="lib-utilities.html#lib.function.pointer.adaptors"> [lib.function.pointer.adaptors]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 26 Dec 2000</p> -<p>The example in 20.3.7 <a href="lib-utilities.html#lib.function.pointer.adaptors"> [lib.function.pointer.adaptors]</a>, p6 shows how to use the C +<b>Section:</b> 20.3.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.function.pointer.adaptors"> [lib.function.pointer.adaptors]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 26 Dec 2000</p> +<p>The example in 20.3.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.function.pointer.adaptors"> [lib.function.pointer.adaptors]</a>, p6 shows how to use the C library function <tt>strcmp()</tt> with the function pointer adapter <tt>ptr_fun()</tt>. But since it's unspecified whether the C library -functions have <tt>extern "C"</tt> or <tt>extern -"C++"</tt> linkage [17.4.2.2 <a href="lib-intro.html#lib.using.linkage"> [lib.using.linkage]</a>], and since +functions have <tt>extern "C"</tt> or <tt>extern +"C++"</tt> linkage [17.4.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.using.linkage"> [lib.using.linkage]</a>], and since function pointers with different the language linkage specifications -(7.5 <a href="dcl.html#dcl.link"> [dcl.link]</a>) are incompatible, whether this example is +(7.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/dcl.html#dcl.link"> [dcl.link]</a>) are incompatible, whether this example is well-formed is unspecified. </p> <p><b>Proposed resolution:</b></p> -<p>Change 20.3.7 <a href="lib-utilities.html#lib.function.pointer.adaptors"> [lib.function.pointer.adaptors]</a> paragraph 6 from:</p> +<p>Change 20.3.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.function.pointer.adaptors"> [lib.function.pointer.adaptors]</a> paragraph 6 from:</p> <blockquote> <p>[<i>Example:</i> </p> - <pre> - replace_if(v.begin(), v.end(), not1(bind2nd(ptr_fun(strcmp), "C")), "C++"); + <pre> replace_if(v.begin(), v.end(), not1(bind2nd(ptr_fun(strcmp), "C")), "C++"); </pre> <p>replaces each <tt>C</tt> with <tt>C++</tt> in sequence <tt>v</tt>.</p> </blockquote> @@ -6828,10 +7734,9 @@ well-formed is unspecified. <blockquote> <p>[<i>Example:</i> </p> - <pre> - int compare(const char*, const char*); + <pre> int compare(const char*, const char*); replace_if(v.begin(), v.end(), - not1(bind2nd(ptr_fun(compare), "abc")), "def"); + not1(bind2nd(ptr_fun(compare), "abc")), "def"); </pre> <p>replaces each <tt>abc</tt> with <tt>def</tt> in sequence <tt>v</tt>.</p> </blockquote> @@ -6840,7 +7745,7 @@ well-formed is unspecified. <p><i>[Copenhagen: Minor change in the proposed resolution. Since this issue deals in part with C and C++ linkage, it was believed to be too -confusing for the strings in the example to be "C" and "C++". +confusing for the strings in the example to be "C" and "C++". ]</i></p> <p><i>[Redmond: More minor changes. Got rid of the footnote (which @@ -6850,9 +7755,9 @@ it corresponds to the new code fragment.]</i></p> <hr> <a name="285"><h3>285. minor editorial errors in fstream ctors</h3></a><p> -<b>Section:</b> 27.8.1.6 <a href="lib-iostreams.html#lib.ifstream.cons"> [lib.ifstream.cons]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 31 Dec 2000</p> -<p>27.8.1.6 <a href="lib-iostreams.html#lib.ifstream.cons"> [lib.ifstream.cons]</a>, p2, 27.8.1.9 <a href="lib-iostreams.html#lib.ofstream.cons"> [lib.ofstream.cons]</a>, p2, and -27.8.1.12 <a href="lib-iostreams.html#lib.fstream.cons"> [lib.fstream.cons]</a>, p2 say about the effects of each constructor: +<b>Section:</b> 27.8.1.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ifstream.cons"> [lib.ifstream.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 31 Dec 2000</p> +<p>27.8.1.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ifstream.cons"> [lib.ifstream.cons]</a>, p2, 27.8.1.9 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ofstream.cons"> [lib.ofstream.cons]</a>, p2, and +27.8.1.12 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.fstream.cons"> [lib.fstream.cons]</a>, p2 say about the effects of each constructor: </p> <p>... If that function returns a null pointer, calls @@ -6860,7 +7765,7 @@ it corresponds to the new code fragment.]</i></p> </p> <p>The parenthetical note doesn't apply since the ctors cannot throw an -exception due to the requirement in 27.4.4.1 <a href="lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a>, p3 +exception due to the requirement in 27.4.4.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.basic.ios.cons"> [lib.basic.ios.cons]</a>, p3 that <tt>exceptions()</tt> be initialized to <tt>ios_base::goodbit</tt>. </p> <p><b>Proposed resolution:</b></p> @@ -6870,7 +7775,7 @@ paragraphs mentioned above. </p> <hr> <a name="286"><h3>286. <cstdlib> requirements missing size_t typedef</h3></a><p> -<b>Section:</b> 25.4 <a href="lib-algorithms.html#lib.alg.c.library"> [lib.alg.c.library]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 30 Dec 2000</p> +<b>Section:</b> 25.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.c.library"> [lib.alg.c.library]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 30 Dec 2000</p> <p> The <cstdlib> header file contains prototypes for bsearch and qsort (C++ Standard section 25.4 paragraphs 3 and 4) and other @@ -6887,11 +7792,11 @@ the type size_t <cstdlib> to Table 97 (section C.2). <p>Since size_t is in <stdlib.h>, it must also be in <cstdlib>.</p> <hr> <a name="288"><h3>288. <cerrno> requirements missing macro EILSEQ</h3></a><p> -<b>Section:</b> 19.3 <a href="lib-diagnostics.html#lib.errno"> [lib.errno]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 30 Dec 2000</p> +<b>Section:</b> 19.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-diagnostics.html#lib.errno"> [lib.errno]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Judy Ward <b>Date:</b> 30 Dec 2000</p> <p> -ISO/IEC 9899:1990/Amendment1:1994 Section 4.3 States: "The list +ISO/IEC 9899:1990/Amendment1:1994 Section 4.3 States: "The list of macros defined in <errno.h> is adjusted to include a new -macro, EILSEQ" +macro, EILSEQ" </p> <p> @@ -6901,12 +7806,12 @@ to the above amendment. <p><b>Proposed resolution:</b></p> <p> -Update Table 26 (section 19.3) "Header <cerrno> synopsis" -and Table 95 (section C.2) "Standard Macros" to include EILSEQ. +Update Table 26 (section 19.3) "Header <cerrno> synopsis" +and Table 95 (section C.2) "Standard Macros" to include EILSEQ. </p> <hr> <a name="292"><h3>292. effects of a.copyfmt (a)</h3></a><p> -<b>Section:</b> 27.4.4.2 <a href="lib-iostreams.html#lib.basic.ios.members"> [lib.basic.ios.members]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 05 Jan 2001</p> +<b>Section:</b> 27.4.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.basic.ios.members"> [lib.basic.ios.members]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 05 Jan 2001</p> <p>The Effects clause of the member function <tt>copyfmt()</tt> in 27.4.4.2, p15 doesn't consider the case where the left-hand side argument is identical to the argument on the right-hand side, that is @@ -6935,7 +7840,7 @@ objects of <tt>rhs</tt>, except that... </blockquote> <hr> <a name="295"><h3>295. Is abs defined in <cmath>?</h3></a><p> -<b>Section:</b> 26.5 <a href="lib-numerics.html#lib.c.math"> [lib.c.math]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Jens Maurer <b>Date:</b> 12 Jan 2001</p> +<b>Section:</b> 26.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.c.math"> [lib.c.math]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Jens Maurer <b>Date:</b> 12 Jan 2001</p> <p> Table 80 lists the contents of the <cmath> header. It does not list <tt>abs()</tt>. However, 26.5, paragraph 6, which lists added @@ -6945,7 +7850,7 @@ of <tt>abs()</tt> should be defined in <cmath>. <p><b>Proposed resolution:</b></p> <p> Add <tt>abs</tt> to Table 80. Also, remove the parenthetical list -of functions "(abs(), div(), rand(), srand())" from 26.5 <a href="lib-numerics.html#lib.c.math"> [lib.c.math]</a>, +of functions "(abs(), div(), rand(), srand())" from 26.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-numerics.html#lib.c.math"> [lib.c.math]</a>, paragraph 1. </p> @@ -6956,10 +7861,10 @@ rid of that vestigial list of functions in paragraph 1.]</i></p> <p>All this DR does is fix a typo; it's uncontroversial. A separate question is whether we're doing the right thing in putting some overloads in <cmath> that we aren't also -putting in <cstdlib>. That's issue <a href="lwg-active.html#323">323</a>.</p> +putting in <cstdlib>. That's issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#323">323</a>.</p> <hr> <a name="297"><h3>297. const_mem_fun_t<>::argument_type should be const T*</h3></a><p> -<b>Section:</b> 20.3.8 <a href="lib-utilities.html#lib.member.pointer.adaptors"> [lib.member.pointer.adaptors]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 6 Jan 2001</p> +<b>Section:</b> 20.3.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.member.pointer.adaptors"> [lib.member.pointer.adaptors]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 6 Jan 2001</p> <p>The class templates <tt>const_mem_fun_t</tt> in 20.3.8, p8 and <tt>const_mem_fun1_t</tt> in 20.3.8, p9 derive from <tt>unary_function<T*, S></tt>, and @@ -7036,7 +7941,7 @@ binary_function<<b>const</b> T*, A, S> {</tt> and the argument type itself, are not the same.</p> <hr> <a name="298"><h3>298. ::operator delete[] requirement incorrect/insufficient</h3></a><p> -<b>Section:</b> 18.4.1.2 <a href="lib-support.html#lib.new.delete.array"> [lib.new.delete.array]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> John A. Pedretti <b>Date:</b> 10 Jan 2001</p> +<b>Section:</b> 18.4.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete.array"> [lib.new.delete.array]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> John A. Pedretti <b>Date:</b> 10 Jan 2001</p> <p> The default behavior of <tt>operator delete[]</tt> described in 18.4.1.2, p12 - namely that for non-null value of <i>ptr</i>, the operator reclaims storage @@ -7059,7 +7964,7 @@ For a null value of <i><tt>ptr</tt></i> , does nothing. Any other value of <i><tt>ptr</tt></i> shall be a value returned earlier by a call to the default <tt>operator new[](std::size_t)</tt>. [Footnote: The value must not have been invalidated by an intervening -call to <tt>operator delete[](void*)</tt> (17.4.3.7 <a href="lib-intro.html#lib.res.on.arguments"> [lib.res.on.arguments]</a>). +call to <tt>operator delete[](void*)</tt> (17.4.3.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.res.on.arguments"> [lib.res.on.arguments]</a>). --- end footnote] For such a non-null value of <i><tt>ptr</tt></i> , reclaims storage allocated by the earlier call to the default <tt>operator new[]</tt>. @@ -7076,8 +7981,56 @@ or <tt>operator delete(<i>ptr</i>, std::nothrow)</tt> respectively. </blockquote> <p>and expunge paragraph 13.</p> <hr> +<a name="300"><h3>300. list::merge() specification incomplete</h3></a><p> +<b>Section:</b> 23.2.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.ops"> [lib.list.ops]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> John Pedretti <b>Date:</b> 23 Jan 2001</p> +<p> +The "Effects" clause for list::merge() (23.2.2.4, p23) +appears to be incomplete: it doesn't cover the case where the argument +list is identical to *this (i.e., this == &x). The requirement in the +note in p24 (below) is that x be empty after the merge which is surely +unintended in this case. +</p> +<p><b>Proposed resolution:</b></p> +<p>In 23.2.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, replace paragraps 23-25 with:</p> +<blockquote> +<p> +23 Effects: if (&x == this) does nothing; otherwise, merges the two +sorted ranges [begin(), end()) and [x.begin(), x.end()). The result +is a range in which the elements will be sorted in non-decreasing +order according to the ordering defined by comp; that is, for every +iterator i in the range other than the first, the condition comp(*i, +*(i - 1)) will be false. +</p> + +<p> +24 Notes: Stable: if (&x != this), then for equivalent elements in the +two original ranges, the elements from the original range [begin(), +end()) always precede the elements from the original range [x.begin(), +x.end()). If (&x != this) the range [x.begin(), x.end()) is empty +after the merge. +</p> + +<p> +25 Complexity: At most size() + x.size() - 1 applications of comp if +(&x ! = this); otherwise, no applications of comp are performed. If +an exception is thrown other than by a comparison there are no +effects. +</p> + +</blockquote> + +<p><i>[Copenhagen: The original proposed resolution did not fix all of +the problems in 23.2.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, p22-25. Three different +paragraphs (23, 24, 25) describe the effects of <tt>merge</tt>. +Changing p23, without changing the other two, appears to introduce +contradictions. Additionally, "merges the argument list into the +list" is excessively vague.]</i></p> + +<p><i>[Post-Curaçao: Robert Klarer provided new wording.]</i></p> + +<hr> <a name="301"><h3>301. basic_string template ctor effects clause omits allocator argument</h3></a><p> -<b>Section:</b> 21.3.1 <a href="lib-strings.html#lib.string.cons"> [lib.string.cons]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 27 Jan 2001</p> +<b>Section:</b> 21.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.string.cons"> [lib.string.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 27 Jan 2001</p> <p> The effects clause for the basic_string template ctor in 21.3.1, p15 leaves out the third argument of type Allocator. I believe this to be @@ -7107,11 +8060,11 @@ a mistake. </blockquote> <hr> <a name="303"><h3>303. Bitset input operator underspecified</h3></a><p> -<b>Section:</b> 23.3.5.3 <a href="lib-containers.html#lib.bitset.operators"> [lib.bitset.operators]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 5 Feb 2001</p> +<b>Section:</b> 23.3.5.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.bitset.operators"> [lib.bitset.operators]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 5 Feb 2001</p> <p> In 23.3.5.3, we are told that <tt>bitset</tt>'s input operator -"Extracts up to <i>N</i> (single-byte) characters from -<i>is</i>.", where <i>is</i> is a stream of type +"Extracts up to <i>N</i> (single-byte) characters from +<i>is</i>.", where <i>is</i> is a stream of type <tt>basic_istream<charT, traits></tt>. </p> @@ -7212,26 +8165,139 @@ input. Using <tt>widen</tt> does mean that alternative digit representations will not be recognized, but this was a known consequence of the design choice.</p> <hr> +<a name="305"><h3>305. Default behavior of codecvt<wchar_t, char, mbstate_t>::length()</h3></a><p> +<b>Section:</b> 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 24 Jan 2001</p> +<p>22.2.1.5/3 introduces codecvt in part with:</p> + +<blockquote> + codecvt<wchar_t,char,mbstate_t> converts between the native + character sets for tiny and wide characters. Instantiations on + mbstate_t perform conversion between encodings known to the library + implementor. +</blockquote> + +<p>But 22.2.1.5.2/10 describes do_length in part with:</p> + +<blockquote> + ... codecvt<wchar_t, char, mbstate_t> ... return(s) the lesser of max and + (from_end-from). +</blockquote> + +<p> +The semantics of do_in and do_length are linked. What one does must +be consistent with what the other does. 22.2.1.5/3 leads me to +believe that the vendor is allowed to choose the algorithm that +codecvt<wchar_t,char,mbstate_t>::do_in performs so that it makes +his customers happy on a given platform. But 22.2.1.5.2/10 explicitly +says what codecvt<wchar_t,char,mbstate_t>::do_length must +return. And thus indirectly specifies the algorithm that +codecvt<wchar_t,char,mbstate_t>::do_in must perform. I believe +that this is not what was intended and is a defect. +</p> + +<p>Discussion from the -lib reflector: + +<br>This proposal would have the effect of making the semantics of +all of the virtual functions in <tt>codecvt<wchar_t, char, +mbstate_t></tt> implementation specified. Is that what we want, or +do we want to mandate specific behavior for the base class virtuals +and leave the implementation specified behavior for the codecvt_byname +derived class? The tradeoff is that former allows implementors to +write a base class that actually does something useful, while the +latter gives users a way to get known and specified---albeit +useless---behavior, and is consistent with the way the standard +handles other facets. It is not clear what the original intention +was.</p> + +<p> +Nathan has suggest a compromise: a character that is a widened version +of the characters in the basic execution character set must be +converted to a one-byte sequence, but there is no such requirement +for characters that are not part of the basic execution character set. +</p> +<p><b>Proposed resolution:</b></p> +<p> +Change 22.2.1.5.2/5 from: +</p> +<p> +The instantiations required in Table 51 (lib.locale.category), namely +codecvt<wchar_t,char,mbstate_t> and +codecvt<char,char,mbstate_t>, store no characters. Stores no more +than (to_limit-to) destination elements. It always leaves the to_next +pointer pointing one beyond the last element successfully stored. +</p> +<p> +to: +</p> +<p> +Stores no more than (to_limit-to) destination elements, and leaves the +to_next pointer pointing one beyond the last element successfully +stored. codecvt<char,char,mbstate_t> stores no characters. +</p> + +<p>Change 22.2.1.5.2/10 from:</p> + +<blockquote> +-10- Returns: (from_next-from) where from_next is the largest value in +the range [from,from_end] such that the sequence of values in the +range [from,from_next) represents max or fewer valid complete +characters of type internT. The instantiations required in Table 51 +(21.1.1.1.1), namely codecvt<wchar_t, char, mbstate_t> and +codecvt<char, char, mbstate_t>, return the lesser of max and +(from_end-from). +</blockquote> + +<p>to:</p> + +<blockquote> +-10- Returns: (from_next-from) where from_next is the largest value in +the range [from,from_end] such that the sequence of values in the range +[from,from_next) represents max or fewer valid complete characters of +type internT. The instantiation codecvt<char, char, mbstate_t> returns +the lesser of max and (from_end-from). +</blockquote> + +<p><i>[Redmond: Nathan suggested an alternative resolution: same as +above, but require that, in the default encoding, a character from the +basic execution character set would map to a single external +character. The straw poll was 8-1 in favor of the proposed +resolution.]</i></p> + +<p><b>Rationale:</b></p> +<p>The default encoding should be whatever users of a given platform +would expect to be the most natural. This varies from platform to +platform. In many cases there is a preexisting C library, and users +would expect the default encoding to be whatever C uses in the default +"C" locale. We could impose a guarantee like the one Nathan suggested +(a character from the basic execution character set must map to a +single external character), but this would rule out important +encodings that are in common use: it would rule out JIS, for +example, and it would rule out a fixed-width encoding of UCS-4.</p> + +<p><i>[Curaçao: fixed rationale typo at the request of Ichiro Koshida; +"shift-JIS" changed to "JIS".]</i></p> + +<hr> <a name="306"><h3>306. offsetof macro and non-POD types</h3></a><p> -<b>Section:</b> 18.1 <a href="lib-support.html#lib.support.types"> [lib.support.types]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 21 Feb 2001</p> +<b>Section:</b> 18.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.support.types"> [lib.support.types]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 21 Feb 2001</p> <p>Spliced together from reflector messages c++std-lib-8294 and -8295:</p> -<p>18.1, paragraph 5, reads: "The macro <tt>offsetof</tt> +<p>18.1, paragraph 5, reads: "The macro <tt>offsetof</tt> accepts a restricted set of <i>type</i> arguments in this International Standard. <i>type</i> shall be a POD structure or a POD union (clause 9). The result of applying the offsetof macro to a field that is a static data member or a function member is -undefined."</p> +undefined."</p> -<p>For the POD requirement, it doesn't say "no diagnostic -required" or "undefined behavior". I read 1.4 <a href="intro.html#intro.compliance"> [intro.compliance]</a>, paragraph 1, to mean that a diagnostic is required. +<p>For the POD requirement, it doesn't say "no diagnostic +required" or "undefined behavior". I read 1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/intro.html#intro.compliance"> [intro.compliance]</a>, paragraph 1, to mean that a diagnostic is required. It's not clear whether this requirement was intended. While it's possible to provide such a diagnostic, the extra complication doesn't seem to add any value. </p> <p><b>Proposed resolution:</b></p> -<p>Change 18.1, paragraph 5, to "If <i>type</i> is not a POD -structure or a POD union the results are undefined."</p> +<p>Change 18.1, paragraph 5, to "If <i>type</i> is not a POD +structure or a POD union the results are undefined."</p> <p><i>[Copenhagen: straw poll was 7-4 in favor. It was generally agreed that requiring a diagnostic was inadvertent, but some LWG @@ -7240,13 +8306,13 @@ possible.]</i></p> <hr> <a name="307"><h3>307. Lack of reference typedefs in container adaptors</h3></a><p> -<b>Section:</b> 23.2.3 <a href="lib-containers.html#lib.container.adaptors"> [lib.container.adaptors]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 13 Mar 2001</p> +<b>Section:</b> 23.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.adaptors"> [lib.container.adaptors]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 13 Mar 2001</p> <p>From reflector message c++std-lib-8330. See also lib-8317.</p> <p> -The standard is currently inconsistent in 23.2.3.2 <a href="lib-containers.html#lib.priority.queue"> [lib.priority.queue]</a> -paragraph 1 and 23.2.3.3 <a href="lib-containers.html#lib.stack"> [lib.stack]</a> paragraph 1. +The standard is currently inconsistent in 23.2.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.priority.queue"> [lib.priority.queue]</a> +paragraph 1 and 23.2.3.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.stack"> [lib.stack]</a> paragraph 1. 23.2.3.3/1, for example, says: </p> @@ -7272,7 +8338,7 @@ container's reference type.</p> <p> I propose 3. This does not preclude option 2 if we choose to do it -later (see issue <a href="lwg-active.html#96">96</a>); the issues are independent. Option +later (see issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#96">96</a>); the issues are independent. Option 3 offers a small step towards support for proxied containers. This small step fixes a current contradiction, is easy for vendors to implement, is already implemented in at least one popular lib, and @@ -7281,14 +8347,13 @@ does not break any code. <p><b>Proposed resolution:</b></p> <p>Summary: Add reference and const_reference typedefs to queue, -priority_queue and stack. Change return types of "value_type&" to -"reference". Change return types of "const value_type&" to -"const_reference". Details:</p> +priority_queue and stack. Change return types of "value_type&" to +"reference". Change return types of "const value_type&" to +"const_reference". Details:</p> <p>Change 23.2.3.1/1 from:</p> -<pre> - namespace std { +<pre> namespace std { template <class T, class Container = deque<T> > class queue { public: @@ -7314,8 +8379,7 @@ priority_queue and stack. Change return types of "value_type&" to <p>to:</p> -<pre> - namespace std { +<pre> namespace std { template <class T, class Container = deque<T> > class queue { public: @@ -7344,8 +8408,7 @@ priority_queue and stack. Change return types of "value_type&" to <p>Change 23.2.3.2/1 from:</p> -<pre> - namespace std { +<pre> namespace std { template <class T, class Container = vector<T>, class Compare = less<typename Container::value_type> > class priority_queue { @@ -7377,8 +8440,7 @@ priority_queue and stack. Change return types of "value_type&" to <p>to:</p> -<pre> - namespace std { +<pre> namespace std { template <class T, class Container = vector<T>, class Compare = less<typename Container::value_type> > class priority_queue { @@ -7412,8 +8474,7 @@ priority_queue and stack. Change return types of "value_type&" to <p>And change 23.2.3.3/1 from:</p> -<pre> - namespace std { +<pre> namespace std { template <class T, class Container = deque<T> > class stack { public: @@ -7457,8 +8518,7 @@ priority_queue and stack. Change return types of "value_type&" to <p>to:</p> -<pre> - namespace std { +<pre> namespace std { template <class T, class Container = deque<T> > class stack { public: @@ -7508,14 +8568,14 @@ and it was deliberately not adopted. Nevertheless, the LWG believes <hr> <a name="308"><h3>308. Table 82 mentions unrelated headers</h3></a><p> -<b>Section:</b> 27 <a href="lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 15 Mar 2001</p> +<b>Section:</b> 27 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.input.output"> [lib.input.output]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 15 Mar 2001</p> <p> Table 82 in section 27 mentions the header <cstdlib> for String -streams (27.7 <a href="lib-iostreams.html#lib.string.streams"> [lib.string.streams]</a>) and the headers <cstdio> and -<cwchar> for File streams (27.8 <a href="lib-iostreams.html#lib.file.streams"> [lib.file.streams]</a>). It's not clear +streams (27.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.string.streams"> [lib.string.streams]</a>) and the headers <cstdio> and +<cwchar> for File streams (27.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.file.streams"> [lib.file.streams]</a>). It's not clear why these headers are mentioned in this context since they do not define any of the library entities described by the -subclauses. According to 17.4.1.1 <a href="lib-intro.html#lib.contents"> [lib.contents]</a>, only such headers +subclauses. According to 17.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.contents"> [lib.contents]</a>, only such headers are to be listed in the summary. </p> <p><b>Proposed resolution:</b></p> @@ -7525,11 +8585,11 @@ Table 82.</p> <p><i>[Copenhagen: changed the proposed resolution slightly. The original proposed resolution also said to remove <cstdio> from Table 82. However, <cstdio> is mentioned several times within -section 27.8 <a href="lib-iostreams.html#lib.file.streams"> [lib.file.streams]</a>, including 27.8.2 <a href="lib-iostreams.html#lib.c.files"> [lib.c.files]</a>.]</i></p> +section 27.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.file.streams"> [lib.file.streams]</a>, including 27.8.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.c.files"> [lib.c.files]</a>.]</i></p> <hr> <a name="310"><h3>310. Is errno a macro?</h3></a><p> -<b>Section:</b> 17.4.1.2 <a href="lib-intro.html#lib.headers"> [lib.headers]</a>, 19.3 <a href="lib-diagnostics.html#lib.errno"> [lib.errno]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 21 Mar 2001</p> +<b>Section:</b> 17.4.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.headers"> [lib.headers]</a>, 19.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-diagnostics.html#lib.errno"> [lib.errno]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Steve Clamage <b>Date:</b> 21 Mar 2001</p> <p> Exactly how should errno be declared in a conforming C++ header? </p> @@ -7539,7 +8599,7 @@ section 27.8 <a href="lib-iostreams.html#lib.file.streams"> [lib.file.streams]</ macro or an identifier with external linkage. In some implementations it can be either, depending on compile-time options. (E.g., on Solaris in multi-threading mode, errno is a macro that expands to a - function call, but is an extern int otherwise. "Unspecified" allows + function call, but is an extern int otherwise. "Unspecified" allows such variability.) </p> @@ -7613,16 +8673,15 @@ not a name is a macro; it must explicitly specify exactly which names are required to be macros. The only one that really works is for it to be a macro.</p> -<p><i>[Curaçao: additional rationale added.]</i></p> +<p><i>[Curaçao: additional rationale added.]</i></p> <hr> <a name="311"><h3>311. Incorrect wording in basic_ostream class synopsis</h3></a><p> -<b>Section:</b> 27.6.2.1 <a href="lib-iostreams.html#lib.ostream"> [lib.ostream]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 21 Mar 2001</p> +<b>Section:</b> 27.6.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream"> [lib.ostream]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 21 Mar 2001</p> -<p>In 27.6.2.1 <a href="lib-iostreams.html#lib.ostream"> [lib.ostream]</a>, the synopsis of class basic_ostream says:</p> +<p>In 27.6.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream"> [lib.ostream]</a>, the synopsis of class basic_ostream says:</p> -<pre> - // partial specializationss +<pre> // partial specializationss template<class traits> basic_ostream<char,traits>& operator<<( basic_ostream<char,traits>&, const char * ); @@ -7630,51 +8689,51 @@ to be a macro.</p> <p>Problems:</p> <ul> -<li>Too many 's's at the end of "specializationss" </li> +<li>Too many 's's at the end of "specializationss" </li> <li>This is an overload, not a partial specialization</li> </ul> <p><b>Proposed resolution:</b></p> -<p>In the synopsis in 27.6.2.1 <a href="lib-iostreams.html#lib.ostream"> [lib.ostream]</a>, remove the +<p>In the synopsis in 27.6.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream"> [lib.ostream]</a>, remove the <i>// partial specializationss</i> comment. Also remove the same comment (correctly spelled, but still incorrect) from the synopsis in -27.6.2.5.4 <a href="lib-iostreams.html#lib.ostream.inserters.character"> [lib.ostream.inserters.character]</a>. +27.6.2.5.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.inserters.character"> [lib.ostream.inserters.character]</a>. </p> <p><i>[ -Pre-Redmond: added 27.6.2.5.4 <a href="lib-iostreams.html#lib.ostream.inserters.character"> [lib.ostream.inserters.character]</a> because of Martin's +Pre-Redmond: added 27.6.2.5.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.inserters.character"> [lib.ostream.inserters.character]</a> because of Martin's comment in c++std-lib-8939. ]</i></p> <hr> -<a name="312"><h3>312. Table 27 is missing headers</h3></a><p> -<b>Section:</b> 20 <a href="lib-utilities.html#lib.utilities"> [lib.utilities]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 29 Mar 2001</p> +<a name="312"></a><h3><a name="312">312. Table 27 is missing headers</a></h3><p> +<b>Section:</b> 20 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.utilities"> [lib.utilities]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 29 Mar 2001</p> <p>Table 27 in section 20 lists the header <memory> (only) for Memory (lib.memory) but neglects to mention the headers -<cstdlib> and <cstring> that are discussed in 20.4.6 <a href="lib-utilities.html#lib.c.malloc"> [lib.c.malloc]</a>.</p> +<cstdlib> and <cstring> that are discussed in 20.4.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-utilities.html#lib.c.malloc"> [lib.c.malloc]</a>.</p> <p><b>Proposed resolution:</b></p> <p>Add <cstdlib> and <cstring> to Table 27, in the same row as <memory>.</p> <hr> -<a name="315"><h3>315. Bad "range" in list::unique complexity</h3></a><p> -<b>Section:</b> 23.2.2.4 <a href="lib-containers.html#lib.list.ops"> [lib.list.ops]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 1 May 2001</p> +<a name="315"><h3>315. Bad "range" in list::unique complexity</h3></a><p> +<b>Section:</b> 23.2.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.ops"> [lib.list.ops]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 1 May 2001</p> <p> -23.2.2.4 <a href="lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, Para 21 describes the complexity of -list::unique as: "If the range (last - first) is not empty, exactly +23.2.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.ops"> [lib.list.ops]</a>, Para 21 describes the complexity of +list::unique as: "If the range (last - first) is not empty, exactly (last - first) -1 applications of the corresponding predicate, -otherwise no applications of the predicate)". +otherwise no applications of the predicate)". </p> <p> -"(last - first)" is not a range. +"(last - first)" is not a range. </p> <p><b>Proposed resolution:</b></p> <p> -Change the "range" from (last - first) to [first, last). +Change the "range" from (last - first) to [first, last). </p> <hr> <a name="316"><h3>316. Vague text in Table 69</h3></a><p> -<b>Section:</b> 23.1.2 <a href="lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 4 May 2001</p> +<b>Section:</b> 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 4 May 2001</p> <p>Table 69 says this about a_uniq.insert(t):</p> <blockquote> @@ -7695,7 +8754,7 @@ takes place... </blockquote> <hr> <a name="317"><h3>317. Instantiation vs. specialization of facets</h3></a><p> -<b>Section:</b> 22 <a href="lib-locales.html#lib.localization"> [lib.localization]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 4 May 2001</p> +<b>Section:</b> 22 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.localization"> [lib.localization]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 4 May 2001</p> <p> The localization section of the standard refers to specializations of the facet templates as instantiations even though the required facets @@ -7745,12 +8804,11 @@ but the wording in clause 22 was never updated to reflect that change.</p> <hr> <a name="318"><h3>318. Misleading comment in definition of numpunct_byname</h3></a><p> -<b>Section:</b> 22.2.3.2 <a href="lib-locales.html#lib.locale.numpunct.byname"> [lib.locale.numpunct.byname]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 12 May 2001</p> +<b>Section:</b> 22.2.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.numpunct.byname"> [lib.locale.numpunct.byname]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 12 May 2001</p> <p>The definition of the numpunct_byname template contains the following comment:</p> -<pre> - namespace std { +<pre> namespace std { template <class charT> class numpunct_byname : public numpunct<charT> { // this class is specialized for char and wchar_t. @@ -7762,24 +8820,24 @@ conceivable that an implementation will not explicitly specialize the template at all, but simply provide the primary template.</p> <p><b>Proposed resolution:</b></p> <p>Remove the comment from the text in 22.2.3.2 and from the proposed -resolution of library issue <a href="lwg-defects.html#228">228</a>.</p> +resolution of library issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#228">228</a>.</p> <hr> -<a name="319"><h3>319. Storage allocation wording confuses "Required behavior", "Requires"</h3></a><p> -<b>Section:</b> 18.4.1.1 <a href="lib-support.html#lib.new.delete.single"> [lib.new.delete.single]</a>, 18.4.1.2 <a href="lib-support.html#lib.new.delete.array"> [lib.new.delete.array]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 15 May 2001</p> -<p>The standard specifies 17.3.1.3 <a href="lib-intro.html#lib.structure.specifications"> [lib.structure.specifications]</a> that "Required -behavior" elements describe "the semantics of a function definition -provided by either the implementation or a C++ program."</p> +<a name="319"></a><h3><a name="319">319. Storage allocation wording confuses "Required behavior", "Requires"</a></h3><p> +<b>Section:</b> 18.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete.single"> [lib.new.delete.single]</a>, 18.4.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete.array"> [lib.new.delete.array]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Beman Dawes <b>Date:</b> 15 May 2001</p> +<p>The standard specifies 17.3.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.structure.specifications"> [lib.structure.specifications]</a> that "Required +behavior" elements describe "the semantics of a function definition +provided by either the implementation or a C++ program."</p> -<p>The standard specifies 17.3.1.3 <a href="lib-intro.html#lib.structure.specifications"> [lib.structure.specifications]</a> that "Requires" -elements describe "the preconditions for calling the function."</p> +<p>The standard specifies 17.3.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.structure.specifications"> [lib.structure.specifications]</a> that "Requires" +elements describe "the preconditions for calling the function."</p> <p>In the sections noted below, the current wording specifies -"Required Behavior" for what are actually preconditions, and thus -should be specified as "Requires".</p> +"Required Behavior" for what are actually preconditions, and thus +should be specified as "Requires".</p> <p><b>Proposed resolution:</b></p> -<p>In 18.4.1.1 <a href="lib-support.html#lib.new.delete.single"> [lib.new.delete.single]</a> Para 12 Change:</p> +<p>In 18.4.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete.single"> [lib.new.delete.single]</a> Para 12 Change:</p> <blockquote> <p>Required behavior: accept a value of ptr that is null or that was returned by an earlier call ...</p> @@ -7790,7 +8848,7 @@ should be specified as "Requires".</p> earlier call ...</p> </blockquote> -<p>In 18.4.1.2 <a href="lib-support.html#lib.new.delete.array"> [lib.new.delete.array]</a> Para 11 Change:</p> +<p>In 18.4.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.new.delete.array"> [lib.new.delete.array]</a> Para 11 Change:</p> <blockquote> <p>Required behavior: accept a value of ptr that is null or that was returned by an earlier call ...</p> @@ -7802,24 +8860,108 @@ should be specified as "Requires".</p> </blockquote> <hr> +<a name="320"><h3>320. list::assign overspecified</h3></a><p> +<b>Section:</b> 23.2.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.list.cons"> [lib.list.cons]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Howard Hinnant <b>Date:</b> 17 May 2001</p> +<p> +Section 23.2.2.1, paragraphs 6-8 specify that list assign (both forms) have +the "effects" of a call to erase followed by a call to insert. +</p> + +<p> +I would like to document that implementers have the freedom to implement +assign by other methods, as long as the end result is the same and the +exception guarantee is as good or better than the basic guarantee. +</p> + +<p> +The motivation for this is to use T's assignment operator to recycle +existing nodes in the list instead of erasing them and reallocating +them with new values. It is also worth noting that, with careful +coding, most common cases of assign (everything but assignment with +true input iterators) can elevate the exception safety to strong if +T's assignment has a nothrow guarantee (with no extra memory cost). +Metrowerks does this. However I do not propose that this subtlety be +standardized. It is a QoI issue. </p> + +<p>Existing practise: +Metrowerks and SGI recycle nodes, Dinkumware and Rogue Wave don't. +</p> +<p><b>Proposed resolution:</b></p> +<p>Change 23.2.2.1/7 from:</p> + +<blockquote> +<p>Effects:</p> + +<pre> erase(begin(), end()); + insert(begin(), first, last); +</pre> +</blockquote> + +<p>to:</p> + +<blockquote> +<p>Effects: Replaces the contents of the list with the range [first, last).</p> +</blockquote> + +<p>In 23.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.sequence.reqmts"> [lib.sequence.reqmts]</a>, in Table 67 (sequence requirements), +add two new rows:</p> +<pre> a.assign(i,j) void pre: i,j are not iterators into a. + Replaces elements in a with a copy + of [i, j). + + a.assign(n,t) void pre: t is not a reference into a. + Replaces elements in a with n copies + of t. +</pre> + +<p>Change 23.2.2.1/8 from:</p> + +<blockquote> +<p>Effects:</p> +<pre> erase(begin(), end()); + insert(begin(), n, t); +</pre> +</blockquote> +<p>to:</p> + +<blockquote> +<p>Effects: Replaces the contents of the list with n copies of t.</p> +</blockquote> + +<p><i>[Redmond: Proposed resolution was changed slightly. Previous +version made explicit statement about exception safety, which wasn't +consistent with the way exception safety is expressed elsewhere. +Also, the change in the sequence requirements is new. Without that +change, the proposed resolution would have required that assignment of +a subrange would have to work. That too would have been +overspecification; it would effectively mandate that assignment use a +temporary. Howard provided wording. +]</i></p> + +<p><i>[Curaçao: Made editorial improvement in wording; changed +"Replaces elements in a with copies of elements in [i, j)." +with "Replaces the elements of a with a copy of [i, j)." +Changes not deemed serious enough to requre rereview.]</i></p> + +<hr> <a name="321"><h3>321. Typo in num_get</h3></a><p> -<b>Section:</b> 22.2.2.1.2 <a href="lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Kevin Djang <b>Date:</b> 17 May 2001</p> +<b>Section:</b> 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Kevin Djang <b>Date:</b> 17 May 2001</p> <p> -Section 22.2.2.1.2 at p7 states that "A length specifier is added to -the conversion function, if needed, as indicated in Table 56." -However, Table 56 uses the term "length modifier", not "length -specifier". +Section 22.2.2.1.2 at p7 states that "A length specifier is added to +the conversion function, if needed, as indicated in Table 56." +However, Table 56 uses the term "length modifier", not "length +specifier". </p> <p><b>Proposed resolution:</b></p> <p> -In 22.2.2.1.2 at p7, change the text "A length specifier is added ..." -to be "A length modifier is added ..." +In 22.2.2.1.2 at p7, change the text "A length specifier is added ..." +to be "A length modifier is added ..." </p> <p><b>Rationale:</b></p> -<p>C uses the term "length modifier". We should be consistent.</p> +<p>C uses the term "length modifier". We should be consistent.</p> <hr> <a name="322"><h3>322. iterator and const_iterator should have the same value type</h3></a><p> -<b>Section:</b> 23.1 <a href="lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 17 May 2001</p> +<b>Section:</b> 23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Matt Austern <b>Date:</b> 17 May 2001</p> <p> It's widely assumed that, if X is a container, iterator_traits<X::iterator>::value_type and @@ -7827,16 +8969,16 @@ iterator_traits<X::const_iterator>::value_type should both be X::value_type. However, this is nowhere stated. The language in Table 65 is not precise about the iterators' value types (it predates iterator_traits), and could even be interpreted as saying that -iterator_traits<X::const_iterator>::value_type should be "const -X::value_type". +iterator_traits<X::const_iterator>::value_type should be "const +X::value_type". </p> -<p>Related issue: <a href="lwg-closed.html#279">279</a>.</p> +<p>Related issue: <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-closed.html#279">279</a>.</p> <p><b>Proposed resolution:</b></p> -<p>In Table 65 ("Container Requirements"), change the return type for -X::iterator to "iterator type whose value type is T". Change the -return type for X::const_iterator to "constant iterator type whose -value type is T".</p> +<p>In Table 65 ("Container Requirements"), change the return type for +X::iterator to "iterator type whose value type is T". Change the +return type for X::const_iterator to "constant iterator type whose +value type is T".</p> <p><b>Rationale:</b></p> <p> This belongs as a container requirement, rather than an iterator @@ -7846,13 +8988,186 @@ pairs is specific to containers' iterator. <p> It is existing practice that (for example) iterator_traits<list<int>::const_iterator>::value_type -is "int", rather than "const int". This is consistent with +is "int", rather than "const int". This is consistent with the way that const pointers are handled: the standard already requires that iterator_traits<const int*>::value_type is int. </p> <hr> +<a name="324"><h3>324. Do output iterators have value types?</h3></a><p> +<b>Section:</b> 24.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.output.iterators"> [lib.output.iterators]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Dave Abrahams <b>Date:</b> 7 June 2001</p> + +<p>Table 73 suggests that output iterators have value types. It +requires the expression "*a = t". Additionally, although Table 73 +never lists "a = t" or "X(a) = t" in the "expressions" column, it +contains a note saying that "a = t" and "X(a) = t" have equivalent +(but nowhere specified!) semantics.</p> + +<p>According to 24.1/9, t is supposed to be "a value of value type +T":</p> + + <blockquote> + In the following sections, a and b denote values of X, n denotes a + value of the difference type Distance, u, tmp, and m denote + identifiers, r denotes a value of X&, t denotes a value of + value type T. + </blockquote> + +<p>Two other parts of the standard that are relevant to whether +output iterators have value types:</p> + +<ul> + <li>24.1/1 says "All iterators i support the expression *i, + resulting in a value of some class, enumeration, or built-in type + T, called the value type of the iterator".</li> + + <li> + 24.3.1/1, which says "In the case of an output iterator, the types + iterator_traits<Iterator>::difference_type + iterator_traits<Iterator>::value_type are both defined as void." + </li> +</ul> + +<p>The first of these passages suggests that "*i" is supposed to +return a useful value, which contradicts the note in 24.1.2/2 saying +that the only valid use of "*i" for output iterators is in an +expression of the form "*i = t". The second of these passages appears +to contradict Table 73, because it suggests that "*i"'s return value +should be void. The second passage is also broken in the case of a an +iterator type, like non-const pointers, that satisfies both the output +iterator requirements and the forward iterator requirements.</p> + +<p>What should the standard say about <tt>*i</tt>'s return value when +i is an output iterator, and what should it say about that t is in the +expression "*i = t"? Finally, should the standard say anything about +output iterators' pointer and reference types?</p> + +<p><b>Proposed resolution:</b></p> +<p>24.1 p1, change</p> + +<blockquote> +<p>All iterators <tt>i</tt> support the expression <tt>*i</tt>, resulting +in a value of some class, enumeration, or built-in type <tt>T</tt>, +called the value type of the iterator.</p> +</blockquote> + +<p>to</p> + +<blockquote> +<p>All input iterators <tt>i</tt> support the expression <tt>*i</tt>, +resulting in a value of some class, enumeration, or built-in type +<tt>T</tt>, called the value type of the iterator. All output +iterators support the expression <tt>*i = o</tt> where <tt>o</tt> is a +value of some type that is in the set of types that are <i>writable</i> to +the particular iterator type of <tt>i</tt>. +</p> +</blockquote> + +<p>24.1 p9, add</p> + +<blockquote> +<p> +<tt>o</tt> denotes a value of some type that is writable to the +output iterator. +</p> +</blockquote> + +<p>Table 73, change</p> + +<blockquote> +<pre>*a = t +</pre> +</blockquote> + +<p>to</p> + +<blockquote> +<pre>*r = o +</pre> +</blockquote> + +<p>and change</p> + +<blockquote> +<pre>*r++ = t +</pre> +</blockquote> + +<p>to</p> + +<blockquote> +<pre>*r++ = o +</pre> +</blockquote> + +<p><i>[post-Redmond: Jeremy provided wording]</i></p> + +<p><b>Rationale:</b></p> +<p>The LWG considered two options: change all of the language that +seems to imply that output iterators have value types, thus making it +clear that output iterators have no value types, or else define value +types for output iterator consistently. The LWG chose the former +option, because it seems clear that output iterators were never +intended to have value types. This was a deliberate design decision, +and any language suggesting otherwise is simply a mistake.</p> + +<p>A future revision of the standard may wish to revisit this design +decision.</p> +<hr> +<a name="325"><h3>325. Misleading text in moneypunct<>::do_grouping</h3></a><p> +<b>Section:</b> 22.2.6.3.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.moneypunct.virtuals"> [lib.locale.moneypunct.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 02 Jul 2001</p> +<p>The Returns clause in 22.2.6.3.2, p3 says about +moneypunct<charT>::do_grouping() +</p> + +<blockquote> + Returns: A pattern defined identically as the result of + numpunct<charT>::do_grouping().241) +</blockquote> + +<p>Footnote 241 then reads</p> + +<blockquote> + This is most commonly the value "\003" (not "3"). +</blockquote> + +<p> +The returns clause seems to imply that the two member functions must +return an identical value which in reality may or may not be true, +since the facets are usually implemented in terms of struct std::lconv +and return the value of the grouping and mon_grouping, respectively. +The footnote also implies that the member function of the moneypunct +facet (rather than the overridden virtual functions in moneypunct_byname) +most commonly return "\003", which contradicts the C standard which +specifies the value of "" for the (most common) C locale. +</p> + +<p><b>Proposed resolution:</b></p> +<p>Replace the text in Returns clause in 22.2.6.3.2, p3 with the following:</p> + +<blockquote> + Returns: A pattern defined identically as, but not necessarily + equal to, the result of numpunct<charT>::do_grouping().241) +</blockquote> + +<p>and replace the text in Footnote 241 with the following:</p> + +<blockquote> + To specify grouping by 3s the value is "\003", not "3". +</blockquote> +<p><b>Rationale:</b></p> +<p> +The fundamental problem is that the description of the locale facet +virtuals serves two purposes: describing the behavior of the base +class, and describing the meaning of and constraints on the behavior +in arbitrary derived classes. The new wording makes that separation a +little bit clearer. The footnote (which is nonnormative) is not +supposed to say what the grouping is in the "C" locale or in any other +locale. It is just a reminder that the values are interpreted as small +integers, not ASCII characters. +</p> +<hr> <a name="327"><h3>327. Typo in time_get facet in table 52</h3></a><p> -<b>Section:</b> 22.1.1.1.1 <a href="lib-locales.html#lib.locale.category"> [lib.locale.category]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Tiki Wan <b>Date:</b> 06 Jul 2001</p> +<b>Section:</b> 22.1.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.category"> [lib.locale.category]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Tiki Wan <b>Date:</b> 06 Jul 2001</p> <p>The <tt>wchar_t</tt> versions of <tt>time_get</tt> and <tt>time_get_byname</tt> are listed incorrectly in table 52, required instantiations. In both cases the second template @@ -7861,14 +9176,12 @@ InputIterator, since these are input facets.</p> <p><b>Proposed resolution:</b></p> <p> In table 52, required instantiations, in -22.1.1.1.1 <a href="lib-locales.html#lib.locale.category"> [lib.locale.category]</a>, change</p> -<pre> - time_get<wchar_t, OutputIterator> +22.1.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.category"> [lib.locale.category]</a>, change</p> +<pre> time_get<wchar_t, OutputIterator> time_get_byname<wchar_t, OutputIterator> </pre> <p>to</p> -<pre> - time_get<wchar_t, InputIterator> +<pre> time_get<wchar_t, InputIterator> time_get_byname<wchar_t, InputIterator> </pre> @@ -7877,30 +9190,110 @@ a typo, wchart instead of wchar_t.]</i></p> <hr> <a name="328"><h3>328. Bad sprintf format modifier in money_put<>::do_put()</h3></a><p> -<b>Section:</b> 22.2.6.2.2 <a href="lib-locales.html#lib.locale.money.put.virtuals"> [lib.locale.money.put.virtuals]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 07 Jul 2001</p> -<p>The sprintf format string , "%.01f" (that's the digit one), in the +<b>Section:</b> 22.2.6.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.money.put.virtuals"> [lib.locale.money.put.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 07 Jul 2001</p> +<p>The sprintf format string , "%.01f" (that's the digit one), in the description of the do_put() member functions of the money_put facet in 22.2.6.2.2, p1 is incorrect. First, the f format specifier is wrong for values of type long double, and second, the precision of 01 doesn't seem to make sense. What was most likely intended was -"%.0Lf"., that is a precision of zero followed by the L length +"%.0Lf"., that is a precision of zero followed by the L length modifier.</p> <p><b>Proposed resolution:</b></p> -<p>Change the format string to "%.0Lf".</p> +<p>Change the format string to "%.0Lf".</p> <p><b>Rationale:</b></p> <p>Fixes an obvious typo</p> <hr> +<a name="329"><h3>329. vector capacity, reserve and reallocation</h3></a><p> +<b>Section:</b> 23.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a>, 23.2.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.modifiers"> [lib.vector.modifiers]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Anthony Williams <b>Date:</b> 13 Jul 2001</p> +<p> +There is an apparent contradiction about which circumstances can cause +a reallocation of a vector in Section 23.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a> and +section 23.2.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.modifiers"> [lib.vector.modifiers]</a>. +</p> + +<p>23.2.4.2p5 says:</p> +<blockquote> +Notes: Reallocation invalidates all the references, pointers, and iterators +referring to the elements in the sequence. It is guaranteed that no +reallocation takes place during insertions that happen after a call to +reserve() until the time when an insertion would make the size of the vector +greater than the size specified in the most recent call to reserve(). +</blockquote> + +<p>Which implies if I do</p> + +<pre> std::vector<int> vec; + vec.reserve(23); + vec.reserve(0); + vec.insert(vec.end(),1); +</pre> + +<p>then the implementation may reallocate the vector for the insert, +as the size specified in the previous call to reserve was zero.</p> + +<p>However, the previous paragraphs (23.2.4.2, p1-2) state:</p> +<blockquote> +<p> +(capacity) Returns: The total number of elements the vector +can hold without requiring reallocation +</p> +<p> +...After reserve(), capacity() is greater or equal to the +argument of reserve if reallocation happens; and equal to the previous value +of capacity() otherwise... +</p> +</blockquote> + +<p> +This implies that vec.capacity() is still 23, and so the insert() +should not require a reallocation, as vec.size() is 0. This is backed +up by 23.2.4.3p1: +</p> +<blockquote> +(insert) Notes: Causes reallocation if the new size is greater than the old +capacity. +</blockquote> + +<p> +Though this doesn't rule out reallocation if the new size is less +than the old capacity, I think the intent is clear. +</p> + +<p><b>Proposed resolution:</b></p> +<p>Change the wording of 23.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a> paragraph 5 to:</p> + +<blockquote> +Notes: Reallocation invalidates all the references, pointers, and +iterators referring to the elements in the sequence. It is guaranteed +that no reallocation takes place during insertions that happen after a +call to reserve() until the time when an insertion would make the size +of the vector greater than the value of capacity(). +</blockquote> + +<p><i>[Redmond: original proposed resolution was modified slightly. In +the original, the guarantee was that there would be no reallocation +until the size would be greater than the value of capacity() after the +most recent call to reserve(). The LWG did not believe that the +"after the most recent call to reserve()" added any useful +information.]</i></p> + +<p><b>Rationale:</b></p> +<p>There was general agreement that, when reserve() is called twice in +succession and the argument to the second invocation is smaller than +the argument to the first, the intent was for the second invocation to +have no effect. Wording implying that such cases have an effect on +reallocation guarantees was inadvertant.</p> +<hr> <a name="331"><h3>331. bad declaration of destructor for ios_base::failure</h3></a><p> -<b>Section:</b> 27.4.2.1.1 <a href="lib-iostreams.html#lib.ios::failure"> [lib.ios::failure]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> PremAnand M. Rao <b>Date:</b> 23 Aug 2001</p> +<b>Section:</b> 27.4.2.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios::failure"> [lib.ios::failure]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> PremAnand M. Rao <b>Date:</b> 23 Aug 2001</p> <p> -With the change in 17.4.4.8 <a href="lib-intro.html#lib.res.on.exception.handling"> [lib.res.on.exception.handling]</a> to state - "An implementation may strengthen the exception-specification for a - non-virtual function by removing listed exceptions." -(issue <a href="lwg-defects.html#119">119</a>) +With the change in 17.4.4.8 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.res.on.exception.handling"> [lib.res.on.exception.handling]</a> to state + "An implementation may strengthen the exception-specification for a + non-virtual function by removing listed exceptions." +(issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#119">119</a>) and the following declaration of ~failure() in ios_base::failure </p> -<pre> - namespace std { +<pre> namespace std { class ios_base::failure : public exception { public: ... @@ -7909,10 +9302,9 @@ and the following declaration of ~failure() in ios_base::failure }; } </pre> -<p>the class failure cannot be implemented since in 18.6.1 <a href="lib-support.html#lib.exception"> [lib.exception]</a> the destructor of class exception has an empty +<p>the class failure cannot be implemented since in 18.6.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.exception"> [lib.exception]</a> the destructor of class exception has an empty exception specification:</p> -<pre> - namespace std { +<pre> namespace std { class exception { public: ... @@ -7927,14 +9319,157 @@ exception specification:</p> <p>The proposed resolution is consistent with the way that destructors of other classes derived from <tt>exception</tt> are handled.</p> <hr> +<a name="333"><h3>333. does endl imply synchronization with the device?</h3></a><p> +<b>Section:</b> 27.6.2.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.manip"> [lib.ostream.manip]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> PremAnand M. Rao <b>Date:</b> 27 Aug 2001</p> +<p>A footnote in 27.6.2.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.manip"> [lib.ostream.manip]</a> states:</p> +<blockquote> + [Footnote: The effect of executing cout << endl is to insert a + newline character in the output sequence controlled by cout, then + synchronize it with any external file with which it might be + associated. --- end foonote] +</blockquote> + +<p> +Does the term "file" here refer to the external device? +This leads to some implementation ambiguity on systems with fully +buffered files where a newline does not cause a flush to the device. +</p> + +<p> +Choosing to sync with the device leads to significant performance +penalties for each call to endl, while not sync-ing leads to +errors under special circumstances. +</p> + +<p> +I could not find any other statement that explicitly defined +the behavior one way or the other. +</p> +<p><b>Proposed resolution:</b></p> +<p>Remove footnote 300 from section 27.6.2.7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.manip"> [lib.ostream.manip]</a>.</p> +<p><b>Rationale:</b></p> +<p>We already have normative text saying what <tt>endl</tt> does: it +inserts a newline character and calls <tt>flush</tt>. This footnote +is at best redundant, at worst (as this issue says) misleading, +because it appears to make promises about what <tt>flush</tt> +does.</p> +<hr> +<a name="334"><h3>334. map::operator[] specification forces inefficient implementation</h3></a><p> +<b>Section:</b> 23.3.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.map.access"> [lib.map.access]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Andrea Griffini <b>Date:</b> 02 Sep 2001</p> +<p> +The current standard describes map::operator[] using a +code example. That code example is however quite +inefficient because it requires several useless copies +of both the passed key_type value and of default +constructed mapped_type instances. +My opinion is that was not meant by the comitee to +require all those temporary copies. +</p> + +<p>Currently map::operator[] behaviour is specified as: </p> +<pre> Returns: + (*((insert(make_pair(x, T()))).first)).second. +</pre> + +<p> +This specification however uses make_pair that is a +template function of which parameters in this case +will be deduced being of type const key_type& and +const T&. This will create a pair<key_type,T> that +isn't the correct type expected by map::insert so +another copy will be required using the template +conversion constructor available in pair to build +the required pair<const key_type,T> instance. +</p> + +<p>If we consider calling of key_type copy constructor +and mapped_type default constructor and copy +constructor as observable behaviour (as I think we +should) then the standard is in this place requiring +two copies of a key_type element plus a default +construction and two copy construction of a mapped_type +(supposing the addressed element is already present +in the map; otherwise at least another copy +construction for each type). +</p> + +<p>A simple (half) solution would be replacing the description with:</p> +<pre> Returns: + (*((insert(value_type(x, T()))).first)).second. +</pre> + +<p>This will remove the wrong typed pair construction that +requires one extra copy of both key and value.</p> + +<p>However still the using of map::insert requires temporary +objects while the operation, from a logical point of view, +doesn't require any. </p> + +<p>I think that a better solution would be leaving free an +implementer to use a different approach than map::insert +that, because of its interface, forces default constructed +temporaries and copies in this case. +The best solution in my opinion would be just requiring +map::operator[] to return a reference to the mapped_type +part of the contained element creating a default element +with the specified key if no such an element is already +present in the container. Also a logarithmic complexity +requirement should be specified for the operation. +</p> + +<p> +This would allow library implementers to write alternative +implementations not using map::insert and reaching optimal +performance in both cases of the addressed element being +present or absent from the map (no temporaries at all and +just the creation of a new pair inside the container if +the element isn't present). +Some implementer has already taken this option but I think +that the current wording of the standard rules that as +non-conforming. +</p> + +<p><b>Proposed resolution:</b></p> + +<p> +Replace 23.3.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.map.access"> [lib.map.access]</a> paragraph 1 with +</p> +<blockquote> +<p> +-1- Effects: If there is no key equivalent to x in the map, inserts +value_type(x, T()) into the map. +</p> +<p> +-2- Returns: A reference to the mapped_type corresponding to x in *this. +</p> +<p> +-3- Complexity: logarithmic. +</p> +</blockquote> + +<p><i>[This is the second option mentioned above. Howard provided +wording. We may also wish to have a blanket statement somewhere in +clause 17 saying that we do not intend the semantics of sample code +fragments to be interpreted as specifing exactly how many copies are +made. See issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#98">98</a> for a similar problem.]</i></p> + +<p><b>Rationale:</b></p> +<p> +This is the second solution described above; as noted, it is +consistent with existing practice. +</p> + +<p>Note that we now need to specify the complexity explicitly, because +we are no longer defining <tt>operator[]</tt> in terms of +<tt>insert</tt>.</p> +<hr> <a name="335"><h3>335. minor issue with char_traits, table 37</h3></a><p> -<b>Section:</b> 21.1.1 <a href="lib-strings.html#lib.char.traits.require"> [lib.char.traits.require]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 06 Sep 2001</p> +<b>Section:</b> 21.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.char.traits.require"> [lib.char.traits.require]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 06 Sep 2001</p> <p> -Table 37, in 21.1.1 <a href="lib-strings.html#lib.char.traits.require"> [lib.char.traits.require]</a>, descibes char_traits::assign +Table 37, in 21.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.char.traits.require"> [lib.char.traits.require]</a>, descibes char_traits::assign as: </p> -<pre> - X::assign(c,d) assigns c = d. +<pre> X::assign(c,d) assigns c = d. </pre> <p>And para 1 says:</p> @@ -7951,8 +9486,7 @@ assign, at least), 'c' is intended to be a reference type. <p>I did a quick survey of the four implementations I happened to have lying around, and sure enough they all have signatures:</p> -<pre> - assign( charT&, const charT& ); +<pre> assign( charT&, const charT& ); </pre> <p>(or the equivalent). It's also described this way in Nico's book. @@ -7966,35 +9500,311 @@ and char_traits<wchar_t> in 21.1.3.2...) </blockquote> <p>and change the description of assign in the table to:</p> -<pre> - X::assign(r,d) assigns r = d +<pre> X::assign(r,d) assigns r = d </pre> <hr> +<a name="336"><h3>336. Clause 17 lack of references to deprecated headers</h3></a><p> +<b>Section:</b> 17 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.library"> [lib.library]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Detlef Vollmann <b>Date:</b> 05 Sep 2001</p> +<p>From c++std-edit-873:</p> + +<p>17.4.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.headers"> [lib.headers]</a>, Table 11. In this table, the header +<strstream> is missing.</p> + +<p>This shows a general problem: The whole clause 17 refers quite +often to clauses 18 through 27, but D.7 is also a part of the standard +library (though a deprecated one).</p> + +<p><b>Proposed resolution:</b></p> + +<p>To 17.4.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.headers"> [lib.headers]</a> Table 11, C++ Library Headers, add +"<strstream>".</p> + +<p>In the following places, change "clauses 17 through 27" to "clauses +17 through 27 and Annex D":</p> + +<ul> +<li>1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/intro.html#intro.refs"> [intro.refs]</a> Normative references/1/footnote 1</li> +<li>1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/intro.html#intro.defs"> [intro.defs]</a> Definitions/1</li> +<li>7 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/dcl.html#dcl.dcl"> [dcl.dcl]</a> Library introduction/9</li> +<li>17.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.description"> [lib.description]</a> Method of description (Informative)/1</li> +<li>17.3.2.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.character.seq"> [lib.character.seq]</a> Character sequences/1/bullet 2</li> +<li>17.3.2.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.functions.within.classes"> [lib.functions.within.classes]</a> Functions within classes/1</li> +<li>17.3.2.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.objects.within.classes"> [lib.objects.within.classes]</a> Private members/1/(2 places)</li> +<li>17.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.requirements"> [lib.requirements]</a> Library-wide requirements/1</li> +<li>17.4.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.headers"> [lib.headers]</a> Headers/4</li> +<li>17.4.3.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.replacement.functions"> [lib.replacement.functions]</a> Replacement functions/1</li> +<li>17.4.4.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.global.functions"> [lib.global.functions]</a> Global or non-member functions/2</li> +<li>17.4.4.6 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.protection.within.classes"> [lib.protection.within.classes]</a> Protection within classes/1</li> +</ul> + + +<hr> <a name="337"><h3>337. replace_copy_if's template parameter should be InputIterator</h3></a><p> -<b>Section:</b> 25.2.4 <a href="lib-algorithms.html#lib.alg.replace"> [lib.alg.replace]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Detlef Vollmann <b>Date:</b> 07 Sep 2001</p> +<b>Section:</b> 25.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.replace"> [lib.alg.replace]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Detlef Vollmann <b>Date:</b> 07 Sep 2001</p> <p>From c++std-edit-876:</p> <p> -In section 25.2.4 <a href="lib-algorithms.html#lib.alg.replace"> [lib.alg.replace]</a> before p4: The name of the first -parameter of template replace_copy_if should be "InputIterator" -instead of "Iterator". According to 17.3.2.1 <a href="lib-intro.html#lib.type.descriptions"> [lib.type.descriptions]</a> p1 the +In section 25.2.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-algorithms.html#lib.alg.replace"> [lib.alg.replace]</a> before p4: The name of the first +parameter of template replace_copy_if should be "InputIterator" +instead of "Iterator". According to 17.3.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.type.descriptions"> [lib.type.descriptions]</a> p1 the parameter name conveys real normative meaning. </p> <p><b>Proposed resolution:</b></p> <p>Change <tt>Iterator</tt> to <tt>InputIterator</tt>.</p> <hr> +<a name="338"><h3>338. is whitespace allowed between `-' and a digit?</h3></a><p> +<b>Section:</b> 22.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.categories"> [lib.locale.categories]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 17 Sep 2001</p> +<p> +From Stage 2 processing in 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a>, p8 and 9 (the +original text or the text corrected by the proposed resolution of +issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#221">221</a>) it seems clear that no whitespace is allowed +within a number, but 22.2.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.numpunct"> [lib.locale.numpunct]</a>, p2, which gives the +format for integer and floating point values, says that whitespace is +optional between a plusminus and a sign. +</p> + +<p> +The text needs to be clarified to either consistently allow or +disallow whitespace between a plusminus and a sign. It might be +worthwhile to consider the fact that the C library stdio facility does +not permit whitespace embedded in numbers and neither does the C or +C++ core language (the syntax of integer-literals is given in 2.13.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lex.html#lex.icon"> [lex.icon]</a>, that of floating-point-literals in 2.13.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lex.html#lex.fcon"> [lex.fcon]</a> of the C++ standard). +</p> +<p><b>Proposed resolution:</b></p> +<p>Change the first part of 22.2.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.numpunct"> [lib.locale.numpunct]</a> paragraph 2 from:</p> +<blockquote> +<p> +The syntax for number formats is as follows, where <tt>digit</tt> +represents the radix set specified by the <tt>fmtflags</tt> argument +value, <tt>whitespace</tt> is as determined by the facet +<tt>ctype<charT></tt> (22.2.1.1), and <tt>thousands-sep</tt> and +<tt>decimal-point</tt> are the results of corresponding +<tt>numpunct<charT></tt> members. Integer values have the +format: +</p> +<pre> integer ::= [sign] units + sign ::= plusminus [whitespace] + plusminus ::= '+' | '-' + units ::= digits [thousands-sep units] + digits ::= digit [digits] +</pre> +</blockquote> +<p>to:</p> +<blockquote> +<p> +The syntax for number formats is as follows, where <tt>digit</tt> +represents the radix set specified by the <tt>fmtflags</tt> argument +value, and <tt>thousands-sep</tt> and <tt>decimal-point</tt> are the +results of corresponding <tt>numpunct<charT></tt> members. +Integer values have the format: +</p> +<pre> integer ::= [sign] units + sign ::= plusminus + plusminus ::= '+' | '-' + units ::= digits [thousands-sep units] + digits ::= digit [digits] +</pre> +</blockquote> +<p><b>Rationale:</b></p> +<p>It's not clear whether the format described in 22.2.3.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.numpunct"> [lib.locale.numpunct]</a> paragraph 2 has any normative weight: nothing in the +standard says how, or whether, it's used. However, there's no reason +for it to differ gratuitously from the very specific description of +numeric processing in 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a>. The proposed +resolution removes all mention of "whitespace" from that format.</p> +<hr> +<a name="339"><h3>339. definition of bitmask type restricted to clause 27</h3></a><p> +<b>Section:</b> 22.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.category.ctype"> [lib.category.ctype]</a>, 17.3.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.bitmask.types"> [lib.bitmask.types]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 17 September 2001</p> +<p> +The ctype_category::mask type is declared to be an enum in 22.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.category.ctype"> [lib.category.ctype]</a> with p1 then stating that it is a bitmask type, most +likely referring to the definition of bitmask type in 17.3.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.bitmask.types"> [lib.bitmask.types]</a>, p1. However, the said definition only applies to +clause 27, making the reference in 22.2.1 somewhat dubious. +</p> +<p><b>Proposed resolution:</b></p> +<p>Clarify 17.3.2.1.2, p1 by changing the current text from</p> + <blockquote> + Several types defined in clause 27 are bitmask types. Each bitmask type + can be implemented as an enumerated type that overloads certain operators, + as an integer type, or as a bitset (23.3.5 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.template.bitset"> [lib.template.bitset]</a>). + </blockquote> +<p>to read</p> + <blockquote> + Several types defined in clauses lib.language.support through + lib.input.output and Annex D are bitmask types. Each bitmask type can + be implemented as an enumerated type that overloads certain operators, + as an integer type, or as a bitset (lib.template.bitset). + </blockquote> + +<p> +Additionally, change the definition in 22.2.1 to adopt the same +convention as in clause 27 by replacing the existing text with the +following (note, in particluar, the cross-reference to 17.3.2.1.2 in +22.2.1, p1): +</p> + +<blockquote> +<p>22.2.1 The ctype category [lib.category.ctype]</p> +<pre>namespace std { + class ctype_base { + public: + typedef <b><i>T</i></b> mask; + + // numeric values are for exposition only. + static const mask space = 1 << 0; + static const mask print = 1 << 1; + static const mask cntrl = 1 << 2; + static const mask upper = 1 << 3; + static const mask lower = 1 << 4; + static const mask alpha = 1 << 5; + static const mask digit = 1 << 6; + static const mask punct = 1 << 7; + static const mask xdigit = 1 << 8; + static const mask alnum = alpha | digit; + static const mask graph = alnum | punct; + }; +} +</pre> + +<p>The type <tt>mask</tt> is a bitmask type (17.3.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-intro.html#lib.bitmask.types"> [lib.bitmask.types]</a>).</p> +</blockquote> + +<p><i>[Curaçao: The LWG notes that T above should be bold-italics to be +consistent with the rest of the standard.]</i></p> + +<hr> +<a name="340"><h3>340. interpretation of <tt>has_facet<Facet>(loc)</tt> +</h3></a><p> +<b>Section:</b> 22.1.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.category"> [lib.locale.category]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 18 Sep 2001</p> +<p> +It's unclear whether 22.1.1.1.1, p3 says that +<tt>has_facet<Facet>(loc)</tt> returns true for any <tt>Facet</tt> +from Table 51 or whether it includes Table 52 as well: +</p> + +<blockquote> +For any locale <tt>loc</tt> either constructed, or returned by +locale::classic(), and any facet <tt>Facet</tt> that is a member of a +standard category, <tt>has_facet<Facet>(loc)</tt> is true. Each +locale member function which takes a <tt>locale::category</tt> +argument operates on the corresponding set of facets. +</blockquote> + +<p> +It seems that it comes down to which facets are considered to be members of a +standard category. Intuitively, I would classify all the facets in Table 52 as +members of their respective standard categories, but there are an unbounded set +of them... +</p> + +<p> +The paragraph implies that, for instance, <tt>has_facet<num_put<C, +OutputIterator> >(loc)</tt> must always return true. I don't think that's +possible. If it were, then <tt>use_facet<num_put<C, OutputIterator> +>(loc)</tt> would have to return a reference to a distinct object for each +valid specialization of <tt>num_put<C, OutputIteratory></tt>, which is +clearly impossible. +</p> + +<p> +On the other hand, if none of the facets in Table 52 is a member of a standard +category then none of the locale member functions that operate on entire +categories of facets will work properly. +</p> + +<p> +It seems that what p3 should mention that it's required (permitted?) +to hold only for specializations of <tt>Facet</tt> from Table 52 on +<tt>C</tt> from the set { <tt>char</tt>, <tt>wchar_t</tt> }, and +<tt>InputIterator</tt> and <tt>OutputIterator</tt> from the set of +{ +{i,o}<tt>streambuf_iterator</tt><{<tt>char</tt>,<tt>wchar_t</tt>}<tt>></tt> +}. +</p> +<p><b>Proposed resolution:</b></p> +<p>In 22.1.1.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.category"> [lib.locale.category]</a>, paragraph 3, change +"that is a member of a standard category" to "shown in Table 51".</p> +<p><b>Rationale:</b></p> +<p>The facets in Table 52 are an unbounded set. Locales should not be +required to contain an infinite number of facets.</p> + +<p>It's not necessary to talk about which values of InputIterator and +OutputIterator must be supported. Table 51 already contains a +complete list of the ones we need.</p> +<hr> +<a name="341"><h3>341. Vector reallocation and swap</h3></a><p> +<b>Section:</b> 23.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Anthony Williams <b>Date:</b> 27 Sep 2001</p> +<p>It is a common idiom to reduce the capacity of a vector by swapping it with +an empty one:</p> +<pre> std::vector<SomeType> vec; + // fill vec with data + std::vector<SomeType>().swap(vec); + // vec is now empty, with minimal capacity +</pre> + +<p>However, the wording of 23.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a>paragraph 5 prevents +the capacity of a vector being reduced, following a call to +reserve(). This invalidates the idiom, as swap() is thus prevented +from reducing the capacity. The proposed wording for issue <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-defects.html#329">329</a> does not affect this. Consequently, the example above +requires the temporary to be expanded to cater for the contents of +vec, and the contents be copied across. This is a linear-time +operation.</p> + +<p>However, the container requirements state that swap must have constant +complexity (23.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.container.requirements"> [lib.container.requirements]</a> note to table 65).</p> + +<p>This is an important issue, as reallocation affects the validity of +references and iterators.</p> + +<p>If the wording of 23.2.4.2p5 is taken to be the desired intent, then +references and iterators remain valid after a call to swap, if they refer to +an element before the new end() of the vector into which they originally +pointed, in which case they refer to the element at the same index position. +Iterators and references that referred to an element whose index position +was beyond the new end of the vector are invalidated.</p> + +<p>If the note to table 65 is taken as the desired intent, then there are two +possibilities with regard to iterators and references:</p> + +<ol> +<li>All Iterators and references into both vectors are invalidated.</li> +<li>Iterators and references into either vector remain valid, and remain +pointing to the same element. Consequently iterators and references that +referred to one vector now refer to the other, and vice-versa.</li> +</ol> +<p><b>Proposed resolution:</b></p> +<p>Add a new paragraph after 23.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.vector.capacity"> [lib.vector.capacity]</a> paragraph 5:</p> +<blockquote> +<pre> void swap(vector<T,Allocator>& x); +</pre> +<p> +<b>Effects:</b> Exchanges the contents and capacity() of <tt>*this</tt> +with that of <tt>x</tt>.</p> +<p> +<b>Complexity:</b> Constant time.</p> +</blockquote> + +<p><i>[This solves the problem reported for this issue. We may also +have a problem with a circular definition of swap() for other +containers.]</i></p> + +<p><b>Rationale:</b></p> +<p> +swap should be constant time. The clear intent is that it should just +do pointer twiddling, and that it should exchange all properties of +the two vectors, including their reallocation guarantees. +</p> +<hr> <a name="345"><h3>345. type tm in <cwchar></h3></a><p> -<b>Section:</b> 21.4 <a href="lib-strings.html#lib.c.strings"> [lib.c.strings]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Clark Nelson <b>Date:</b> 19 Oct 2001</p> +<b>Section:</b> 21.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.c.strings"> [lib.c.strings]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Clark Nelson <b>Date:</b> 19 Oct 2001</p> <p> C99, and presumably amendment 1 to C90, specify that <wchar.h> -declares struct tm as an incomplete type. However, table 48 in 21.4 <a href="lib-strings.html#lib.c.strings"> [lib.c.strings]</a> does not mention the type tm as being declared in +declares struct tm as an incomplete type. However, table 48 in 21.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.c.strings"> [lib.c.strings]</a> does not mention the type tm as being declared in <cwchar>. Is this omission intentional or accidental? </p> <p><b>Proposed resolution:</b></p> -<p>In section 21.4 <a href="lib-strings.html#lib.c.strings"> [lib.c.strings]</a>, add "tm" to table 48.</p> +<p>In section 21.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-strings.html#lib.c.strings"> [lib.c.strings]</a>, add "tm" to table 48.</p> <hr> <a name="346"><h3>346. Some iterator member functions should be const</h3></a><p> -<b>Section:</b> 24.1 <a href="lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> <b>Status:</b> <a href="lwg-active.html#DR">DR</a> <b>Submitter:</b> Jeremy Siek <b>Date:</b> 20 Oct 2001</p> +<b>Section:</b> 24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Jeremy Siek <b>Date:</b> 20 Oct 2001</p> <p>Iterator member functions and operators that do not change the state of the iterator should be defined as const member functions or as functions that take iterators either by const reference or by @@ -8006,37 +9816,437 @@ are suggested to make this explicit.</p> for non-const and a,b for const iterators. The following changes make this more explicit and also fix a couple problems.</p> <p><b>Proposed resolution:</b></p> -<p>In 24.1 <a href="lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> Change the first section of p9 from -"In the following sections, a and b denote values of X..." to -"In the following sections, a and b denote values of type const X...".</p> +<p>In 24.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.iterator.requirements"> [lib.iterator.requirements]</a> Change the first section of p9 from +"In the following sections, a and b denote values of X..." to +"In the following sections, a and b denote values of type const X...".</p> <p>In Table 73, change</p> -<pre> - a->m U& ... +<pre> a->m U& ... </pre> <p>to</p> -<pre> - a->m const U& ... +<pre> a->m const U& ... r->m U& ... </pre> <p>In Table 73 expression column, change</p> -<pre> - *a = t +<pre> *a = t </pre> <p>to</p> -<pre> - *r = t +<pre> *r = t </pre> <p><i>[Redmond: The container requirements should be reviewed to see if the same problem appears there.]</i></p> +<hr> +<a name="349"><h3>349. Minor typographical error in ostream_iterator</h3></a><p> +<b>Section:</b> 24.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.ostream.iterator"> [lib.ostream.iterator]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Andy Sawyer <b>Date:</b> 24 Oct 2001</p> +<p>24.5.2 [lib.ostream.iterator] states:</p> +<pre> [...] + + private: + // basic_ostream<charT,traits>* out_stream; exposition only + // const char* delim; exposition only +</pre> + +<p>Whilst it's clearly marked "exposition only", I suspect 'delim' +should be of type 'const charT*'.</p> +<p><b>Proposed resolution:</b></p> +<p> +In 24.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.ostream.iterator"> [lib.ostream.iterator]</a>, replace <tt>const char* delim</tt> with +<tt>const charT* delim</tt>. +</p> +<hr> +<a name="354"><h3>354. Associative container lower/upper bound requirements</h3></a><p> +<b>Section:</b> 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Hans Aberg <b>Date:</b> 17 Dec 2001</p> +<p> +Discussions in the thread "Associative container lower/upper bound +requirements" on comp.std.c++ suggests that there is a defect in the +C++ standard, Table 69 of section 23.1.2, "Associative containers", +[lib.associative.reqmts]. It currently says:</p> + +<blockquote> +<p> +a.find(k): returns an iterator pointing to an element with the key equivalent to +k, or a.end() if such an element is not found. +</p> + +<p> +a.lower_bound(k): returns an iterator pointing to the first element with +key not less than k. +</p> + +<p> +a.upper_bound(k): returns an iterator pointing to the first element with +key greater than k. +</p> +</blockquote> + +<p> +We have "or a.end() if such an element is not found" for +<tt>find</tt>, but not for <tt>upper_bound</tt> or +<tt>lower_bound</tt>. As the text stands, one would be forced to +insert a new element into the container and return an iterator to that +in case the sought iterator does not exist, which does not seem to be +the intention (and not possible with the "const" versions). +</p> +<p><b>Proposed resolution:</b></p> + +<p>Change Table 69 of section 23.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-containers.html#lib.associative.reqmts"> [lib.associative.reqmts]</a> indicated entries +to:</p> + +<blockquote> +<p> +a.lower_bound(k): returns an iterator pointing to the first element with +key not less than k, or a.end() if such an element is not found. +</p> + +<p> +a.upper_bound(k): returns an iterator pointing to the first element with +key greater than k, or a.end() if such an element is not found. +</p> +</blockquote> + +<p><i>[Curaçao: LWG reviewed PR.]</i></p> + +<hr> +<a name="358"><h3>358. interpreting <tt>thousands_sep</tt> after a <tt>decimal_point</tt> +</h3></a><p> +<b>Section:</b> 22.2.2.1.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.facet.num.get.virtuals"> [lib.facet.num.get.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 12 Mar 2002</p> +<p> +I don't think <tt>thousands_sep</tt> is being treated correctly after +decimal_point has been seen. Since grouping applies only to the +integral part of the number, the first such occurrence should, IMO, +terminate Stage 2. (If it does not terminate it, then 22.2.2.1.2, p12 +and 22.2.3.1.2, p3 need to explain how <tt>thousands_sep</tt> is to be +interpreted in the fractional part of a number.) +</p> + +<p> +The easiest change I can think of that resolves this issue would be +something like below. +</p> +<p><b>Proposed resolution:</b></p> +<p> +Change the first sentence of 22.2.2.1.2, p9 from +</p> + +<blockquote> + If discard is true then the position of the character is + remembered, but the character is otherwise ignored. If it is not + discarded, then a check is made to determine if c is allowed as + the next character of an input field of the conversion specifier + returned by stage 1. If so it is accumulated. +</blockquote> + +<p>to</p> + +<blockquote> + If <tt>discard</tt> is true, then if <tt>'.'</tt> has not yet been + accumulated, then the position of the character is remembered, but + the character is otherwise ignored. Otherwise, if <tt>'.'</tt> has + already been accumulated, the character is discarded and Stage 2 + terminates. ... +</blockquote> + +<p><b>Rationale:</b></p> +<p>We believe this reflects the intent of the Standard. Thousands sep + characters after the decimal point are not useful in any locale. + Some formatting conventions do group digits that follow the decimal + point, but they usually introduce a different grouping character + instead of reusing the thousand sep character. If we want to add + support for such conventions, we need to do so explicitly.</p> + +<hr> +<a name="360"><h3>360. locale mandates inefficient implementation</h3></a><p> +<b>Section:</b> 22.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale"> [lib.locale]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 12 Mar 2002</p> +<p> +22.1.1, p7 (copied below) allows iostream formatters and extractors +to make assumptions about the values returned from facet members. +However, such assumptions are apparently not guaranteed to hold +in other cases (e.g., when the facet members are being called directly +rather than as a result of iostream calls, or between successive +calls to the same iostream functions with no interevening calls to +<tt>imbue()</tt>, or even when the facet member functions are called +from other member functions of other facets). This restriction +prevents locale from being implemented efficiently. +</p> +<p><b>Proposed resolution:</b></p> +<p>Change the first sentence in 22.1.1, p7 from</p> +<blockquote> + In successive calls to a locale facet member function during + a call to an iostream inserter or extractor or a streambuf member + function, the returned result shall be identical. [Note: This + implies that such results may safely be reused without calling + the locale facet member function again, and that member functions + of iostream classes cannot safely call <tt>imbue()</tt> + themselves, except as specified elsewhere. --end note] +</blockquote> + +<p>to</p> + +<blockquote> + In successive calls to a locale facet member function on a facet + object installed in the same locale, the returned result shall be + identical. ... +</blockquote> + +<p><b>Rationale:</b></p> +<p>This change is reasonable becuase it clarifies the intent of this + part of the standard.</p> +<hr> +<a name="363"><h3>363. Missing exception specification in 27.4.2.1.1</h3></a><p> +<b>Section:</b> 27.4.2.1.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios::failure"> [lib.ios::failure]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Walter Brown and Marc Paterno <b>Date:</b> 20 May 2002</p> +<p> +The destructor of ios_base::failure should have an empty throw +specification, because the destructor of its base class, exception, is +declared in this way. +</p> +<p><b>Proposed resolution:</b></p> +<p>Change the destructor to</p> +<pre> virtual ~failure() throw(); +</pre> +<p><b>Rationale:</b></p> +<p>Fixes an obvious glitch. This is almost editorial.</p> +<hr> +<a name="364"><h3>364. Inconsistent wording in 27.5.2.4.2</h3></a><p> +<b>Section:</b> 27.5.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Walter Brown, Marc Paterno <b>Date:</b> 10 May 2002</p> +<p> +27.5.2.4.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.streambuf.virt.buffer"> [lib.streambuf.virt.buffer]</a> paragraph 1 is inconsistent with the Effects +clause for seekoff. +</p> +<p><b>Proposed resolution:</b></p> +<p> +Make this paragraph, the Effects clause for setbuf, consistent in wording +with the Effects clause for seekoff in paragraph 3 by amending paragraph 1 +to indicate the purpose of setbuf: +</p> + +<p>Original text:</p> + +<blockquote> +1 Effects: Performs an operation that is defined separately for each +class derived from basic_streambuf in this clause (27.7.1.3, 27.8.1.4). +</blockquote> + +<p>Proposed text:</p> + +<blockquote> +1 Effects: Influences stream buffering in a way that is defined separately +for each class derived from basic_streambuf in this clause +(27.7.1.3, 27.8.1.4). +</blockquote> + +<p><b>Rationale:</b></p> +<p>The LWG doesn't believe there is any normative difference between + the existing wording and what's in the proposed resolution, but the + change may make the intent clearer.</p> +<hr> +<a name="370"><h3>370. Minor error in basic_istream::get</h3></a><p> +<b>Section:</b> 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Ray Lischner <b>Date:</b> 15 Jul 2002</p> +<p>Defect report for description of basic_istream::get (section 27.6.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.unformatted"> [lib.istream.unformatted]</a>), paragraph 15. The description for the get function +with the following signature:</p> + +<pre> basic_istream<charT,traits>& get(basic_streambuf<char_type,traits>& + sb); +</pre> + +<p>is incorrect. It reads</p> + +<blockquote> + Effects: Calls get(s,n,widen('\n')) +</blockquote> + +<p>which I believe should be:</p> + +<blockquote> + Effects: Calls get(sb,widen('\n')) +</blockquote> +<p><b>Proposed resolution:</b></p> +<p>Change the <b>Effects</b> paragraph to:</p> +<blockquote> + Effects: Calls get(sb,this->widen('\n')) +</blockquote> + +<p><i>[Pre-Oxford: Minor correction from Howard: replaced 'widen' + with 'this->widen'.]</i></p> + +<p><b>Rationale:</b></p> +<p>Fixes an obvious typo.</p> +<hr> +<a name="373"><h3>373. Are basic_istream and basic_ostream to use (exceptions()&badbit) != 0 ?</h3></a><p> +<b>Section:</b> 27.6.1.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted.reqmts"> [lib.istream.formatted.reqmts]</a>, 27.6.2.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.formatted.reqmts"> [lib.ostream.formatted.reqmts]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Keith Baker <b>Date:</b> 23 Jul 2002</p> + +<p> +In 27.6.1.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted.reqmts"> [lib.istream.formatted.reqmts]</a> and 27.6.2.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.formatted.reqmts"> [lib.ostream.formatted.reqmts]</a> +(exception()&badbit) != 0 is used in testing for rethrow, yet +exception() is the constructor to class std::exception in 18.6.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-support.html#lib.exception"> [lib.exception]</a> that has no return type. Should member function +exceptions() found in 27.4.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ios"> [lib.ios]</a> be used instead? +</p> + +<p><b>Proposed resolution:</b></p> +<p> +In 27.6.1.2.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.istream.formatted.reqmts"> [lib.istream.formatted.reqmts]</a> and 27.6.2.5.1 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.ostream.formatted.reqmts"> [lib.ostream.formatted.reqmts]</a>, change +"(exception()&badbit) != 0" to "(exceptions()&badbit) != 0". +</p> +<p><b>Rationale:</b></p> +<p>Fixes an obvious typo.</p> +<hr> +<a name="375"><h3>375. basic_ios should be ios_base in 27.7.1.3</h3></a><p> +<b>Section:</b> 27.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Ray Lischner <b>Date:</b> 14 Aug 2002</p> +<p> +In Section 27.7.1.3 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iostreams.html#lib.stringbuf.virtuals"> [lib.stringbuf.virtuals]</a>: Table 90, Table 91, and paragraph +14 all contain references to "basic_ios::" which should be +"ios_base::". +</p> +<p><b>Proposed resolution:</b></p> +<p> +Change all references to "basic_ios" in Table 90, Table 91, and +paragraph 14 to "ios_base". +</p> +<p><b>Rationale:</b></p> +<p>Fixes an obvious typo.</p> +<hr> +<a name="380"><h3>380. typos in codecvt tables 53 and 54</h3></a><p> +<b>Section:</b> 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 6 Sep 2002</p> +<p> +Tables 53 and 54 in 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> are both titled "convert +result values," when surely "do_in/do_out result values" must have +been intended for Table 53 and "do_unshift result values" for Table +54. +</p> +<p> +Table 54, row 3 says that the meaning of partial is "more characters +needed to be supplied to complete termination." The function is not +supplied any characters, it is given a buffer which it fills with +characters or, more precisely, destination elements (i.e., an escape +sequence). So partial means that space for more than (to_limit - to) +destination elements was needed to terminate a sequence given the +value of state. +</p> +<p><b>Proposed resolution:</b></p> +<p> +Change the title of Table 53 to "do_in/do_out result values" and +the title of Table 54 to "do_unshift result values." +</p> +<p> +Change the text in Table 54, row 3 (the <b>partial</b> row), under the +heading Meaning, to "space for more than (to_limit - to) destination +elements was needed to terminate a sequence given the value of state." +</p> +<hr> +<a name="381"><h3>381. detection of invalid mbstate_t in codecvt</h3></a><p> +<b>Section:</b> 22.2.1.5.2 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-locales.html#lib.locale.codecvt.virtuals"> [lib.locale.codecvt.virtuals]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> Martin Sebor <b>Date:</b> 6 Sep 2002</p> +<p> +All but one codecvt member functions that take a state_type argument +list as one of their preconditions that the state_type argument have +a valid value. However, according to 22.2.1.5.2, p6, +codecvt::do_unshift() is the only codecvt member that is supposed to +return error if the state_type object is invalid. +</p> + +<p> +It seems to me that the treatment of state_type by all codecvt member +functions should be the same and the current requirements should be +changed. Since the detection of invalid state_type values may be +difficult in general or computationally expensive in some specific +cases, I propose the following: +</p> +<p><b>Proposed resolution:</b></p> +<p> +Add a new paragraph before 22.2.1.5.2, p5, and after the function +declaration below +</p> +<pre> result do_unshift(stateT& state, + externT* to, externT* to_limit, externT*& to_next) const; +</pre> +<p> +as follows: +</p> +<pre> Requires: (to <= to_end) well defined and true; state initialized, + if at the beginning of a sequence, or else equal to the result of + converting the preceding characters in the sequence. +</pre> +<p> +and change the text in Table 54, row 4, the <b>error</b> row, under +the heading Meaning, from +</p> +<pre> state has invalid value +</pre> +<p> +to +</p> +<pre> an unspecified error has occurred +</pre> +<p><b>Rationale:</b></p> +<p>The intent is that implementations should not be required to detect +invalid state values; such a requirement appears nowhere else. An +invalid state value is a precondition violation, <i>i.e.</i> undefined +behavior. Implementations that do choose to detect invalid state +values, or that choose to detect any other kind of error, may return +<b>error</b> as an indication.</p> +<hr> +<a name="383"><h3>383. Bidirectional iterator assertion typo</h3></a><p> +<b>Section:</b> 24.1.4 <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lib-iterators.html#lib.bidirectional.iterators"> [lib.bidirectional.iterators]</a> <b>Status:</b> <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#WP">WP</a> <b>Submitter:</b> ysapir (submitted via comp.std.c++) <b>Date:</b> 17 Oct 2002</p> +<p> +Following a discussion on the boost list regarding end iterators and +the possibility of performing operator--() on them, it seems to me +that there is a typo in the standard. This typo has nothing to do +with that discussion. +</p> + +<p> +I have checked this newsgroup, as well as attempted a search of the +Active/Defect/Closed Issues List on the site for the words "s is +derefer" so I believe this has not been proposed before. Furthermore, +the "Lists by Index" mentions only DR <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#299">299</a> on section +24.1.4, and DR <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#299">299</a> is not related to this issue. +</p> + +<p> +The standard makes the following assertion on bidirectional iterators, +in section 24.1.4 [lib.bidirectional.iterators], Table 75: +</p> + +<pre> operational assertion/note +expression return type semantics pre/post-condition + +--r X& pre: there exists s such + that r == ++s. + post: s is dereferenceable. + --(++r) == r. + --r == --s implies r == s. + &r == &--r. +</pre> + +<p> +(See <a href="http://aspn.activestate.com/ASPN/Mail/Message/boost/1395763">http://aspn.activestate.com/ASPN/Mail/Message/boost/1395763</a>.) +</p> + +<p> +In particular, "s is dereferenceable" seems to be in error. It seems +that the intention was to say "r is dereferenceable". +</p> + +<p> +If it were to say "r is dereferenceable" it would +make perfect sense. Since s must be dereferenceable prior to +operator++, then the natural result of operator-- (to undo operator++) +would be to make r dereferenceable. Furthermore, without other +assertions, and basing only on precondition and postconditions, we +could not otherwise know this. So it is also interesting information. +</p> + +<p><b>Proposed resolution:</b></p> +<p> +Change the guarantee to "postcondition: r is dereferenceable." +</p> +<p><b>Rationale:</b></p> +<p>Fixes an obvious typo</p> <p>----- End of document -----</p> -</body> -</html> +</body></html>
\ No newline at end of file diff --git a/libstdc++-v3/include/bits/list.tcc b/libstdc++-v3/include/bits/list.tcc index 2afde96995a..9c5a0cde607 100644 --- a/libstdc++-v3/include/bits/list.tcc +++ b/libstdc++-v3/include/bits/list.tcc @@ -249,21 +249,26 @@ namespace std list<_Tp,_Alloc>:: merge(list& __x) { - iterator __first1 = begin(); - iterator __last1 = end(); - iterator __first2 = __x.begin(); - iterator __last2 = __x.end(); - while (__first1 != __last1 && __first2 != __last2) - if (*__first2 < *__first1) - { - iterator __next = __first2; - _M_transfer(__first1, __first2, ++__next); - __first2 = __next; - } - else - ++__first1; - if (__first2 != __last2) - _M_transfer(__last1, __first2, __last2); + // _GLIBCXX_RESOLVE_LIB_DEFECTS + // 300. list::merge() specification incomplete + if (this != &__x) + { + iterator __first1 = begin(); + iterator __last1 = end(); + iterator __first2 = __x.begin(); + iterator __last2 = __x.end(); + while (__first1 != __last1 && __first2 != __last2) + if (*__first2 < *__first1) + { + iterator __next = __first2; + _M_transfer(__first1, __first2, ++__next); + __first2 = __next; + } + else + ++__first1; + if (__first2 != __last2) + _M_transfer(__last1, __first2, __last2); + } } // FIXME put this somewhere else @@ -351,20 +356,26 @@ namespace std list<_Tp,_Alloc>:: merge(list& __x, _StrictWeakOrdering __comp) { - iterator __first1 = begin(); - iterator __last1 = end(); - iterator __first2 = __x.begin(); - iterator __last2 = __x.end(); - while (__first1 != __last1 && __first2 != __last2) - if (__comp(*__first2, *__first1)) - { - iterator __next = __first2; - _M_transfer(__first1, __first2, ++__next); - __first2 = __next; - } - else - ++__first1; - if (__first2 != __last2) _M_transfer(__last1, __first2, __last2); + // _GLIBCXX_RESOLVE_LIB_DEFECTS + // 300. list::merge() specification incomplete + if (this != &__x) + { + iterator __first1 = begin(); + iterator __last1 = end(); + iterator __first2 = __x.begin(); + iterator __last2 = __x.end(); + while (__first1 != __last1 && __first2 != __last2) + if (__comp(*__first2, *__first1)) + { + iterator __next = __first2; + _M_transfer(__first1, __first2, ++__next); + __first2 = __next; + } + else + ++__first1; + if (__first2 != __last2) + _M_transfer(__last1, __first2, __last2); + } } template<typename _Tp, typename _Alloc> |
