<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3c.org/TR/1999/REC-html401-19991224/loose.dtd">
<HTML><HEAD><TITLE>C++ Standard Library Closed Issues List</TITLE>
<META http-equiv=Content-Type content="text/html; charset=windows-1252">
<META content="MSHTML 6.00.2800.1400" name=GENERATOR></HEAD>
<BODY text=#000000 bgColor=#ffffff>
<TABLE>
  <TBODY>
  <TR>
    <TD align=left>Doc. no.</TD>
    <TD align=left>N1686=04-0126</TD></TR>
  <TR>
    <TD align=left>Date:</TD>
    <TD align=left>10 Sep 2004</TD></TR>
  <TR>
    <TD align=left>Project:</TD>
    <TD align=left>Programming Language C++</TD></TR>
  <TR>
    <TD align=left>Reply to:</TD>
    <TD align=left>Matt Austern &lt;austern@apple.com&gt;</TD></TR></TBODY></TABLE>
<H1>C++ Standard Library Closed Issues List (Revision 32)</H1>
<P>Reference ISO/IEC IS 14882:1998(E)</P>
<P>Also see:</P>
<UL>
  <LI><A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-toc.html">Table 
  of Contents</A> for all library issues. 
  <LI><A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-index.html">Index 
  by Section</A> for all library issues. 
  <LI><A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-status.html">Index 
  by Status</A> for all library issues. 
  <LI><A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html">Library 
  Active Issues List</A> 
  <LI><A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html">Library 
  Defect Reports List</A> </LI></UL>
<P>This document contains only library issues which have been closed by the 
Library Working Group as duplicates or not defects. That is, issues which have a 
status of <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A> 
or <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>. 
See the <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html">Library 
Active Issues List</A> active issues and more information. See the <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html">Library 
Defect Reports List</A> for issues considered defects. The introductory material 
in that document also applies to this document.</P>
<H2>Revision History</H2>
<UL>
  <LI>R32: 2004-09 pre-Redmond mailing: reflects new proposed resolutions and 
  new issues received after the 2004-07 mailing. Added new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#479">479</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#481">481</A>. 

  <LI>R31: 2004-07 mid-term mailing: reflects new proposed resolutions and new 
  issues received after the post-Sydney mailing. Added new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#463">463</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#478">478</A>. 

  <LI>R30: Post-Sydney mailing: reflects decisions made at the Sydney meeting. 
  Voted all "Ready" issues from R29 into the working paper. Added new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#460">460</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#462">462</A>. 

  <LI>R29: Pre-Sydney mailing. Added new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#441">441</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#457">457</A>. 

  <LI>R28: Post-Kona mailing: reflects decisions made at the Kona meeting. Added 
  new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#432">432</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#440">440</A>. 

  <LI>R27: Pre-Kona mailing. Added new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#404">404</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#431">431</A>. 

  <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>R25: Pre-Oxford mailing. Added new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#390">390</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#402">402</A>. 

  <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="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#253">253</A>, 
  which has been given a new proposed resolution, were moved to DR status. Added 
  new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#383">383</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#389">389</A>. 
  (Issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#387">387</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#389">389</A> 
  were discussed at the meeting.) Made progress on issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#225">225</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#226">226</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#229">229</A>: 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#225">225</A> 
  and <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#229">229</A> 
  have been moved to Ready status, and the only remaining concerns with <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#226">226</A> 
  involve wording. 
  <LI>R23: Pre-Santa Cruz mailing. Added new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#367">367</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#382">382</A>. 
  Moved issues in the TC to TC status. 
  <LI>R22: Post-Curaao mailing. Added new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#362">362</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#366">366</A>. 

  <LI>R21: Pre-Curaao mailing. Added new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#351">351</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#361">361</A>. 

  <LI>R20: Post-Redmond mailing; reflects actions taken in Redmond. Added new 
  issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#336">336</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#350">350</A>, 
  of which issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#347">347</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/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="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#284">284</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#241">241</A>, 
  and <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#267">267</A>. 
  Noteworthy issues discussed at Redmond include <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#120">120</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#202">202</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#226">226</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#233">233</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#270">270</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#253">253</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#254">254</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#323">323</A>. 

  <LI>R19: Pre-Redmond mailing. Added new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#323">323</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#335">335</A>. 

  <LI>R18: Post-Copenhagen mailing; reflects actions taken in Copenhagen. Added 
  new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#312">312</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#317">317</A>, 
  and discussed new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#271">271</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#314">314</A>. 
  Changed status of issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#103">103</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#118">118</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#136">136</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#153">153</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#165">165</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#171">171</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#183">183</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#184">184</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#185">185</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#186">186</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#214">214</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#221">221</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#234">234</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#237">237</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#243">243</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#248">248</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#251">251</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#252">252</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#256">256</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#260">260</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#261">261</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#262">262</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#263">263</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#265">265</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#268">268</A> 
  to DR. Changed status of issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#49">49</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#109">109</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#117">117</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#182">182</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#228">228</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#230">230</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#232">232</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#235">235</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#238">238</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#241">241</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#242">242</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#250">250</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#259">259</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#264">264</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#266">266</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#267">267</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#271">271</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#272">272</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#273">273</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#275">275</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#281">281</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#284">284</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#285">285</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#286">286</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#288">288</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#292">292</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#295">295</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#297">297</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#298">298</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#301">301</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#303">303</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#306">306</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#307">307</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#308">308</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#312">312</A> 
  to Ready. Closed issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#111">111</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#277">277</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#279">279</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#287">287</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#289">289</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#293">293</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#302">302</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#313">313</A> 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#314">314</A> 
  as NAD. 
  <LI>R17: Pre-Copenhagen mailing. Converted issues list to XML. Added proposed 
  resolutions for issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#49">49</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#76">76</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#91">91</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#235">235</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#250">250</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#267">267</A>. 
  Added new issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#278">278</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#311">311</A>. 

  <LI>R16: post-Toronto mailing; reflects actions taken in Toronto. Added new 
  issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#265">265</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#277">277</A>. 
  Changed status of issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#3">3</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#8">8</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#9">9</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#19">19</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#26">26</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#31">31</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#61">61</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#63">63</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#86">86</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#108">108</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#112">112</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#114">114</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#115">115</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#122">122</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#127">127</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#129">129</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#134">134</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#137">137</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#142">142</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#144">144</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#146">146</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#147">147</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#159">159</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#164">164</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#170">170</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#181">181</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#199">199</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#208">208</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#209">209</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#210">210</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#211">211</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#212">212</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#217">217</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#220">220</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#222">222</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#223">223</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#224">224</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#227">227</A> 
  to "DR". Reopened issue <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#23">23</A>. 
  Reopened issue <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#187">187</A>. 
  Changed issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#2">2</A> 
  and <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#4">4</A> 
  to NAD. Fixed a typo in issue <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#17">17</A>. 
  Fixed issue <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#70">70</A>: 
  signature should be changed both places it appears. Fixed issue <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#160">160</A>: 
  previous version didn't fix the bug in enough places. 
  <LI>R15: pre-Toronto mailing. Added issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#233">233</A>-<A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#264">264</A>. 
  Some small HTML formatting changes so that we pass Weblint tests. 
  <LI>R14: post-Tokyo II mailing; reflects committee actions taken in Tokyo. 
  Added issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#228">228</A> 
  to <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#232">232</A>. 
  (00-0019R1/N1242) 
  <LI>R13: pre-Tokyo II updated: Added issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#212">212</A> 
  to <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#227">227</A>. 

  <LI>R12: pre-Tokyo II mailing: Added issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#199">199</A> 
  to <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#211">211</A>. 
  Added "and paragraph 5" to the proposed resolution of issue <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#29">29</A>. 
  Add further rationale to issue <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#178">178</A>. 

  <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="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#4">4</A> 
  and <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#38">38</A>. 
  Added issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#196">196</A> 
  to <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#198">198</A>. 
  Closed issues list split into "defects" and "closed" documents. Changed the 
  proposed resolution of issue <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#4">4</A> 
  to NAD, and changed the wording of proposed resolution of issue <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#38">38</A>. 

  <LI>R10: pre-Kona updated. Added proposed resolutions <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#83">83</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#86">86</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#91">91</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#92">92</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#109">109</A>. 
  Added issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#190">190</A> 
  to <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#195">195</A>. 
  (99-0033/D1209, 14 Oct 99) 
  <LI>R9: pre-Kona mailing. Added issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#140">140</A> 
  to <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#189">189</A>. 
  Issues list split into separate "active" and "closed" documents. 
  (99-0030/N1206, 25 Aug 99) 
  <LI>R8: post-Dublin mailing. Updated to reflect LWG and full committee actions 
  in Dublin. (99-0016/N1193, 21 Apr 99) 
  <LI>R7: pre-Dublin updated: Added issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#130">130</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#131">131</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#132">132</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#133">133</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#134">134</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#135">135</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#136">136</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#137">137</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#138">138</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#139">139</A> 
  (31 Mar 99) 
  <LI>R6: pre-Dublin mailing. Added issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#127">127</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#128">128</A>, 
  and <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#129">129</A>. 
  (99-0007/N1194, 22 Feb 99) 
  <LI>R5: update issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#103">103</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#112">112</A>; 
  added issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#114">114</A> 
  to <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#126">126</A>. 
  Format revisions to prepare for making list public. (30 Dec 98) 
  <LI>R4: post-Santa Cruz II updated: Issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#110">110</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#111">111</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#112">112</A>, 
  <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#113">113</A> 
  added, several issues corrected. (22 Oct 98) 
  <LI>R3: post-Santa Cruz II: Issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#94">94</A> 
  to <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#109">109</A> 
  added, many issues updated to reflect LWG consensus (12 Oct 98) 
  <LI>R2: pre-Santa Cruz II: Issues <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#73">73</A> 
  to <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#93">93</A> 
  added, issue <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#17">17</A> 
  updated. (29 Sep 98) 
  <LI>R1: Correction to issue <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#55">55</A> 
  resolution, <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#60">60</A> 
  code format, <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#64">64</A> 
  title. (17 Sep 98) </LI></UL>
<H2>Closed Issues</H2>
<HR>
<A name=2>
<H3>2.&nbsp;Auto_ptr conversions effects incorrect</H3></A>
<P><B>Section:</B>&nbsp;20.4.5.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.auto.ptr.conv">[lib.auto.ptr.conv]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nathan Myers&nbsp; <B>Date:</B>&nbsp;4 Dec 1997</P>
<P>Paragraph 1 in "Effects", says "Calls p-&gt;release()" where it clearly must 
be "Calls p.release()". (As it is, it seems to require using 
auto_ptr&lt;&gt;::operator-&gt; to refer to X::release, assuming that 
exists.)</P>
<P><B>Proposed resolution:</B></P>
<P>Change 20.4.5.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.auto.ptr.conv">[lib.auto.ptr.conv]</A> 
paragraph 1 Effects from "Calls p-&gt;release()" to "Calls p.release()".</P>
<P><B>Rationale:</B></P>
<P>Not a defect: the proposed change is already found in the standard. 
[Originally classified as a defect, later reclassified.]</P>
<HR>
<A name=4>
<H3>4.&nbsp;Basic_string size_type and difference_type should be implementation 
defined</H3></A>
<P><B>Section:</B>&nbsp;21.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.basic.string">[lib.basic.string]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Beman Dawes&nbsp; <B>Date:</B>&nbsp;16 Nov 1997</P>
<P>In Morristown we changed the size_type and difference_type typedefs for all 
the other containers to implementation defined with a reference to 23.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.container.requirements">[lib.container.requirements]</A>. 
This should probably also have been done for strings. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Not a defect. [Originally classified as a defect, later reclassified.] 
basic_string, unlike the other standard library template containers, is severely 
constrained by its use of char_traits. Those types are dictated by the traits 
class, and are far from implementation defined.</P>
<HR>
<A name=6>
<H3>6.&nbsp;File position not an offset unimplementable</H3></A>
<P><B>Section:</B>&nbsp;27.4.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.fpos">[lib.fpos]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Matt Austern&nbsp; <B>Date:</B>&nbsp;15 Dec 1997</P>
<P>Table 88, in I/O, is too strict; it's unimplementable on systems where a file 
position isn't just an offset. It also never says just what fpos&lt;&gt; is 
really supposed to be. [Here's my summary, which Jerry agrees is more or less 
accurate. "I think I now know what the class really is, at this point: it's a 
magic cookie that encapsulates an mbstate_t and a file position (possibly 
represented as an fpos_t), it has syntactic support for pointer-like arithmetic, 
and implementors are required to have real, not just syntactic, support for 
arithmetic." This isn't standardese, of course.] </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Not a defect. The LWG believes that the Standard is already clear, and that 
the above summary is what the Standard in effect says.</P>
<HR>
<A name=10>
<H3>10.&nbsp;Codecvt&lt;&gt;::do unclear</H3></A>
<P><B>Section:</B>&nbsp;22.2.1.5.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.codecvt.virtuals">[lib.locale.codecvt.virtuals]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Matt Austern&nbsp; <B>Date:</B>&nbsp;14 Jan 1998</P>
<P>Section 22.2.1.5.2 says that codecvt&lt;&gt;::do_in and do_out should return 
the value noconv if "no conversion was needed". However, I don't see anything 
anywhere that defines what it means for a conversion to be needed or not needed. 
I can think of several circumstances where one might plausibly think that a 
conversion is not "needed", but I don't know which one is intended here. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Duplicate. See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#19">19</A>.</P>
<HR>
<A name=12>
<H3>12.&nbsp;Way objects hold allocators unclear</H3></A>
<P><B>Section:</B>&nbsp;20.1.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.allocator.requirements">[lib.allocator.requirements]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Angelika Langer&nbsp; <B>Date:</B>&nbsp;23 Feb 1998</P>
<P>I couldn't find a statement in the standard saying whether the allocator 
object held by a container is held as a copy of the constructor argument or 
whether a pointer of reference is maintained internal. There is an according 
statement for compare objects and how they are maintained by the associative 
containers, but I couldn't find anything regarding allocators. </P>
<P>Did I overlook it? Is it an open issue or known defect? Or is it deliberately 
left unspecified? </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Not a defect. The LWG believes that the Standard is already clear.&nbsp; See 
23.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.container.requirements">[lib.container.requirements]</A>, 
paragraph 8.</P>
<HR>
<A name=43>
<H3>43.&nbsp;Locale table correction</H3></A>
<P><B>Section:</B>&nbsp;22.2.1.5.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.codecvt.virtuals">[lib.locale.codecvt.virtuals]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Brendan Kehoe&nbsp; <B>Date:</B>&nbsp;1 Jun 1998</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Duplicate. See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#33">33</A>.</P>
<HR>
<A name=45>
<H3>45.&nbsp;Stringstreams read/write pointers initial position unclear</H3></A>
<P><B>Section:</B>&nbsp;27.7.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.ostringstream">[lib.ostringstream]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Matthias Mueller&nbsp; <B>Date:</B>&nbsp;27 May 1998</P>
<P>In a comp.lang.c++.moderated Matthias Mueller wrote:</P>
<P>"We are not sure how to interpret the CD2 (see 27.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.iostream.forward">[lib.iostream.forward]</A>, 
27.7.3.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.ostringstream.cons">[lib.ostringstream.cons]</A>, 
27.7.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.stringbuf.cons">[lib.stringbuf.cons]</A>) 
with respect to the question as to what the correct initial positions of the 
write and&nbsp; read pointers of a stringstream should be."</P>
<P>"Is it the same to output two strings or to initialize the stringstream with 
the first and to output the second?"</P>
<P><I>[PJ Plauger, Bjarne Stroustrup, Randy Smithey, Sean Corfield, and Jerry 
Schwarz have all offered opinions; see reflector messages lib-6518, 6519, 6520, 
6521, 6523, 6524.]</I></P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The LWG believes the Standard is correct as written. The behavior of 
stringstreams is consistent with fstreams, and there is a constructor which can 
be used to obtain the desired effect. This behavior is known to be different 
from strstreams.</P>
<HR>
<A name=58>
<H3>58.&nbsp;Extracting a char from a wide-oriented stream</H3></A>
<P><B>Section:</B>&nbsp;27.6.1.2.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.istream::extractors">[lib.istream::extractors]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Matt Austern&nbsp; <B>Date:</B>&nbsp;1 Jul 1998</P>
<P>27.6.1.2.3 has member functions for extraction of signed char and unsigned 
char, both singly and as strings. However, it doesn't say what it means to 
extract a <TT>char</TT> from a <TT>basic_streambuf&lt;charT, Traits&gt;</TT>. 
</P>
<P>basic_streambuf, after all, has no members to extract a char, so 
basic_istream must somehow convert from charT to signed char or unsigned char. 
The standard doesn't say how it is to perform that conversion. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The Standard is correct as written. There is no such extractor and this is 
the intent of the LWG.</P>
<HR>
<A name=65>
<H3>65.&nbsp;Underspecification of strstreambuf::seekoff</H3></A>
<P><B>Section:</B>&nbsp;D.7.1.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/future.html#depr.strstreambuf.virtuals">[depr.strstreambuf.virtuals]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Matt Austern&nbsp; <B>Date:</B>&nbsp;18 Aug 1998</P>
<P>The standard says how this member function affects the current stream 
position. (<TT>gptr</TT> or <TT>pptr</TT>) However, it does not say how this 
member function affects the beginning and end of the get/put area. </P>
<P>This is an issue when seekoff is used to position the get pointer beyond the 
end of the current read area. (Which is legal. This is implicit in the 
definition of <I>seekhigh</I> in D.7.1, paragraph 4.) </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The LWG agrees that seekoff() is underspecified, but does not wish to invest 
effort in this deprecated feature.</P>
<HR>
<A name=67>
<H3>67.&nbsp;Setw useless for strings</H3></A>
<P><B>Section:</B>&nbsp;21.3.7.9 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.string.io">[lib.string.io]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Steve Clamage&nbsp; <B>Date:</B>&nbsp;9 Jul 1998</P>
<P>In a comp.std.c++ posting Michel Michaud wrote: What should be output by: 
</P><PRE>   string text("Hello");
   cout &lt;&lt; '[' &lt;&lt; setw(10) &lt;&lt; right &lt;&lt; text &lt;&lt; ']';
</PRE>
<P>Shouldn't it be:</P><PRE>   [     Hello]</PRE>
<P>Another person replied: Actually, according to the FDIS, the width of the 
field should be the minimum of width and the length of the string, so the output 
shouldn't have any padding. I think that this is a typo, however, and that what 
is wanted is the maximum of the two. (As written, setw is useless for strings. 
If that had been the intent, one wouldn't expect them to have mentioned using 
its value.) </P>
<P>It's worth pointing out that this is a recent correction anyway; IIRC, 
earlier versions of the draft forgot to mention formatting parameters 
whatsoever.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Duplicate. See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#25">25</A>.</P>
<HR>
<A name=72>
<H3>72.&nbsp;Do_convert phantom member function</H3></A>
<P><B>Section:</B>&nbsp;22.2.1.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.codecvt">[lib.locale.codecvt]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nathan Myers&nbsp; <B>Date:</B>&nbsp;24 Aug 1998</P>
<P>In 22.2.1.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.codecvt">[lib.locale.codecvt]</A> 
par 3, and in 22.2.1.5.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.codecvt.virtuals">[lib.locale.codecvt.virtuals]</A> 
par 8, a nonexistent member function "do_convert" is mentioned. This member was 
replaced with "do_in" and "do_out", the proper referents in the contexts 
above.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Duplicate: see issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#24">24</A>.</P>
<HR>
<A name=73>
<H3>73.&nbsp;<TT>is_open</TT> should be const</H3></A>
<P><B>Section:</B>&nbsp;27.8.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.fstreams">[lib.fstreams]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Matt Austern&nbsp; <B>Date:</B>&nbsp;27 Aug 1998</P>
<P>Classes <TT>basic_ifstream</TT>, <TT>basic_ofstream</TT>, and 
<TT>basic_fstream</TT> all have a member function <TT>is_open</TT>. It should be 
a <TT>const</TT> member function, since it does nothing but call one of 
<TT>basic_filebuf</TT>'s const member functions. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Not a defect. This is a deliberate feature; const streams would be 
meaningless.</P>
<HR>
<A name=77>
<H3>77.&nbsp;Valarray operator[] const returning value</H3></A>
<P><B>Section:</B>&nbsp;26.3.2.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.valarray.access">[lib.valarray.access]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Levente Farkas&nbsp; <B>Date:</B>&nbsp;9 Sep 1998</P>
<P>valarray:<BR><BR>&nbsp;&nbsp;&nbsp; <TT>T operator[] (size_t) 
const;</TT><BR><BR>why not <BR><BR>&nbsp;&nbsp;&nbsp; <TT>const T&amp; 
operator[] (size_t) const;</TT><BR><BR>as in vector ???<BR><BR>One can't copy 
even from a const valarray eg:<BR><BR>&nbsp;&nbsp;&nbsp; <TT>memcpy(ptr, 
&amp;v[0], v.size() * sizeof(double));<BR></TT><BR>[I] find this bug in valarray 
is very difficult.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The LWG believes that the interface was deliberately designed that way. That 
is what valarray was designed to do; that's where the "value array" name comes 
from. LWG members further comment that "we don't want valarray to be a full STL 
container." 26.3.2.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.valarray.access">[lib.valarray.access]</A> 
specifies properties that indicate "an absence of aliasing" for non-constant 
arrays; this allows optimizations, including special hardware optimizations, 
that are not otherwise possible. </P>
<HR>
<A name=81>
<H3>81.&nbsp;Wrong declaration of slice operations</H3></A>
<P><B>Section:</B>&nbsp;26.3.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.template.slice.array">[lib.template.slice.array]</A>, 
26.3.7 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.template.gslice.array">[lib.template.gslice.array]</A>, 
26.3.8 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.template.mask.array">[lib.template.mask.array]</A>, 
26.3.9 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.template.indirect.array">[lib.template.indirect.array]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nico Josuttis&nbsp; <B>Date:</B>&nbsp;29 Sep 1998</P>
<P>Isn't the definition of copy constructor and assignment operators wrong? 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Instead of</P><PRE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; slice_array(const slice_array&amp;); 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; slice_array&amp; operator=(const slice_array&amp;);</PRE>
<P>IMHO they have to be</P><PRE>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;slice_array(const slice_array&lt;T&gt;&amp;); 
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;slice_array&amp; operator=(const slice_array&lt;T&gt;&amp;);</PRE>
<P>Same for gslice_array. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Not a defect. The Standard is correct as written. </P>
<HR>
<A name=82>
<H3>82.&nbsp;Missing constant for set elements</H3></A>
<P><B>Section:</B>&nbsp;23.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.associative.reqmts">[lib.associative.reqmts]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nico Josuttis&nbsp; <B>Date:</B>&nbsp;29 Sep 1998</P>
<P>Paragraph 5 specifies:</P>
<BLOCKQUOTE>For set and multiset the value type is the same as the key type. 
  For map and multimap it is equal to pair&lt;const Key, T&gt;. </BLOCKQUOTE>
<P>Strictly speaking, this is not correct because for set and multiset the value 
type is the same as the <B>constant</B> key type.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Not a defect. The Standard is correct as written; it uses a different 
mechanism (const &amp;) for <TT>set</TT> and <TT>multiset</TT>. See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#103">103</A> 
for a related issue.</P>
<HR>
<A name=84>
<H3>84.&nbsp;Ambiguity with string::insert()</H3></A>
<P><B>Section:</B>&nbsp;21.3.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.string.modifiers">[lib.string.modifiers]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nico Josuttis&nbsp; <B>Date:</B>&nbsp;29 Sep 1998</P>
<P>If I try</P><PRE>    s.insert(0,1,' ');</PRE>
<P>&nbsp; I get an nasty ambiguity. It might be</P><PRE>    s.insert((size_type)0,(size_type)1,(charT)' ');</PRE>
<P>which inserts 1 space character at position 0, or</P><PRE>    s.insert((char*)0,(size_type)1,(charT)' ')</PRE>
<P>which inserts 1 space character at iterator/address 0 (bingo!), or</P><PRE>    s.insert((char*)0, (InputIterator)1, (InputIterator)' ')</PRE>
<P>which normally inserts characters from iterator 1 to iterator ' '. But 
according to 23.1.1.9 (the "do the right thing" fix) it is equivalent to the 
second. However, it is still ambiguous, because of course I mean the first!</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Not a defect. The LWG believes this is a "genetic misfortune" inherent in the 
design of string and thus not a defect in the Standard as such .</P>
<HR>
<A name=85>
<H3>85.&nbsp;String char types</H3></A>
<P><B>Section:</B>&nbsp;21 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.strings">[lib.strings]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nico Josuttis&nbsp; <B>Date:</B>&nbsp;29 Sep 1998</P>
<P>The standard seems not to require that charT is equivalent to 
traits::char_type. So, what happens if charT is not equivalent to 
traits::char_type?</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>There is already wording in 21.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.char.traits">[lib.char.traits]</A> 
paragraph 3 that requires them to be the same.</P>
<HR>
<A name=87>
<H3>87.&nbsp;Error in description of string::compare()</H3></A>
<P><B>Section:</B>&nbsp;21.3.6.8 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.string::compare">[lib.string::compare]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nico Josuttis&nbsp; <B>Date:</B>&nbsp;29 Sep 1998</P>
<P>The following compare() description is obviously a bug:</P><PRE>int compare(size_type pos, size_type n1, 
            charT *s, size_type n2 = npos) const;
</PRE>
<P>because without passing n2 it should compare up to the end of the string 
instead of comparing npos characters (which throws an exception) </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Duplicate; see issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#5">5</A>.</P>
<HR>
<A name=88>
<H3>88.&nbsp;Inconsistency between string::insert() and 
string::append()</H3></A>
<P><B>Section:</B>&nbsp;21.3.5.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.string::insert">[lib.string::insert]</A>, 
21.3.5.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.string::append">[lib.string::append]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nico Josuttis&nbsp; <B>Date:</B>&nbsp;29 Sep 1998</P>
<P>Why does </P><PRE>  template&lt;class InputIterator&gt; 
       basic_string&amp; append(InputIterator first, InputIterator last);</PRE>
<P>return a string, while</P><PRE>  template&lt;class InputIterator&gt; 
       void insert(iterator p, InputIterator first, InputIterator last);</PRE>
<P>returns nothing ?</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The LWG believes this stylistic inconsistency is not sufficiently serious to 
constitute a defect.</P>
<HR>
<A name=89>
<H3>89.&nbsp;Missing throw specification for string::insert() and 
string::replace()</H3></A>
<P><B>Section:</B>&nbsp;21.3.5.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.string::insert">[lib.string::insert]</A>, 
21.3.5.6 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.string::replace">[lib.string::replace]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nico Josuttis&nbsp; <B>Date:</B>&nbsp;29 Sep 1998</P>
<P>All insert() and replace() members for strings with an iterator as first 
argument lack a throw specification. The throw specification should probably be: 
length_error if size exceeds maximum. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Considered a duplicate because it will be solved by the resolution of issue 
<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#83">83</A>.</P>
<HR>
<A name=93>
<H3>93.&nbsp;Incomplete Valarray Subset Definitions</H3></A>
<P><B>Section:</B>&nbsp;26.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.numarray">[lib.numarray]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nico Josuttis&nbsp; <B>Date:</B>&nbsp;29 Sep 1998</P>
<P>You can easily create subsets, but you can't easily combine them with other 
subsets. Unfortunately, you almost always needs an explicit type conversion to 
valarray. This is because the standard does not specify that valarray subsets 
provide the same operations as valarrays. </P>
<P>For example, to multiply two subsets and assign the result to a third subset, 
you can't write the following:</P><PRE>va[slice(0,4,3)] = va[slice(1,4,3)] * va[slice(2,4,3)];</PRE>
<P>Instead, you have to code as follows:</P><PRE>va[slice(0,4,3)] = static_cast&lt;valarray&lt;double&gt; &gt;(va[slice(1,4,3)]) * 
                   static_cast&lt;valarray&lt;double&gt; &gt;(va[slice(2,4,3)]);</PRE>
<P>This is tedious and error-prone. Even worse, it costs performance because 
each cast creates a temporary objects, which could be avoided without the cast. 
</P>
<P><B>Proposed resolution:</B></P>
<P>Extend all valarray subset types so that they offer all valarray 
operations.</P>
<P><B>Rationale:</B></P>
<P>This is not a defect in the Standard; it is a request for an extension.</P>
<HR>
<A name=94>
<H3>94.&nbsp;May library implementors add template parameters to Standard 
Library classes?</H3></A>
<P><B>Section:</B>&nbsp;17.4.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-intro.html#lib.conforming">[lib.conforming]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Matt Austern&nbsp; <B>Date:</B>&nbsp;22 Jan 1998</P>
<P>Is it a permitted extension for library implementors to add template 
parameters to standard library classes, provided that those extra parameters 
have defaults? For example, instead of defining <TT>template &lt;class T, class 
Alloc = allocator&lt;T&gt; &gt; class vector;</TT> defining it as <TT>template 
&lt;class T, class Alloc = allocator&lt;T&gt;, int N = 1&gt; class vector;</TT> 
</P>
<P>The standard may well already allow this (I can't think of any way that this 
extension could break a conforming program, considering that users are not 
permitted to forward-declare standard library components), but it ought to be 
explicitly permitted or forbidden. </P>
<P>comment from Steve Cleary via comp.std.c++:</P>
<BLOCKQUOTE>
  <P>I disagree [with the proposed resolution] for the following reason: 
  consider user library code with template template parameters. For example, a 
  user library object may be templated on the type of underlying sequence 
  storage to use (deque/list/vector), since these classes all take the same 
  number and type of template parameters; this would allow the user to determine 
  the performance tradeoffs of the user library object. A similar example is a 
  user library object templated on the type of underlying set storage 
  (set/multiset) or map storage (map/multimap), which would allow users to 
  change (within reason) the semantic meanings of operations on that object.</P>
  <P>I think that additional template parameters should be forbidden in the 
  Standard classes. Library writers don't lose any expressive power, and can 
  still offer extensions because additional template parameters may be provided 
  by a non-Standard implementation class:</P><PRE> 
   template &lt;class T, class Allocator = allocator&lt;T&gt;, int N = 1&gt;
   class __vector
   { ... };
   template &lt;class T, class Allocator = allocator&lt;T&gt; &gt;
   class vector: public __vector&lt;T, Allocator&gt;
   { ... };
</PRE></BLOCKQUOTE>
<P><B>Proposed resolution:</B></P>
<P>Add a new subclause [presumably 17.4.4.9] following 17.4.4.8 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-intro.html#lib.res.on.exception.handling">[lib.res.on.exception.handling]</A>:</P>
<BLOCKQUOTE>
  <P>17.4.4.9 Template Parameters</P>
  <P>A specialization of a template class described in the C++ Standard Library 
  behaves the same as if the implementation declares no additional template 
  parameters.</P>
  <P>Footnote: Additional template parameters with default values are thus 
  permitted.</P></BLOCKQUOTE>
<P>Add "template parameters" to the list of subclauses at the end of 17.4.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-intro.html#lib.conforming">[lib.conforming]</A> 
paragraph 1.</P>
<P><I>[Kona: The LWG agreed the standard needs clarification. After discussion 
with John Spicer, it seems added template parameters can be detected by a 
program using template-template parameters. A straw vote - "should implementors 
be allowed to add template parameters?" found no consensus ; 5 - yes, 7 - 
no.]</I></P>
<P><B>Rationale:</B></P>
<P>There is no ambiguity; the standard is clear as written. Library implementors 
are not permitted to add template parameters to standard library classes. This 
does not fall under the "as if" rule, so it would be permitted only if the 
standard gave explicit license for implementors to do this. This would require a 
change in the standard. </P>
<P>The LWG decided against making this change, because it would break user code 
involving template template parameters or specializations of standard library 
class templates. </P>
<HR>
<A name=95>
<H3>95.&nbsp;Members added by the implementation</H3></A>
<P><B>Section:</B>&nbsp;17.4.4.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-intro.html#lib.member.functions">[lib.member.functions]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;AFNOR&nbsp; <B>Date:</B>&nbsp;7 Oct 1998</P>
<P>In 17.3.4.4/2 vs 17.3.4.7/0 there is a hole; an implementation could add 
virtual members a base class and break user derived classes.</P>
<P>Example: </P>
<BLOCKQUOTE><PRE>// implementation code:
struct _Base { // _Base is in the implementer namespace
        virtual void foo ();
};
class vector : _Base // deriving from a class is allowed
{ ... };

// user code:
class vector_checking : public vector 
{
        void foo (); // don't want to override _Base::foo () as the 
                     // user doesn't know about _Base::foo ()
};</PRE></BLOCKQUOTE>
<P><B>Proposed resolution:</B></P>
<P>Clarify the wording to make the example illegal.</P>
<P><B>Rationale:</B></P>
<P>This is not a defect in the Standard.&nbsp; The example is already 
illegal.&nbsp; See 17.4.4.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-intro.html#lib.member.functions">[lib.member.functions]</A> 
paragraph 2.</P>
<HR>
<A name=97>
<H3>97.&nbsp;Insert inconsistent definition</H3></A>
<P><B>Section:</B>&nbsp;23 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.containers">[lib.containers]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;AFNOR&nbsp; <B>Date:</B>&nbsp;7 Oct 1998</P>
<P><TT>insert(iterator, const value_type&amp;)</TT> is defined both on sequences 
and on set, with unrelated semantics: insert here (in sequences), and insert 
with hint (in associative containers). They should have different names (B.S. 
says: do not abuse overloading).</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>This is not a defect in the Standard. It is a genetic misfortune of the 
design, for better or for worse.</P>
<HR>
<A name=99>
<H3>99.&nbsp;Reverse_iterator comparisons completely wrong</H3></A>
<P><B>Section:</B>&nbsp;24.4.1.3.13 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.reverse.iter.op<">[lib.reverse.iter.op&lt;]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;AFNOR&nbsp; <B>Date:</B>&nbsp;7 Oct 1998</P>
<P>The &lt;, &gt;, &lt;=, &gt;= comparison operator are wrong: they return the 
opposite of what they should.</P>
<P>Note: same problem in CD2, these were not even defined in CD1. SGI STL code 
is correct; this problem is known since the Morristown meeting but there it was 
too late</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>This is not a defect in the Standard. A careful reading shows the Standard is 
correct as written. A review of several implementations show that they implement 
exactly what the Standard says.</P>
<HR>
<A name=100>
<H3>100.&nbsp;Insert iterators/ostream_iterators overconstrained</H3></A>
<P><B>Section:</B>&nbsp;24.4.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.insert.iterators">[lib.insert.iterators]</A>, 
24.5.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.ostreambuf.iterator">[lib.ostreambuf.iterator]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;AFNOR&nbsp; <B>Date:</B>&nbsp;7 Oct 1998</P>
<P>Overspecified For an insert iterator it, the expression *it is required to 
return a reference to it. This is a simple possible implementation, but as the 
SGI STL documentation says, not the only one, and the user should not assume 
that this is the case.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The LWG believes this causes no harm and is not a defect in the standard. The 
only example anyone could come up with caused some incorrect code to work, 
rather than the other way around.</P>
<HR>
<A name=101>
<H3>101.&nbsp;No way to free storage for vector and deque</H3></A>
<P><B>Section:</B>&nbsp;23.2.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.vector">[lib.vector]</A>, 
23.2.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.deque">[lib.deque]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;AFNOR&nbsp; <B>Date:</B>&nbsp;7 Oct 1998</P>
<P>Reserve can not free storage, unlike string::reserve</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>This is not a defect in the Standard. The LWG has considered this issue in 
the past and sees no need to change the Standard. Deque has no reserve() member 
function. For vector, shrink-to-fit can be expressed in a single line of code 
(where <TT>v</TT> is <TT>vector&lt;T&gt;</TT>): </P>
<BLOCKQUOTE>
  <P><TT>vector&lt;T&gt;(v).swap(v);&nbsp; // shrink-to-fit 
v</TT></P></BLOCKQUOTE>
<HR>
<A name=102>
<H3>102.&nbsp;Bug in insert range in associative containers</H3></A>
<P><B>Section:</B>&nbsp;23.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.associative.reqmts">[lib.associative.reqmts]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;AFNOR&nbsp; <B>Date:</B>&nbsp;7 Oct 1998</P>
<P>Table 69 of Containers say that a.insert(i,j) is linear if [i, j) is ordered. 
It seems impossible to implement, as it means that if [i, j) = [x], insert in an 
associative container is O(1)!</P>
<P><B>Proposed resolution:</B></P>
<P>N+log (size()) if [i,j) is sorted according to value_comp()</P>
<P><B>Rationale:</B></P>
<P>Subsumed by issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#264">264</A>.</P>
<HR>
<A name=104>
<H3>104.&nbsp;Description of basic_string::operator[] is unclear</H3></A>
<P><B>Section:</B>&nbsp;21.3.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.string.access">[lib.string.access]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;AFNOR&nbsp; <B>Date:</B>&nbsp;7 Oct 1998</P>
<P>It is not clear that undefined behavior applies when pos == size () for the 
non const version.</P>
<P><B>Proposed resolution:</B></P>
<P>Rewrite as: Otherwise, if pos &gt; size () or pos == size () and the 
non-const version is used, then the behavior is undefined.</P>
<P><B>Rationale:</B></P>
<P>The Standard is correct. The proposed resolution already appears in the 
Standard.</P>
<HR>
<A name=105>
<H3>105.&nbsp;fstream ctors argument types desired</H3></A>
<P><B>Section:</B>&nbsp;27.8 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.file.streams">[lib.file.streams]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;AFNOR&nbsp; <B>Date:</B>&nbsp;7 Oct 1998</P>
<P>fstream ctors take a const char* instead of string.<BR>fstream ctors can't 
take wchar_t</P>
<P>An extension to add a const wchar_t* to fstream would make the implementation 
non conforming.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>This is not a defect in the Standard. It might be an interesting extension 
for the next Standard. </P>
<HR>
<A name=107>
<H3>107.&nbsp;Valarray constructor is strange</H3></A>
<P><B>Section:</B>&nbsp;26.3.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.template.valarray">[lib.template.valarray]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;AFNOR&nbsp; <B>Date:</B>&nbsp;7 Oct 1998</P>
<P>The order of the arguments is (elem, size) instead of the normal (size, elem) 
in the rest of the library. Since elem often has an integral or floating point 
type, both types are convertible to each other and reversing them leads to a 
well formed program.</P>
<P><B>Proposed resolution:</B></P>
<P>Inverting the arguments could silently break programs. Introduce the two 
signatures (const T&amp;, size_t) and (size_t, const T&amp;), but make the one 
we do not want private so errors result in a diagnosed access violation. This 
technique can also be applied to STL containers.</P>
<P><B>Rationale:</B></P>
<P>The LWG believes that while the order of arguments is unfortunate, it does 
not constitute a defect in the standard. The LWG believes that the proposed 
solution will not work for valarray&lt;size_t&gt; and perhaps other cases.</P>
<HR>
<A name=111>
<H3>111.&nbsp;istreambuf_iterator::equal overspecified, inefficient</H3></A>
<P><B>Section:</B>&nbsp;24.5.3.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.istreambuf.iterator::equal">[lib.istreambuf.iterator::equal]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nathan Myers&nbsp; <B>Date:</B>&nbsp;15 Oct 1998</P>
<P>The member istreambuf_iterator&lt;&gt;::equal is specified to be 
unnecessarily inefficient. While this does not affect the efficiency of 
conforming implementations of iostreams, because they can "reach into" the 
iterators and bypass this function, it does affect users who use 
istreambuf_iterators. </P>
<P>The inefficiency results from a too-scrupulous definition, which requires a 
"true" result if neither iterator is at eof. In practice these iterators can 
only usefully be compared with the "eof" value, so the extra test implied 
provides no benefit, but slows down users' code. </P>
<P>The solution is to weaken the requirement on the function to return true only 
if both iterators are at eof. </P>
<P><B>Proposed resolution:</B></P>
<P>Replace 24.5.3.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.istreambuf.iterator::equal">[lib.istreambuf.iterator::equal]</A>, 
paragraph 1, </P>
<BLOCKQUOTE>
  <P>-1- Returns: true if and only if both iterators are at end-of-stream, or 
  neither is at end-of-stream, regardless of what streambuf object they use. 
</P></BLOCKQUOTE>
<P>with</P>
<BLOCKQUOTE>
  <P>-1- Returns: true if and only if both iterators are at end-of-stream, 
  regardless of what streambuf object they use. </P></BLOCKQUOTE>
<P><B>Rationale:</B></P>
<P>It is not clear that this is a genuine defect. Additionally, the LWG was 
reluctant to make a change that would result in operator== not being a 
equivalence relation. One consequence of this change is that an algorithm that's 
passed the range [i, i) would no longer treat it as an empty range.</P>
<HR>
<A name=113>
<H3>113.&nbsp;Missing/extra iostream sync semantics</H3></A>
<P><B>Section:</B>&nbsp;27.6.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.istream">[lib.istream]</A>, 
27.6.1.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.istream.unformatted">[lib.istream.unformatted]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Steve Clamage&nbsp; <B>Date:</B>&nbsp;13 Oct 1998</P>
<P>In 27.6.1.1, class basic_istream has a member function sync, described in 
27.6.1.3, paragraph 36. </P>
<P>Following the chain of definitions, I find that the various sync functions 
have defined semantics for output streams, but no semantics for input streams. 
On the other hand, basic_ostream has no sync function. </P>
<P>The sync function should at minimum be added to basic_ostream, for internal 
consistency. </P>
<P>A larger question is whether sync should have assigned semantics for input 
streams. </P>
<P>Classic iostreams said streambuf::sync flushes pending output and attempts to 
return unread input characters to the source. It is a protected member function. 
The filebuf version (which is public) has that behavior (it backs up the read 
pointer). Class strstreambuf does not override streambuf::sync, and so sync 
can't be called on a strstream. </P>
<P>If we can add corresponding semantics to the various sync functions, we 
should. If not, we should remove sync from basic_istream.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>A sync function is not needed in basic_ostream because the flush function 
provides the desired functionality.</P>
<P>As for the other points, the LWG finds the standard correct as written.</P>
<HR>
<A name=116>
<H3>116.&nbsp;bitset cannot be constructed with a const char*</H3></A>
<P><B>Section:</B>&nbsp;23.3.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.template.bitset">[lib.template.bitset]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Judy Ward&nbsp; <B>Date:</B>&nbsp;6 Nov 1998</P>
<P>The following code does not compile with the EDG compiler:</P>
<BLOCKQUOTE><PRE>#include &lt;bitset&gt;
using namespace std;
bitset&lt;32&gt; b("111111111");</PRE></BLOCKQUOTE>
<P>If you cast the ctor argument to a string, i.e.:</P>
<BLOCKQUOTE><PRE>bitset&lt;32&gt; b(string("111111111"));</PRE></BLOCKQUOTE>
<P>then it will compile. The reason is that bitset has the following templatized 
constructor:</P>
<BLOCKQUOTE><PRE>template &lt;class charT, class traits, class Allocator&gt;
explicit bitset (const basic_string&lt;charT, traits, Allocator&gt;&amp; str, ...);</PRE></BLOCKQUOTE>
<P>According to the compiler vendor, Steve Adamcyk at EDG, the user cannot pass 
this template constructor a <TT>const char*</TT> and expect a conversion to 
<TT>basic_string</TT>. The reason is "When you have a template constructor, it 
can get used in contexts where type deduction can be done. Type deduction 
basically comes up with exact matches, not ones involving conversions." </P>
<P>I don't think the intention when this constructor became templatized was for 
construction from a <TT>const char*</TT> to no longer work.</P>
<P><B>Proposed resolution:</B></P>
<P>Add to 23.3.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.template.bitset">[lib.template.bitset]</A> 
a bitset constructor declaration</P>
<BLOCKQUOTE><PRE>explicit bitset(const char*);</PRE></BLOCKQUOTE>
<P>and in Section 23.3.5.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.bitset.cons">[lib.bitset.cons]</A> 
add:</P>
<BLOCKQUOTE><PRE>explicit bitset(const char* str);</PRE>
  <P>Effects: <BR>&nbsp;&nbsp;&nbsp; Calls <TT>bitset((string) str, 0, 
  string::npos);</TT></P></BLOCKQUOTE>
<P><B>Rationale:</B></P>
<P>Although the problem is real, the standard is designed that way so it is not 
a defect. Education is the immediate workaround. A future standard may wish to 
consider the Proposed Resolution as an extension.</P>
<HR>
<A name=121>
<H3>121.&nbsp;Detailed definition for ctype&lt;wchar_t&gt; 
specialization</H3></A>
<P><B>Section:</B>&nbsp;22.1.1.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.category">[lib.locale.category]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Judy Ward&nbsp; <B>Date:</B>&nbsp;15 Dec 1998</P>
<P>Section 22.1.1.1.1 has the following listed in Table 51: ctype&lt;char&gt; , 
ctype&lt;wchar_t&gt;. </P>
<P>Also Section 22.2.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.ctype">[lib.locale.ctype]</A> 
says: </P>
<BLOCKQUOTE>
  <P>The instantiations required in Table 51 (22.1.1.1.1) namely 
  ctype&lt;char&gt; and ctype&lt;wchar_t&gt; , implement character classing 
  appropriate to the implementation's native character set. </P></BLOCKQUOTE>
<P>However, Section 22.2.1.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.facet.ctype.special">[lib.facet.ctype.special]</A> 
only has a detailed description of the ctype&lt;char&gt; specialization, not the 
ctype&lt;wchar_t&gt; specialization. </P>
<P><B>Proposed resolution:</B></P>
<P>Add the ctype&lt;wchar_t&gt; detailed class description to Section 22.2.1.3 
<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.facet.ctype.special">[lib.facet.ctype.special]</A>. 
</P>
<P><B>Rationale:</B></P>
<P>Specialization for wchar_t is not needed since the default is acceptable.</P>
<HR>
<A name=128>
<H3>128.&nbsp;Need open_mode() function for file stream, string streams, file 
buffers, and string&nbsp; buffers</H3></A>
<P><B>Section:</B>&nbsp;27.7 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.string.streams">[lib.string.streams]</A>, 
27.8 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.file.streams">[lib.file.streams]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Angelika Langer&nbsp; <B>Date:</B>&nbsp;22 Feb 1999</P>
<P>The following question came from Thorsten Herlemann:</P>
<BLOCKQUOTE>
  <P>You can set a mode when constructing or opening a file-stream or filebuf, 
  e.g. ios::in, ios::out, ios::binary, ... But how can I get that mode later on, 
  e.g. in my own operator &lt;&lt; or operator &gt;&gt; or when I want to check 
  whether a file-stream or file-buffer object passed as parameter is opened for 
  input or output or binary? Is there no possibility? Is this a design-error in 
  the standard C++ library? </P></BLOCKQUOTE>
<P>It is indeed impossible to find out what a stream's or stream buffer's open 
mode is, and without that knowledge you don't know how certain operations 
behave. Just think of the append mode. </P>
<P>Both streams and stream buffers should have a <TT>mode()</TT> function that 
returns the current open mode setting. </P>
<P><B>Proposed resolution:</B></P>
<P>For stream buffers, add a function to the base class as a non-virtual 
function qualified as const to 27.5.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.streambuf">[lib.streambuf]</A>:</P>
<P>&nbsp;&nbsp;&nbsp;&nbsp;<TT>openmode mode() const</TT>;</P>
<P><B>&nbsp;&nbsp;&nbsp; Returns</B> the current open mode.</P>
<P>With streams, I'm not sure what to suggest. In principle, the mode could 
already be returned by <TT>ios_base</TT>, but the mode is only initialized for 
file and string stream objects, unless I'm overlooking anything. For this reason 
it should be added to the most derived stream classes. Alternatively, it could 
be added to <TT>basic_ios</TT> and would be default initialized in 
<TT>basic_ios&lt;&gt;::init()</TT>.</P>
<P><B>Rationale:</B></P>
<P>This might be an interesting extension for some future, but it is not a 
defect in the current standard. The Proposed Resolution is retained for future 
reference.</P>
<HR>
<A name=131>
<H3>131.&nbsp;list::splice throws nothing</H3></A>
<P><B>Section:</B>&nbsp;23.2.2.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.list.ops">[lib.list.ops]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Howard Hinnant&nbsp; <B>Date:</B>&nbsp;6 Mar 1999</P>
<P>What happens if a splice operation causes the size() of a list to grow beyond 
max_size()?</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Size() cannot grow beyond max_size().&nbsp; </P>
<HR>
<A name=135>
<H3>135.&nbsp;basic_iostream doubly initialized</H3></A>
<P><B>Section:</B>&nbsp;27.6.1.5.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.iostream.cons">[lib.iostream.cons]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Howard Hinnant&nbsp; <B>Date:</B>&nbsp;6 Mar 1999</P>
<P>-1- Effects Constructs an object of class basic_iostream, assigning initial 
values to the base classes by calling basic_istream&lt;charT,traits&gt;(sb) 
(lib.istream) and basic_ostream&lt;charT,traits&gt;(sb) (lib.ostream)</P>
<P>The called for basic_istream and basic_ostream constructors call init(sb). 
This means that the basic_iostream's virtual base class is initialized 
twice.</P>
<P><B>Proposed resolution:</B></P>
<P>Change 27.6.1.5.1, paragraph 1 to:</P>
<P>-1- Effects Constructs an object of class basic_iostream, assigning initial 
values to the base classes by calling basic_istream&lt;charT,traits&gt;(sb) 
(lib.istream).</P>
<P><B>Rationale:</B></P>
<P>The LWG agreed that the <TT>init()</TT> function is called twice, but said 
that this is harmless and so not a defect in the standard.</P>
<HR>
<A name=138>
<H3>138.&nbsp;Class ctype_byname&lt;char&gt; redundant and misleading</H3></A>
<P><B>Section:</B>&nbsp;22.2.1.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.ctype.byname.special">[lib.locale.ctype.byname.special]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Angelika Langer&nbsp; <B>Date:</B>&nbsp;March 18, 
1999</P>
<P>Section 22.2.1.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.ctype.byname.special">[lib.locale.ctype.byname.special]</A> 
specifies that ctype_byname&lt;char&gt; must be a specialization of the 
ctype_byname template.</P>
<P>It is common practice in the standard that specializations of class templates 
are only mentioned where the interface of the specialization deviates from the 
interface of the template that it is a specialization of. Otherwise, the fact 
whether or not a required instantiation is an actual instantiation or a 
specialization is left open as an implementation detail. </P>
<P>Clause 22.2.1.4 deviates from that practice and for that reason is 
misleading. The fact, that ctype_byname&lt;char&gt; is specified as a 
specialization suggests that there must be something "special" about it, but it 
has the exact same interface as the ctype_byname template. Clause 22.2.1.4 does 
not have any explanatory value, is at best redundant, at worst misleading - 
unless I am missing anything. </P>
<P>Naturally, an implementation will most likely implement 
ctype_byname&lt;char&gt; as a specialization, because the base class 
ctype&lt;char&gt; is a specialization with an interface different from the ctype 
template, but that's an implementation detail and need not be mentioned in the 
standard. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The standard as written is mildly misleading, but the correct fix is to deal 
with the underlying problem in the ctype_byname base class, not in the 
specialization. See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#228">228</A>.</P>
<HR>
<A name=140>
<H3>140.&nbsp;map&lt;Key, T&gt;::value_type does not satisfy the assignable 
requirement</H3></A>
<P><B>Section:</B>&nbsp;23.3.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.map">[lib.map]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Mark Mitchell&nbsp; <B>Date:</B>&nbsp;14 Apr 1999</P>
<BLOCKQUOTE>
  <P>23.1 <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.container.requirements">[lib.container.requirements]</A><BR><BR>expression&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  return type &nbsp;&nbsp;&nbsp;&nbsp; 
  pre/post-condition<BR>-------------&nbsp;&nbsp;&nbsp;&nbsp; ----------- 
  &nbsp;&nbsp;&nbsp;&nbsp; 
  -------------------<BR>X::value_type&nbsp;&nbsp;&nbsp; T 
  &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
  T is assignable<BR><BR>23.3.1 <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.map">[lib.map]</A><BR><BR>A 
  map satisfies all the requirements of a container.<BR><BR>For a map&lt;Key, 
  T&gt; ... the value_type is pair&lt;const Key, T&gt;.</P></BLOCKQUOTE>
<P>There's a contradiction here. In particular, `pair&lt;const Key, T&gt;' is 
not assignable; the `const Key' cannot be assigned to. So,&nbsp; map&lt;Key, 
T&gt;::value_type does not satisfy the assignable requirement imposed by a 
container.</P>
<P><I>[See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#103">103</A> 
for the slightly related issue of modification of set keys.]</I></P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The LWG believes that the standard is inconsistent, but that this is a design 
problem rather than a strict defect. May wish to reconsider for the next 
standard.</P>
<HR>
<A name=143>
<H3>143.&nbsp;C .h header wording unclear</H3></A>
<P><B>Section:</B>&nbsp;D.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/future.html#depr.c.headers">[depr.c.headers]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Christophe de Dinechin&nbsp; <B>Date:</B>&nbsp;4 May 
1999</P>
<P>[depr.c.headers] paragraph 2 reads:</P>
<BLOCKQUOTE>
  <P>Each C header, whose name has the form name.h, behaves as if each name 
  placed in the Standard library namespace by the corresponding cname header is 
  also placed within the namespace scope of the namespace std and is followed by 
  an explicit using-declaration (_namespace.udecl_)</P></BLOCKQUOTE>
<P>I think it should mention the global name space somewhere...&nbsp; Currently, 
it indicates that name placed in std is also placed in std...</P>
<P>I don't know what is the correct wording. For instance, if struct tm is 
defined in time.h, ctime declares std::tm. However, the current wording seems 
ambiguous regarding which of the following would occur for use of both ctime and 
time.h:</P>
<BLOCKQUOTE><PRE>// version 1:
namespace std {
        struct tm { ... };
}
using std::tm;

// version 2:
struct tm { ... };
namespace std {
        using ::tm;
}

// version 3:
struct tm { ... };
namespace std {
        struct tm { ... };
}</PRE></BLOCKQUOTE>
<P>I think version 1 is intended.</P>
<P><I>[Kona: The LWG agreed that the wording is not clear. It also agreed that 
version 1 is intended, version 2 is not equivalent to version 1, and version 3 
is clearly not intended. The example below was constructed by Nathan Myers to 
illustrate why version 2 is not equivalent to version 1.</I></P>
<P><I>Although not equivalent, the LWG is unsure if (2) is enough of a problem 
to be prohibited. Points discussed in favor of allowing (2):</I></P>
<BLOCKQUOTE>
  <UL>
    <LI><I>It may be a convenience to implementors.</I> 
    <LI><I>The only cases that fail are structs, of which the C library contains 
    only a few.</I> </LI></UL></BLOCKQUOTE>
<P><I>]</I></P>
<P><B>Example:</B></P>
<BLOCKQUOTE><PRE>#include &lt;time.h&gt;
#include &lt;utility&gt;

int main() {
    std::tm * t;
    make_pair( t, t ); // okay with version 1 due to Koenig lookup
                       // fails with version 2; make_pair not found
    return 0;
}</PRE></BLOCKQUOTE>
<P><B>Proposed resolution:</B></P>
<P>Replace D.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/future.html#depr.c.headers">[depr.c.headers]</A> 
paragraph 2 with:</P>
<BLOCKQUOTE>
  <P>Each C header, whose name has the form name.h, behaves as if each name 
  placed in the Standard library namespace by the corresponding cname header is 
  also placed within the namespace scope of the namespace std by name.h and is 
  followed by an explicit using-declaration (_namespace.udecl_) in global 
  scope.</P></BLOCKQUOTE>
<P><B>Rationale:</B></P>
<P>The current wording in the standard is the result of a difficult compromise 
that averted delay of the standard. Based on discussions in Tokyo it is clear 
that there is no still no consensus on stricter wording, so the issue has been 
closed. It is suggested that users not write code that depends on Koenig lookup 
of C library functions.</P>
<HR>
<A name=145>
<H3>145.&nbsp;adjustfield lacks default value</H3></A>
<P><B>Section:</B>&nbsp;27.4.4.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.basic.ios.cons">[lib.basic.ios.cons]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Angelika Langer&nbsp; <B>Date:</B>&nbsp;12 May 1999</P>
<P>There is no initial value for the adjustfield defined, although many people 
believe that the default adjustment were right. This is a common 
misunderstanding. The standard only defines that, if no adjustment is specified, 
all the predefined inserters must add fill characters before the actual value, 
which is "as if" the right flag were set. The flag itself need not be set.</P>
<P>When you implement a user-defined inserter you cannot rely on right being the 
default setting for the adjustfield. Instead, you must be prepared to find none 
of the flags set and must keep in mind that in this case you should make your 
inserter behave "as if" the right flag were set. This is surprising to many 
people and complicates matters more than necessary.</P>
<P>Unless there is a good reason why the adjustfield should not be initialized I 
would suggest to give it the default value that everybody expects anyway.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>This is not a defect. It is deliberate that the default is no bits set. 
Consider Arabic or Hebrew, for example. See 22.2.2.2.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.facet.num.put.virtuals">[lib.facet.num.put.virtuals]</A> 
paragraph 19, Table 61 - Fill padding.</P>
<HR>
<A name=149>
<H3>149.&nbsp;Insert should return iterator to first element inserted</H3></A>
<P><B>Section:</B>&nbsp;23.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.sequence.reqmts">[lib.sequence.reqmts]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Andrew Koenig&nbsp; <B>Date:</B>&nbsp;28 Jun 1999</P>
<P>Suppose that c and c1 are sequential containers and i is an iterator that 
refers to an element of c. Then I can insert a copy of c1's elements into c 
ahead of element i by executing </P>
<BLOCKQUOTE><PRE>c.insert(i, c1.begin(), c1.end());</PRE></BLOCKQUOTE>
<P>If c is a vector, it is fairly easy for me to find out where the newly 
inserted elements are, even though i is now invalid: </P>
<BLOCKQUOTE><PRE>size_t i_loc = i - c.begin();
c.insert(i, c1.begin(), c1.end());</PRE></BLOCKQUOTE>
<P>and now the first inserted element is at c.begin()+i_loc and one past the 
last is at c.begin()+i_loc+c1.size().<BR><BR>But what if c is a list? I can 
still find the location of one past the last inserted element, because i is 
still valid. To find the location of the first inserted element, though, I must 
execute something like </P>
<BLOCKQUOTE><PRE>for (size_t n = c1.size(); n; --n)
   --i;</PRE></BLOCKQUOTE>
<P>because i is now no longer a random-access iterator.<BR><BR>Alternatively, I 
might write something like </P>
<BLOCKQUOTE><PRE>bool first = i == c.begin();
list&lt;T&gt;::iterator j = i;
if (!first) --j;
c.insert(i, c1.begin(), c1.end());
if (first)
   j = c.begin();
else
   ++j;</PRE></BLOCKQUOTE>
<P>which, although wretched, requires less overhead.<BR><BR>But I think the 
right solution is to change the definition of insert so that instead of 
returning void, it returns an iterator that refers to the first element 
inserted, if any, and otherwise is a copy of its first argument.&nbsp; </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The LWG believes this was an intentional design decision and so is not a 
defect. It may be worth revisiting for the next standard.</P>
<HR>
<A name=157>
<H3>157.&nbsp;Meaningless error handling for <TT>pword()</TT> and 
<TT>iword()</TT> </H3></A>
<P><B>Section:</B>&nbsp;27.4.2.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.ios.base.storage">[lib.ios.base.storage]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Dietmar Khl&nbsp; <B>Date:</B>&nbsp;20 Jul 1999</P>
<P>According to paragraphs 2 and 4 of 27.4.2.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.ios.base.storage">[lib.ios.base.storage]</A>, 
the functions <TT>iword()</TT> and <TT>pword()</TT> "set the <TT>badbit</TT> 
(which might throw an exception)" on failure. ... but what does it mean for 
<TT>ios_base</TT> to set the <TT>badbit</TT>? The state facilities of the 
IOStream library are defined in <TT>basic_ios</TT>, a derived class! It would be 
possible to attempt a down cast but then it would be necessary to know the 
character type used...</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Duplicate. See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#41">41</A>.</P>
<HR>
<A name=162>
<H3>162.&nbsp;Really "formatted input functions"?</H3></A>
<P><B>Section:</B>&nbsp;27.6.1.2.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.istream::extractors">[lib.istream::extractors]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Dietmar Khl&nbsp; <B>Date:</B>&nbsp;20 Jul 1999</P>
<P>It appears to be somewhat nonsensical to consider the functions defined in 
the 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="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/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>See also issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#166">166</A> 
for the same problem in formatted output</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Duplicate. See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#60">60</A>.</P>
<HR>
<A name=163>
<H3>163.&nbsp;Return of <TT>gcount()</TT> after a call to <TT>gcount</TT> 
</H3></A>
<P><B>Section:</B>&nbsp;27.6.1.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.istream.unformatted">[lib.istream.unformatted]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Dietmar Khl&nbsp; <B>Date:</B>&nbsp;20 Jul 1999</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="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/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 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 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><B>Rationale:</B></P>
<P>Duplicate.&nbsp; See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#60">60</A>.</P>
<HR>
<A name=166>
<H3>166.&nbsp;Really "formatted output functions"?</H3></A>
<P><B>Section:</B>&nbsp;27.6.2.5.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.ostream.inserters">[lib.ostream.inserters]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Dietmar Khl&nbsp; <B>Date:</B>&nbsp;20 Jul 1999</P>
<P>From 27.6.2.5.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.ostream.formatted.reqmts">[lib.ostream.formatted.reqmts]</A> 
it appears that all the functions defined in 27.6.2.5.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.ostream.inserters">[lib.ostream.inserters]</A> 
have to construct a <TT>sentry</TT> object. Is this really intended?</P>
<P>This is basically the same problem as issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#162">162</A> 
but for output instead of input.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Duplicate. See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#60">60</A>.</P>
<HR>
<A name=177>
<H3>177.&nbsp;Complex operators cannot be explicitly instantiated</H3></A>
<P><B>Section:</B>&nbsp;26.2.6 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.complex.ops">[lib.complex.ops]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Judy Ward&nbsp; <B>Date:</B>&nbsp;2 Jul 1999</P>
<P>A user who tries to explicitly instantiate a complex non-member operator will 
get compilation errors. Below is a simplified example of the reason why. The 
problem is that iterator_traits cannot be instantiated on a non-pointer type 
like float, yet when the compiler is trying to decide which operator+ needs to 
be instantiated it must instantiate the declaration to figure out the first 
argument type of a reverse_iterator operator.</P><PRE>namespace std {
template &lt;class Iterator&gt; 
struct iterator_traits
{
    typedef typename Iterator::value_type value_type;
};

template &lt;class T&gt; class reverse_iterator;

// reverse_iterator operator+
template &lt;class T&gt; 
reverse_iterator&lt;T&gt; operator+
(typename iterator_traits&lt;T&gt;::difference_type, const reverse_iterator&lt;T&gt;&amp;);

template &lt;class T&gt; struct complex {};

// complex operator +
template &lt;class T&gt;
complex&lt;T&gt; operator+ (const T&amp; lhs, const complex&lt;T&gt;&amp; rhs) 
{ return complex&lt;T&gt;();} 
}

// request for explicit instantiation
template std::complex&lt;float&gt; std::operator+&lt;float&gt;(const float&amp;, 
     const std::complex&lt;float&gt;&amp;);</PRE>
<P>See also c++-stdlib reflector messages: lib-6814, 6815, 6816.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Implementors can make minor changes and the example will work. Users are not 
affected in any case.</P>
<P>According to John Spicer, It is possible to explicitly instantiate these 
operators using different syntax: change "std::operator+&lt;float&gt;" to 
"std::operator+".</P>
<P>The proposed resolution of issue 120 is that users will not be able to 
explicitly instantiate standard library templates. If that resolution is 
accepted then library implementors will be the only ones that will be affected 
by this problem, and they must use the indicated syntax.</P>
<HR>
<A name=178>
<H3>178.&nbsp;Should clog and cerr initially be tied to cout?</H3></A>
<P><B>Section:</B>&nbsp;27.3.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.narrow.stream.objects">[lib.narrow.stream.objects]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Judy Ward&nbsp; <B>Date:</B>&nbsp;2 Jul 1999</P>
<P>Section 27.3.1 says "After the object cerr is initialized, cerr.flags() &amp; 
unitbuf is nonzero. Its state is otherwise the same as required for 
ios_base::init (lib.basic.ios.cons). It doesn't say anything about the the state 
of clog. So this means that calling cerr.tie() and clog.tie() should return 0 
(see Table 89 for ios_base::init effects). </P>
<P>Neither of the popular standard library implementations that I tried does 
this, they both tie cerr and clog to &amp;cout. I would think that would be what 
users expect. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The standard is clear as written.</P>
<P>27.3.1/5 says that "After the object cerr is initialized, cerr.flags() &amp; 
unitbuf is nonzero. Its state is otherwise the same as required for 
ios_base::init (27.4.4.1)." Table 89 in 27.4.4.1, which gives the postconditions 
of basic_ios::init(), says that tie() is 0. (Other issues correct ios_base::init 
to basic_ios::init().)</P>
<HR>
<A name=180>
<H3>180.&nbsp;Container member iterator arguments constness has unintended 
consequences</H3></A>
<P><B>Section:</B>&nbsp;23 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.containers">[lib.containers]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Dave Abrahams&nbsp; <B>Date:</B>&nbsp;1 Jul 1999</P>
<P>It is the constness of the container which should control whether it can be 
modified through a member function such as erase(), not the constness of the 
iterators. The iterators only serve to give positioning information.</P>
<P>Here's a simple and typical example problem which is currently very difficult 
or impossible to solve without the change proposed below.</P>
<P>Wrap a standard container C in a class W which allows clients to find and 
read (but not modify) a subrange of (C.begin(), C.end()]. The only modification 
clients are allowed to make to elements in this subrange is to erase them from C 
through the use of a member function of W.</P>
<P><B>Proposed resolution:</B></P>
<P>Change all non-const iterator parameters of standard library container member 
functions to accept const_iterator parameters. Note that this change applies to 
all library clauses, including strings.</P>
<P>For example, in 21.3.5.5 change:<BR><BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
<TT>iterator erase(iterator 
p);</TT><BR><BR>to:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <TT>iterator 
erase(const_iterator p);</TT> </P>
<P><B>Rationale:</B></P>
<P>The issue was discussed at length. It was generally agreed that 1) There is 
no major technical argument against the change (although there is a minor 
argument that some obscure programs may break), and 2) Such a change would not 
break const correctness. The concerns about making the change were 1) it is user 
detectable (although only in boundary cases), 2) it changes a large number of 
signatures, and 3) it seems more of a design issue that an out-and-out 
defect.</P>
<P>The LWG believes that this issue should be considered as part of a general 
review of const issues for the next revision of the standard. Also see issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#200">200</A>.</P>
<HR>
<A name=188>
<H3>188.&nbsp;valarray helpers missing augmented assignment operators</H3></A>
<P><B>Section:</B>&nbsp;26.3.2.6 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.valarray.cassign">[lib.valarray.cassign]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Gabriel Dos Reis&nbsp; <B>Date:</B>&nbsp;15 Aug 1999</P>
<P>26.3.2.6 defines augmented assignment operators valarray&lt;T&gt;::op=(const 
T&amp;), but fails to provide corresponding versions for the helper classes. 
Thus making the following illegal:</P>
<BLOCKQUOTE><PRE>#include &lt;valarray&gt;

int main()
{
std::valarray&lt;double&gt; v(3.14, 1999);

v[99] *= 2.0; // Ok

std::slice s(0, 50, 2);

v[s] *= 2.0; // ERROR
}</PRE></BLOCKQUOTE>
<P>I can't understand the intent of that omission. It makes the valarray library 
less intuitive and less useful.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Although perhaps an unfortunate design decision, the omission is not a defect 
in the current standard.&nbsp; A future standard may wish to add the missing 
operators.</P>
<HR>
<A name=190>
<H3>190.&nbsp;min() and max() functions should be std::binary_functions</H3></A>
<P><B>Section:</B>&nbsp;25.3.7 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-algorithms.html#lib.alg.min.max">[lib.alg.min.max]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Mark Rintoul&nbsp; <B>Date:</B>&nbsp;26 Aug 1999</P>
<P>Both std::min and std::max are defined as template functions. This is very 
different than the definition of std::plus (and similar structs) which are 
defined as function objects which inherit std::binary_function.<BR><BR>This lack 
of inheritance leaves std::min and std::max somewhat useless in standard library 
algorithms which require a function object that inherits 
std::binary_function.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Although perhaps an unfortunate design decision, the omission is not a defect 
in the current standard.&nbsp; A future standard may wish to consider additional 
function objects.</P>
<HR>
<A name=191>
<H3>191.&nbsp;Unclear complexity for algorithms such as binary search</H3></A>
<P><B>Section:</B>&nbsp;25.3.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-algorithms.html#lib.alg.binary.search">[lib.alg.binary.search]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nico Josuttis&nbsp; <B>Date:</B>&nbsp;10 Oct 1999</P>
<P>The complexity of binary_search() is stated as "At most log(last-first) + 2 
comparisons", which seems to say that the algorithm has logarithmic complexity. 
However, this algorithms is defined for forward iterators. And for forward 
iterators, the need to step element-by-element results into linear complexity. 
But such a statement is missing in the standard. The same applies to 
lower_bound(), upper_bound(), and equal_range().&nbsp;<BR><BR>However, strictly 
speaking the standard contains no bug here. So this might considered to be a 
clarification or improvement. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The complexity is expressed in terms of comparisons, and that complexity can 
be met even if the number of iterators accessed is linear. Paragraph 1 already 
says exactly what happens to iterators.</P>
<HR>
<A name=192>
<H3>192.&nbsp;a.insert(p,t) is inefficient and overconstrained</H3></A>
<P><B>Section:</B>&nbsp;23.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.associative.reqmts">[lib.associative.reqmts]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Ed Brey&nbsp; <B>Date:</B>&nbsp;6 Jun 1999</P>
<P>As defined in 23.1.2, paragraph 7 (table 69), a.insert(p,t) suffers from 
several problems:</P>
<TABLE cellPadding=5 border=1>
  <TBODY>
  <TR>
    <TD><B>expression</B></TD>
    <TD><B>return type</B></TD>
    <TD><B>pre/post-condition</B></TD>
    <TD><B>complexity</B></TD></TR>
  <TR>
    <TD><TT>a.insert(p,t)</TT></TD>
    <TD><TT>iterator</TT></TD>
    <TD>inserts t if and only if there is no element with key equivalent to 
      the key of t in containers with unique keys; always inserts t in 
      containers with equivalent keys. always returns the iterator pointing to 
      the element with key equivalent to the key of t . iterator p is a hint 
      pointing to where the insert should start to search.</TD>
    <TD>logarithmic in general, but amortized constant if t is inserted right 
      after p .</TD></TR></TBODY></TABLE>
<P>1. For a container with unique keys, only logarithmic complexity is 
guaranteed if no element is inserted, even though constant complexity is always 
possible if p points to an element equivalent to t.</P>
<P>2. For a container with equivalent keys, the amortized constant complexity 
guarantee is only useful if no key equivalent to t exists in the container. 
Otherwise, the insertion could occur in one of multiple locations, at least one 
of which would not be right after p.</P>
<P>3. By guaranteeing amortized constant complexity only when t is inserted 
after p, it is impossible to guarantee constant complexity if t is inserted at 
the beginning of the container. Such a problem would not exist if amortized 
constant complexity was guaranteed if t is inserted before p, since there is 
always some p immediately before which an insert can take place.</P>
<P>4. For a container with equivalent keys, p does not allow specification of 
where to insert the element, but rather only acts as a hint for improving 
performance. This negates the added functionality that p would provide if it 
specified where within a sequence of equivalent keys the insertion should occur. 
Specifying the insert location provides more control to the user, while 
providing no disadvantage to the container implementation.</P>
<P><B>Proposed resolution:</B></P>
<P>In 23.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.associative.reqmts">[lib.associative.reqmts]</A> 
paragraph 7, replace the row in table 69 for a.insert(p,t) with the following 
two rows:</P>
<TABLE cellPadding=5 border=1>
  <TBODY>
  <TR>
    <TD><B>expression</B></TD>
    <TD><B>return type</B></TD>
    <TD><B>pre/post-condition</B></TD>
    <TD><B>complexity</B></TD></TR>
  <TR>
    <TD><TT>a_uniq.insert(p,t)</TT></TD>
    <TD><TT>iterator</TT></TD>
    <TD>inserts t if and only if there is no element with key equivalent to 
      the key of t. returns the iterator pointing to the element with key 
      equivalent to the key of t.</TD>
    <TD>logarithmic in general, but amortized constant if t is inserted right 
      before p or p points to an element with key equivalent to t.</TD></TR>
  <TR>
    <TD><TT>a_eq.insert(p,t)</TT></TD>
    <TD><TT>iterator</TT></TD>
    <TD>inserts t and returns the iterator pointing to the newly inserted 
      element. t is inserted right before p if doing so preserves the container 
      ordering.</TD>
    <TD>logarithmic in general, but amortized constant if t is inserted right 
      before p.</TD></TR></TBODY></TABLE>
<P><B>Rationale:</B></P>
<P>Too big a change.&nbsp; Furthermore, implementors report checking both before 
p and after p, and don't want to change this behavior.</P>
<HR>
<A name=194>
<H3>194.&nbsp;rdbuf() functions poorly specified</H3></A>
<P><B>Section:</B>&nbsp;27.4.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.ios">[lib.ios]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Steve Clamage&nbsp; <B>Date:</B>&nbsp;7 Sep 1999</P>
<P>In classic iostreams, base class ios had an rdbuf function that returned a 
pointer to the associated streambuf. Each derived class had its own rdbuf 
function that returned a pointer of a type reflecting the actual type derived 
from streambuf. Because in ARM C++, virtual function overrides had to have the 
same return type, rdbuf could not be virtual.</P>
<P>In standard iostreams, we retain the non-virtual rdbuf function design, and 
in addition have an overloaded rdbuf function that sets the buffer pointer. 
There is no need for the second function to be virtual nor to be implemented in 
derived classes.</P>
<P>Minor question: Was there a specific reason not to make the original rdbuf 
function virtual?</P>
<P>Major problem: Friendly compilers warn about functions in derived classes 
that hide base-class overloads. Any standard implementation of iostreams will 
result in such a warning on each of the iostream classes, because of the 
ill-considered decision to overload rdbuf only in a base class.</P>
<P>In addition, users of the second rdbuf function must use explicit 
qualification or a cast to call it from derived classes. An explicit 
qualification or cast to basic_ios would prevent access to any later overriding 
version if there was one.</P>
<P>What I'd like to do in an implementation is add a using- declaration for the 
second rdbuf function in each derived class. It would eliminate warnings about 
hiding functions, and would enable access without using explicit qualification. 
Such a change I don't think would change the behavior of any valid program, but 
would allow invalid programs to compile:</P>
<BLOCKQUOTE><PRE> filebuf mybuf;
 fstream f;
 f.rdbuf(mybuf); // should be an error, no visible rdbuf</PRE></BLOCKQUOTE>
<P>I'd like to suggest this problem as a defect, with the proposed resolution to 
require the equivalent of a using-declaration for the rdbuf function that is not 
replaced in a later derived class. We could discuss whether replacing the 
function should be allowed.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>For historical reasons, the standard is correct as written. There is a subtle 
difference between the base class <TT>rdbuf()</TT> and derived class 
<TT>rdbuf()</TT>. The derived class <TT>rdbuf()</TT> always returns the original 
streambuf, whereas the base class <TT>rdbuf()</TT> will return the "current 
streambuf" if that has been changed by the variant you mention.</P>
<P>Permission is not required to add such an extension. See 17.4.4.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-intro.html#lib.member.functions">[lib.member.functions]</A>.</P>
<HR>
<A name=196>
<H3>196.&nbsp;Placement new example has alignment problems</H3></A>
<P><B>Section:</B>&nbsp;18.4.1.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-support.html#lib.new.delete.placement">[lib.new.delete.placement]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Herb Sutter&nbsp; <B>Date:</B>&nbsp;15 Dec 1998</P>
<P>The example in 18.4.1.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-support.html#lib.new.delete.placement">[lib.new.delete.placement]</A> 
paragraph 4 reads: </P>
<BLOCKQUOTE>
  <P>[Example: This can be useful for constructing an object at a known 
  address:<BR><BR><TT>&nbsp;&nbsp; char 
  place[sizeof(Something)];<BR>&nbsp;&nbsp; Something* p = new (place) 
  Something();<BR><BR></TT>end example] </P></BLOCKQUOTE>
<P>This example has potential alignment problems. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Duplicate: see issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#114">114</A>.</P>
<HR>
<A name=203>
<H3>203.&nbsp;basic_istream::sentry::sentry() is uninstantiable with 
ctype&lt;user-defined type&gt;</H3></A>
<P><B>Section:</B>&nbsp;27.6.1.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.istream::sentry">[lib.istream::sentry]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Matt McClure and Dietmar Khl&nbsp; <B>Date:</B>&nbsp;1 
Jan 2000</P>
<P>27.6.1.1.2 Paragraph 4 states:</P>
<BLOCKQUOTE>
  <P>To decide if the character c is a whitespace character, the constructor 
  performs ''as if'' it executes the following code fragment:&nbsp;</P><PRE>const ctype&lt;charT&gt;&amp; ctype = use_facet&lt;ctype&lt;charT&gt; &gt;(is.getloc());
if (ctype.is(ctype.space,c)!=0)
// c is a whitespace character.</PRE></BLOCKQUOTE>
<P>But Table 51 in 22.1.1.1.1 only requires an implementation to provide 
specializations for ctype&lt;char&gt; and ctype&lt;wchar_t&gt;. If sentry's 
constructor is implemented using ctype, it will be uninstantiable for a 
user-defined character type charT, unless the implementation has provided 
non-working (since it would be impossible to define a correct ctype&lt;charT&gt; 
specialization for an arbitrary charT) definitions of ctype's virtual member 
functions.</P>
<P>It seems the intent the standard is that sentry should behave, in every 
respect, not just during execution, as if it were implemented using ctype, with 
the burden of providing a ctype specialization falling on the user. But as it is 
written, nothing requires the translation of sentry's constructor to behave as 
if it used the above code, and it would seem therefore, that sentry's 
constructor should be instantiable for all character types. </P>
<P>Note: If I have misinterpreted the intent of the standard with respect to 
sentry's constructor's instantiability, then a note should be added to the 
following effect: </P>
<BLOCKQUOTE>An implementation is forbidden from using the above code if it 
  renders the constructor uninstantiable for an otherwise valid character type. 
</BLOCKQUOTE>
<P>In any event, some clarification is needed.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>It is possible but not easy to instantiate on types other than char or 
wchar_t; many things have to be done first. That is by intention and is not a 
defect.</P>
<HR>
<A name=204>
<H3>204.&nbsp;distance(first, last) when "last" is before "first"</H3></A>
<P><B>Section:</B>&nbsp;24.3.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.iterator.operations">[lib.iterator.operations]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Rintala Matti&nbsp; <B>Date:</B>&nbsp;28 Jan 2000</P>
<P>Section 24.3.4 describes the function distance(first, last) (where first and 
last are iterators) which calculates "the number of increments or decrements 
needed to get from 'first' to 'last'".</P>
<P>The function should work for forward, bidirectional and random access 
iterators, and there is a requirement 24.3.4.5 which states that "'last' must be 
reachable from 'first'".</P>
<P>With random access iterators the function is easy to implement as "last - 
first".</P>
<P>With forward iterators it's clear that 'first' must point to a place before 
'last', because otherwise 'last' would not be reachable from 'first'.</P>
<P>But what about bidirectional iterators? There 'last' is reachable from 
'first' with the -- operator even if 'last' points to an earlier position than 
'first'. However, I cannot see how the distance() function could be implemented 
if the implementation does not know which of the iterators points to an earlier 
position (you cannot use ++ or -- on either iterator if you don't know which 
direction is the "safe way to travel").</P>
<P>The paragraph 24.3.4.1 states that "for ... bidirectional iterators they use 
++ to provide linear time implementations". However, the ++ operator is not 
mentioned in the reachability requirement. Furthermore 24.3.4.4 explicitly 
mentions that distance() returns the number of increments _or decrements_, 
suggesting that it could return a negative number also for bidirectional 
iterators when 'last' points to a position before 'first'.</P>
<P>Is a further requirement is needed to state that for forward and 
bidirectional iterators "'last' must be reachable from 'first' using the ++ 
operator". Maybe this requirement might also apply to random access iterators so 
that distance() would work the same way for every iterator category?</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>"Reachable" is defined in the standard in 24.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.iterator.requirements">[lib.iterator.requirements]</A> 
paragraph 6. The definition is only in terms of operator++(). The LWG sees no 
defect in the standard.</P>
<HR>
<A name=205>
<H3>205.&nbsp; numeric_limits unclear on how to determine floating point 
types</H3></A>
<P><B>Section:</B>&nbsp;18.2.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-support.html#lib.numeric.limits.members">[lib.numeric.limits.members]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Steve Cleary&nbsp; <B>Date:</B>&nbsp;28 Jan 2000</P>
<P>In several places in 18.2.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-support.html#lib.numeric.limits.members">[lib.numeric.limits.members]</A>, 
a member is described as "Meaningful for all floating point types." However, no 
clear method of determining a floating point type is provided.</P>
<P>In 18.2.1.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-support.html#lib.numeric.special">[lib.numeric.special]</A>, 
paragraph 1 states ". . . (for example, epsilon() is only meaningful if 
is_integer is false). . ." which suggests that a type is a floating point type 
if is_specialized is true and is_integer is false; however, this is unclear.</P>
<P>When clarifying this, please keep in mind this need of users: what exactly is 
the definition of floating point? Would a fixed point or rational representation 
be considered one? I guess my statement here is that there could also be types 
that are neither integer or (strictly) floating point.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>It is up to the implementor of a user define type to decide if it is a 
floating point type.</P>
<HR>
<A name=206>
<H3>206.&nbsp;operator new(size_t, nothrow) may become unlinked to ordinary 
operator new if ordinary version replaced</H3></A>
<P><B>Section:</B>&nbsp;18.4.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-support.html#lib.new.delete.single">[lib.new.delete.single]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Howard Hinnant&nbsp; <B>Date:</B>&nbsp;29 Aug 1999</P>
<P>As specified, the implementation of the nothrow version of operator new does 
not necessarily call the ordinary operator new, but may instead simply call the 
same underlying allocator and return a null pointer instead of throwing an 
exception in case of failure.</P>
<P>Such an implementation breaks code that replaces the ordinary version of new, 
but not the nothrow version. If the ordinary version of new/delete is replaced, 
and if the replaced delete is not compatible with pointers returned from the 
library versions of new, then when the replaced delete receives a pointer 
allocated by the library new(nothrow), crash follows.</P>
<P>The fix appears to be that the lib version of new(nothrow) must call the 
ordinary new. Thus when the ordinary new gets replaced, the lib version will 
call the replaced ordinary new and things will continue to work.</P>
<P>An alternative would be to have the ordinary new call new(nothrow). This 
seems sub-optimal to me as the ordinary version of new is the version most 
commonly replaced in practice. So one would still need to replace both ordinary 
and nothrow versions if one wanted to replace the ordinary version.</P>
<P>Another alternative is to put in clear text that if one version is replaced, 
then the other must also be replaced to maintain compatibility. Then the 
proposed resolution below would just be a quality of implementation issue. There 
is already such text in paragraph 7 (under the new(nothrow) version). But this 
nuance is easily missed if one reads only the paragraphs relating to the 
ordinary new.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Yes, they may become unlinked, and that is by design. If a user replaces one, 
the user should also replace the other.</P>
<HR>
<A name=207>
<H3>207.&nbsp;ctype&lt;char&gt; members return clause incomplete</H3></A>
<P><B>Section:</B>&nbsp;22.2.1.3.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.facet.ctype.char.members">[lib.facet.ctype.char.members]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Robert Klarer&nbsp; <B>Date:</B>&nbsp;2 Nov 1999</P>
<P>The <TT>widen</TT> and <TT>narrow</TT> member functions are described in 
22.2.1.3.2, paragraphs 9-11. In each case we have two overloaded signatures 
followed by a <B>Returns</B> clause. The <B>Returns</B> clause only describes 
one of the overloads. </P>
<P><B>Proposed resolution:</B></P>
<P>Change the returns clause in 22.2.1.3.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.facet.ctype.char.members">[lib.facet.ctype.char.members]</A> 
paragraph 10 from:</P>
<P>&nbsp;&nbsp;&nbsp; Returns: do_widen(low, high, to).</P>
<P>to:</P>
<P>&nbsp;&nbsp;&nbsp; Returns: do_widen(c) or do_widen(low, high, to), 
respectively.</P>
<P>Change the returns clause in 22.2.1.3.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.facet.ctype.char.members">[lib.facet.ctype.char.members]</A> 
paragraph 11 from:</P>
<P>&nbsp;&nbsp;&nbsp; Returns: do_narrow(low, high, to).</P>
<P>to:</P>
<P>&nbsp;&nbsp;&nbsp; Returns: do_narrow(c) or do_narrow(low, high, to), 
respectively.</P>
<P><B>Rationale:</B></P>
<P>Subsumed by issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#153">153</A>, 
which addresses the same paragraphs.</P>
<HR>
<A name=213>
<H3>213.&nbsp;Math function overloads ambiguous</H3></A>
<P><B>Section:</B>&nbsp;26.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.c.math">[lib.c.math]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nico Josuttis&nbsp; <B>Date:</B>&nbsp;26 Feb 2000</P>
<P>Due to the additional overloaded versions of numeric functions for float and 
long double according to Section 26.5, calls such as int x; std::pow (x, 4) are 
ambiguous now in a standard conforming implementation. Current implementations 
solve this problem very different (overload for all types, don't overload for 
float and long double, use preprocessor, follow the standard and get 
ambiguities).</P>
<P>This behavior should be standardized or at least identified as implementation 
defined.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>These math issues are an understood and accepted consequence of the design. 
They have been discussed several times in the past. Users must write casts or 
write floating point expressions as arguments.</P>
<HR>
<A name=215>
<H3>215.&nbsp;Can a map's key_type be const?</H3></A>
<P><B>Section:</B>&nbsp;23.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.associative.reqmts">[lib.associative.reqmts]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Judy Ward&nbsp; <B>Date:</B>&nbsp;29 Feb 2000</P>
<P>A user noticed that this doesn't compile with the Rogue Wave library because 
the rb_tree class declares a key_allocator, and allocator&lt;const int&gt; is 
not legal, I think:</P>
<BLOCKQUOTE><PRE>map &lt; const int, ... &gt; // legal?</PRE></BLOCKQUOTE>
<P>which made me wonder whether it is legal for a map's key_type to be const. In 
email from Matt Austern he said:</P>
<BLOCKQUOTE>
  <P>I'm not sure whether it's legal to declare a map with a const key type. I 
  hadn't thought about that question until a couple weeks ago. My intuitive 
  feeling is that it ought not to be allowed, and that the standard ought to say 
  so. It does turn out to work in SGI's library, though, and someone in the 
  compiler group even used it. Perhaps this deserves to be written up as an 
  issue too.</P></BLOCKQUOTE>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The "key is assignable" requirement from table 69 in 23.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.associative.reqmts">[lib.associative.reqmts]</A> 
already implies the key cannot be const.</P>
<HR>
<A name=216>
<H3>216.&nbsp;setbase manipulator description flawed</H3></A>
<P><B>Section:</B>&nbsp;27.6.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.std.manip">[lib.std.manip]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Hyman Rosen&nbsp; <B>Date:</B>&nbsp;29 Feb 2000</P>
<P>27.6.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.std.manip">[lib.std.manip]</A> 
paragraph 5 says:</P>
<BLOCKQUOTE><PRE>smanip setbase(int base);</PRE>
  <P>Returns: An object s of unspecified type such that if out is an (instance 
  of) basic_ostream then the expression out&lt;&lt;s behaves as if f(s) were 
  called, in is an (instance of) basic_istream then the expression in&gt;&gt;s 
  behaves as if f(s) were called. Where f can be defined as:</P><PRE>ios_base&amp; f(ios_base&amp; str, int base)
{
  // set basefield
  str.setf(n == 8 ? ios_base::oct :
                n == 10 ? ios_base::dec :
                n == 16 ? ios_base::hex :
                  ios_base::fmtflags(0), ios_base::basefield);
  return str;
}</PRE></BLOCKQUOTE>
<P>There are two problems here. First, f takes two parameters, so the 
description needs to say that out&lt;&lt;s and in&gt;&gt;s behave as if 
f(s,base) had been called. Second, f is has a parameter named base, but is 
written as if the parameter was named n.</P>
<P>Actually, there's a third problem. The paragraph has grammatical errors. 
There needs to be an "and" after the first comma, and the "Where f" sentence 
fragment needs to be merged into its preceding sentence. You may also want to 
format the function a little better. The formatting above is more-or-less what 
the Standard contains.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The resolution of this defect is subsumed by the proposed resolution for 
issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#193">193</A>.</P>
<P><I>[Tokyo: The LWG agrees that this is a defect and notes that it occurs 
additional places in the section, all requiring fixes.]</I></P>
<HR>
<A name=218>
<H3>218.&nbsp;Algorithms do not use binary predicate objects for default 
comparisons</H3></A>
<P><B>Section:</B>&nbsp;25.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-algorithms.html#lib.alg.sorting">[lib.alg.sorting]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Pablo Halpern&nbsp; <B>Date:</B>&nbsp;6 Mar 2000</P>
<P>Many of the algorithms take an argument, pred, of template parameter type 
BinaryPredicate or an argument comp of template parameter type Compare. These 
algorithms usually have an overloaded version that does not take the predicate 
argument. In these cases pred is usually replaced by the use of operator== and 
comp is replaced by the use of operator&lt;.</P>
<P>This use of hard-coded operators is inconsistent with other parts of the 
library, particularly the containers library, where equality is established 
using equal_to&lt;&gt; and ordering is established using less&lt;&gt;. Worse, 
the use of operator&lt;, would cause the following innocent-looking code to have 
undefined behavior:</P>
<BLOCKQUOTE><PRE>vector&lt;string*&gt; vec;
sort(vec.begin(), vec.end());</PRE></BLOCKQUOTE>
<P>The use of operator&lt; is not defined for pointers to unrelated objects. If 
std::sort used less&lt;&gt; to compare elements, then the above code would be 
well-defined, since less&lt;&gt; is explicitly specialized to produce a total 
ordering of pointers.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>This use of operator== and operator&lt; was a very deliberate, conscious, and 
explicitly made design decision; these operators are often more efficient. The 
predicate forms are available for users who don't want to rely on operator== and 
operator&lt;.</P>
<HR>
<A name=219>
<H3>219.&nbsp;find algorithm missing version that takes a binary predicate 
argument</H3></A>
<P><B>Section:</B>&nbsp;25.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-algorithms.html#lib.alg.find">[lib.alg.find]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Pablo Halpern&nbsp; <B>Date:</B>&nbsp;6 Mar 2000</P>
<P>The find function always searches for a value using operator== to compare the 
value argument to each element in the input iterator range. This is inconsistent 
with other find-related functions such as find_end and find_first_of, which 
allow the caller to specify a binary predicate object to be used for determining 
equality. The fact that this can be accomplished using a combination of find_if 
and bind_1st or bind_2nd does not negate the desirability of a consistent, 
simple, alternative interface to find.</P>
<P><B>Proposed resolution:</B></P>
<BLOCKQUOTE>
  <P>In section 25.1.2 <A 
  href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-algorithms.html#lib.alg.find">[lib.alg.find]</A>, 
  add a second prototype for find (between the existing prototype and the 
  prototype for find_if), as follows:</P><PRE>    template&lt;class InputIterator, class T, class BinaryPredicate&gt;
      InputIterator find(InputIterator first, InputIterator last,
                         const T&amp; value, BinaryPredicate bin_pred);</PRE>
  <P>Change the description of the return from:</P>
  <BLOCKQUOTE>
    <P>Returns: The first iterator i in the range [first, last) for which the 
    following corresponding conditions hold: *i == value, pred(*i) != false. 
    Returns last if no such iterator is found.</P></BLOCKQUOTE>
  <P>&nbsp;to:</P>
  <BLOCKQUOTE>
    <P>Returns: The first iterator i in the range [first, last) for which the 
    following&nbsp; corresponding condition holds: *i == value, 
    bin_pred(*i,value) != false, pred(*) != false. Return last if no such 
    iterator is found.</P></BLOCKQUOTE></BLOCKQUOTE>
<P><B>Rationale:</B></P>
<P>This is request for a pure extension, so it is not a defect in the current 
standard.&nbsp; As the submitter pointed out, "this can be accomplished using a 
combination of find_if and bind_1st or bind_2nd".</P>
<HR>
<A name=236>
<H3>236.&nbsp;ctype&lt;char&gt;::is() member modifies facet</H3></A>
<P><B>Section:</B>&nbsp;22.2.1.3.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.facet.ctype.char.members">[lib.facet.ctype.char.members]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Dietmar Khl&nbsp; <B>Date:</B>&nbsp;24 Apr 2000</P>
<P>The description of the <TT>is()</TT> member in paragraph 4 of 22.2.1.3.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.facet.ctype.char.members">[lib.facet.ctype.char.members]</A> 
is broken: According to this description, the second form of the <TT>is()</TT> 
method modifies the masks in the <TT>ctype</TT> object. The correct semantics 
if, of course, to obtain an array of masks. The corresponding method in the 
general case, ie. the <TT>do_is()</TT> method as described in 22.2.1.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.ctype.virtuals">[lib.locale.ctype.virtuals]</A> 
paragraph 1 does the right thing.</P>
<P><B>Proposed resolution:</B></P>
<P>Change paragraph 4 from</P>
<BLOCKQUOTE>The second form, for all *p in the range [low, high), assigns 
  vec[p-low] to table()[(unsigned char)*p]. </BLOCKQUOTE>
<P>to become</P>
<BLOCKQUOTE>The second form, for all *p in the range [low, high), assigns 
  table()[(unsigned char)*p] to vec[p-low]. </BLOCKQUOTE>
<P><B>Rationale:</B></P>
<P>Duplicate. See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#28">28</A>.</P>
<HR>
<A name=244>
<H3>244.&nbsp;Must <TT>find</TT>'s third argument be CopyConstructible?</H3></A>
<P><B>Section:</B>&nbsp;25.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-algorithms.html#lib.alg.find">[lib.alg.find]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Andrew Koenig&nbsp; <B>Date:</B>&nbsp;02 May 2000</P>
<P>Is the following implementation of <TT>find</TT> acceptable?</P><PRE>        template&lt;class Iter, class X&gt;
        Iter find(Iter begin, Iter end, const X&amp; x)
        {
            X x1 = x;           // this is the crucial statement
            while (begin != end &amp;&amp; *begin != x1)
                ++begin;
            return begin;
        }
</PRE>
<P>If the answer is yes, then it is implementation-dependent as to whether the 
following fragment is well formed:</P><PRE>        vector&lt;string&gt; v;

        find(v.begin(), v.end(), "foo");
</PRE>
<P>At issue is whether there is a requirement that the third argument of find be 
CopyConstructible. There may be no problem here, but analysis is necessary.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>There is no indication in the standard that find's third argument is required 
to be Copy Constructible. The LWG believes that no such requirement was 
intended. As noted above, there are times when a user might reasonably pass an 
argument that is not Copy Constructible.</P>
<HR>
<A name=245>
<H3>245.&nbsp;Which operations on <TT>istream_iterator</TT> trigger input 
operations?</H3></A>
<P><B>Section:</B>&nbsp;24.5.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.istream.iterator">[lib.istream.iterator]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Andrew Koenig&nbsp; <B>Date:</B>&nbsp;02 May 2000</P>
<P>I do not think the standard specifies what operation(s) on istream iterators 
trigger input operations. So, for example:</P><PRE>        istream_iterator&lt;int&gt; i(cin);

        int n = *i++;
</PRE>
<P>I do not think it is specified how many integers have been read from cin. The 
number must be at least 1, of course, but can it be 2? More?</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The standard is clear as written: the stream is read every time operator++ is 
called, and it is also read either when the iterator is constructed or when 
operator* is called for the first time. In the example above, exactly two 
integers are read from cin.</P>
<P>There may be a problem with the interaction between istream_iterator and some 
STL algorithms, such as find. There are no guarantees about how many times find 
may invoke operator++.</P>
<HR>
<A name=246>
<H3>246.&nbsp;<TT>a.insert(p,t)</TT> is incorrectly specified</H3></A>
<P><B>Section:</B>&nbsp;23.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.associative.reqmts">[lib.associative.reqmts]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Mark Rodgers&nbsp; <B>Date:</B>&nbsp;19 May 2000</P>
<P>Closed issue 192 raised several problems with the specification of this 
function, but was rejected as Not A Defect because it was too big a change with 
unacceptable impacts on existing implementations. However, issues remain that 
could be addressed with a smaller change and with little or no consequent 
impact.</P>
<OL>
  <LI>
  <P>The specification is inconsistent with the original proposal and with 
  several implementations.</P>
  <P>The initial implementation by Hewlett Packard only ever looked immediately 
  <I>before</I> p, and I do not believe there was any intention to standardize 
  anything other than this behavior. Consequently, current implementations by 
  several leading implementors also look immediately before p, and will only 
  insert after p in logarithmic time. I am only aware of one implementation that 
  does actually look after p, and it looks before p as well. It is therefore 
  doubtful that existing code would be relying on the behavior defined in the 
  standard, and it would seem that fixing this defect as proposed below would 
  standardize existing practice.</P>
  <LI>
  <P>The specification is inconsistent with insertion for sequence 
  containers.</P>
  <P>This is difficult and confusing to teach to newcomers. All insert 
  operations that specify an iterator as an insertion location should have a 
  consistent meaning for the location represented by that iterator.</P>
  <LI>
  <P>As specified, there is no way to hint that the insertion should occur at 
  the beginning of the container, and the way to hint that it should occur at 
  the end is long winded and unnatural.</P>
  <P>For a container containing n elements, there are n+1 possible insertion 
  locations and n+1 valid iterators. For there to be a one-to-one mapping 
  between iterators and insertion locations, the iterator must represent an 
  insertion location immediately before the iterator.</P>
  <LI>
  <P>When appending sorted ranges using insert_iterators, insertions are 
  guaranteed to be sub-optimal.</P>
  <P>In such a situation, the optimum location for insertion is always 
  immediately after the element previously inserted. The mechanics of the insert 
  iterator guarantee that it will try and insert after the element after that, 
  which will never be correct. However, if the container first tried to insert 
  before the hint, all insertions would be performed in amortized constant 
  time.</P></LI></OL>
<P><B>Proposed resolution:</B></P>
<P>In 23.1.2 [lib.associative.reqmts] paragraph 7, table 69, make the following 
changes in the row for a.insert(p,t):</P>
<P><I>assertion/note pre/post condition:</I> <BR>Change the last sentence 
from</P>
<BLOCKQUOTE>"iterator p is a hint pointing to where the insert should start to 
  search." </BLOCKQUOTE>
<P>to</P>
<BLOCKQUOTE>"iterator p is a hint indicating that immediately before p may be 
  a correct location where the insertion could occur." </BLOCKQUOTE>
<P><I>complexity:</I><BR>Change the words "right after" to "immediately 
before".</P>
<P><B>Rationale:</B></P>
<P>Duplicate; see issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#233">233</A>.</P>
<HR>
<A name=249>
<H3>249.&nbsp;Return Type of <TT>auto_ptr::operator=</TT> </H3></A>
<P><B>Section:</B>&nbsp;20.4.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.auto.ptr">[lib.auto.ptr]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Joseph Gottman&nbsp; <B>Date:</B>&nbsp;30 Jun 2000</P>
<P>According to section 20.4.5, the function <TT>auto_ptr::operator=()</TT> 
returns a reference to an auto_ptr. The reason that <TT>operator=()</TT> usually 
returns a reference is to facilitate code like</P><PRE>    int x,y,z;
    x = y = z = 1;
</PRE>
<P>However, given analogous code for <TT>auto_ptr</TT>s,</P><PRE>    auto_ptr&lt;int&gt; x, y, z;
    z.reset(new int(1));
    x = y = z;
</PRE>
<P>the result would be that <TT>z</TT> and <TT>y</TT> would both be set to NULL, 
instead of all the <TT>auto_ptr</TT>s being set to the same value. This makes 
such cascading assignments useless and counterintuitive for 
<TT>auto_ptr</TT>s.</P>
<P><B>Proposed resolution:</B></P>
<P>Change <TT>auto_ptr::operator=()</TT> to return <TT>void</TT> instead of an 
<TT>auto_ptr</TT> reference.</P>
<P><B>Rationale:</B></P>
<P>The return value has uses other than cascaded assignments: a user can call an 
auto_ptr member function, pass the auto_ptr to a function, etc. Removing the 
return value could break working user code.</P>
<HR>
<A name=255>
<H3>255.&nbsp;Why do <TT>basic_streambuf&lt;&gt;::pbump()</TT> and 
<TT>gbump()</TT> take an int?</H3></A>
<P><B>Section:</B>&nbsp;27.5.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.streambuf">[lib.streambuf]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Martin Sebor&nbsp; <B>Date:</B>&nbsp;12 Aug 2000</P>
<P>The basic_streambuf members gbump() and pbump() are specified to take an int 
argument. This requirement prevents the functions from effectively manipulating 
buffers larger than std::numeric_limits&lt;int&gt;::max() characters. It also 
makes the common use case for these functions somewhat difficult as many 
compilers will issue a warning when an argument of type larger than int (such as 
ptrdiff_t on LLP64 architectures) is passed to either of the function. Since 
it's often the result of the subtraction of two pointers that is passed to the 
functions, a cast is necessary to silence such warnings. Finally, the usage of a 
native type in the functions signatures is inconsistent with other member 
functions (such as sgetn() and sputn()) that manipulate the underlying character 
buffer. Those functions take a streamsize argument. </P>
<P><B>Proposed resolution:</B></P>
<P>Change the signatures of these functions in the synopsis of template class 
basic_streambuf (27.5.2) and in their descriptions (27.5.2.3.1, p4 and 
27.5.2.3.2, p4) to take a streamsize argument. </P>
<P>Although this change has the potential of changing the ABI of the library, 
the change will affect only platforms where int is different than the definition 
of streamsize. However, since both functions are typically inline (they are on 
all known implementations), even on such platforms the change will not affect 
any user code unless it explicitly relies on the existing type of the functions 
(e.g., by taking their address). Such a possibility is IMO quite remote. </P>
<P>Alternate Suggestion from Howard Hinnant, c++std-lib-7780: </P>
<P>This is something of a nit, but I'm wondering if streamoff wouldn't be a 
better choice than streamsize. The argument to pbump and gbump MUST be signed. 
But the standard has this to say about streamsize (27.4.1/2/Footnote): </P>
<BLOCKQUOTE>[Footnote: streamsize is used in most places where ISO C would use 
  size_t. Most of the uses of streamsize could use size_t, except for the 
  strstreambuf constructors, which require negative values. It should probably 
  be the signed type corresponding to size_t (which is what Posix.2 calls 
  ssize_t). --- end footnote] </BLOCKQUOTE>
<P>This seems a little weak for the argument to pbump and gbump. Should we ever 
really get rid of strstream, this footnote might go with it, along with the 
reason to make streamsize signed. </P>
<P><B>Rationale:</B></P>
<P>The LWG believes this change is too big for now. We may wish to reconsider 
this for a future revision of the standard. One possibility is overloading 
pbump, rather than changing the signature.</P>
<HR>
<A name=257>
<H3>257.&nbsp;STL functional object and iterator inheritance.</H3></A>
<P><B>Section:</B>&nbsp;20.3.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.base">[lib.base]</A>, 
24.3.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.iterator.basic">[lib.iterator.basic]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Robert Dick &nbsp; <B>Date:</B>&nbsp;17 Aug 2000</P>
<P>According to the November 1997 Draft Standard, the results of deleting an 
object of a derived class through a pointer to an object of its base class are 
undefined if the base class has a non-virtual destructor. Therefore, it is 
potentially dangerous to publicly inherit from such base classes. </P>
<P>Defect: <BR>The STL design encourages users to publicly inherit from a number 
of classes which do nothing but specify interfaces, and which contain 
non-virtual destructors. </P>
<P>Attribution: <BR>Wil Evers and William E. Kempf suggested this modification 
for functional objects. </P>
<P><B>Proposed resolution:</B></P>
<P>When a base class in the standard library is useful only as an interface 
specifier, i.e., when an object of the class will never be directly 
instantiated, specify that the class contains a protected destructor. This will 
prevent deletion through a pointer to the base class without performance, or 
space penalties (on any implementation I'm aware of). </P>
<P>As an example, replace... </P><PRE>    template &lt;class Arg, class Result&gt;
    struct unary_function {
            typedef Arg    argument_type;
            typedef Result result_type;
    };
</PRE>
<P>... with... </P><PRE>    template &lt;class Arg, class Result&gt;
    struct unary_function {
            typedef Arg    argument_type;
            typedef Result result_type;
    protected:
            ~unary_function() {}
    };
</PRE>
<P>Affected definitions: <BR>&nbsp;20.3.1 [lib.function.objects] -- 
unary_function, binary_function <BR>&nbsp;24.3.2 [lib.iterator.basic] -- 
iterator </P>
<P><B>Rationale:</B></P>
<P>The standard is clear as written; this is a request for change, not a defect 
in the strict sense. The LWG had several different objections to the proposed 
change. One is that it would prevent users from creating objects of type 
<TT>unary_function</TT> and <TT>binary_function</TT>. Doing so can sometimes be 
legitimate, if users want to pass temporaries as traits or tag types in generic 
code. </P>
<HR>
<A name=267>
<H3>267.&nbsp;interaction of strstreambuf::overflow() and seekoff()</H3></A>
<P><B>Section:</B>&nbsp;D.7.1.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/future.html#depr.strstreambuf.virtuals">[depr.strstreambuf.virtuals]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Martin Sebor&nbsp; <B>Date:</B>&nbsp;5 Oct 2000</P>
<P>It appears that the interaction of the strstreambuf members overflow() and 
seekoff() can lead to undefined behavior in cases where defined behavior could 
reasonably be expected. The following program demonstrates this behavior: </P><PRE>    #include &lt;strstream&gt;

    int main ()
    {
         std::strstreambuf sb;
         sb.sputc ('c');

         sb.pubseekoff (-1, std::ios::end, std::ios::in);
         return !('c' == sb.sgetc ());
    }
</PRE>
<P>D.7.1.1, p1 initializes strstreambuf with a call to 
basic_streambuf&lt;&gt;(), which in turn sets all pointers to 0 in 27.5.2.1, p1. 
</P>
<P>27.5.2.2.5, p1 says that basic_streambuf&lt;&gt;::sputc(c) calls 
overflow(traits::to_int_type(c)) if a write position isn't available (it isn't 
due to the above). </P>
<P>D.7.1.3, p3 says that strstreambuf::overflow(off, ..., ios::in) makes at 
least one write position available (i.e., it allows the function to make any 
positive number of write positions available). </P>
<P>D.7.1.3, p13 computes newoff = seekhigh - eback(). In D.7.1, p4 we see 
seekhigh = epptr() ? epptr() : egptr(), or seekhigh = epptr() in this case. 
newoff is then epptr() - eback(). </P>
<P>D.7.1.4, p14 sets gptr() so that gptr() == eback() + newoff + off, or gptr() 
== epptr() + off holds. </P>
<P>If strstreambuf::overflow() made exactly one write position available then 
gptr() will be set to just before epptr(), and the program will return 0. Buf if 
the function made more than one write position available, epptr() and gptr() 
will both point past pptr() and the behavior of the program is undefined. </P>
<P><B>Proposed resolution:</B></P>
<P>Change the last sentence of D.7.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/future.html#depr.strstreambuf">[depr.strstreambuf]</A> 
paragraph 4 from</P>
<BLOCKQUOTE>Otherwise, seeklow equals gbeg and seekhigh is either pend, if 
  pend is not a null pointer, or gend. </BLOCKQUOTE>
<P>to become</P>
<BLOCKQUOTE>Otherwise, seeklow equals gbeg and seekhigh is either gend if 0 == 
  pptr(), or pbase() + max where max is the maximum value of pptr() - pbase() 
  ever reached for this stream. </BLOCKQUOTE>
<P><I>[ pre-Copenhagen: Dietmar provided wording for proposed resolution. 
]</I></P>
<P><I>[ post-Copenhagen: Fixed a typo: proposed resolution said to fix 4.7.1, 
not D.7.1. ]</I></P>
<P><B>Rationale:</B></P>
<P>This is related to issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#65">65</A>: 
it's not clear what it means to seek beyond the current area. Without resolving 
issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#65">65</A> 
we can't resolve this. As with issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#65">65</A>, 
the library working group does not wish to invest time nailing down corner cases 
in a deprecated feature.</P>
<HR>
<A name=269>
<H3>269.&nbsp;cstdarg and unnamed parameters</H3></A>
<P><B>Section:</B>&nbsp;18.7 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-support.html#lib.support.runtime">[lib.support.runtime]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;J. Stephen Adamczyk&nbsp; <B>Date:</B>&nbsp;10 Oct 
2000</P>
<P>One of our customers asks whether this is valid C++: </P><PRE>   #include &lt;cstdarg&gt;

   void bar(const char *, va_list);

   void
   foo(const char *file, const char *, ...)
   {
     va_list ap;
     va_start(ap, file);
     bar(file, ap);
     va_end(ap);
   }
</PRE>
<P>The issue being whether it is valid to use cstdarg when the final parameter 
before the "..." is unnamed. cstdarg is, as far as I can tell, inherited 
verbatim from the C standard. and the definition there (7.8.1.1 in the ISO C89 
standard) refers to "the identifier of the rightmost parameter". What happens 
when there is no such identifier? </P>
<P>My personal opinion is that this should be allowed, but some tweak might be 
required in the C++ standard. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Not a defect, the C and C++ standards are clear. It is impossible to use 
varargs if the parameter immediately before "..." has no name, because that is 
the parameter that must be passed to va_start. The example given above is 
broken, because va_start is being passed the wrong parameter. </P>
<P>There is no support for extending varargs to provide additional functionality 
beyond what's currently there. For reasons of C/C++ compatibility, it is 
especially important not to make gratuitous changes in this part of the C++ 
standard. The C committee has already been requested not to touch this part of 
the C standard unless necessary. </P>
<HR>
<A name=277>
<H3>277.&nbsp;Normative encouragement in allocator requirements unclear</H3></A>
<P><B>Section:</B>&nbsp;20.1.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.allocator.requirements">[lib.allocator.requirements]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Matt Austern&nbsp; <B>Date:</B>&nbsp;07 Nov 2000</P>
<P>In 20.1.5, paragraph 5, the standard says that "Implementors are encouraged 
to supply libraries that can accept allocators that encapsulate more general 
memory models and that support non-equal instances." This is intended as 
normative encouragement to standard library implementors. However, it is 
possible to interpret this sentence as applying to nonstandard third-party 
libraries. </P>
<P><B>Proposed resolution:</B></P>
<P>In 20.1.5, paragraph 5, change "Implementors" to "Implementors of the library 
described in this International Standard". </P>
<P><B>Rationale:</B></P>
<P>The LWG believes the normative encouragement is already sufficiently clear, 
and that there are no important consequences even if it is misunderstood.</P>
<HR>
<A name=279>
<H3>279.&nbsp;const and non-const iterators should have equivalent 
typedefs</H3></A>
<P><B>Section:</B>&nbsp;23.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.container.requirements">[lib.container.requirements]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Steve Cleary&nbsp; <B>Date:</B>&nbsp;27 Nov 2000</P>
<P>This came from an email from Steve Cleary to Fergus in reference to issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#179">179</A>. 
The library working group briefly discussed this in Toronto and believes it 
should be a separate issue. </P>
<P>Steve said: "We may want to state that the const/non-const iterators must 
have the same difference type, size_type, and category." </P>
<P>(Comment from Judy) I'm not sure if the above sentence should be true for all 
const and non-const iterators in a particular container, or if it means the 
container's iterator can't be compared with the container's const_iterator 
unless the above it true. I suspect the former. </P>
<P><B>Proposed resolution:</B></P>
<P>In <B>Section:</B> 23.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.container.requirements">[lib.container.requirements]</A>, 
table 65, in the assertion/note pre/post condition for X::const_iterator, add 
the following: </P>
<BLOCKQUOTE>
  <P>typeid(X::const_iterator::difference_type) == 
  typeid(X::iterator::difference_type) </P>
  <P>typeid(X::const_iterator::size_type) == typeid(X::iterator::size_type) </P>
  <P>typeid(X::const_iterator::category) == typeid(X::iterator::category) 
</P></BLOCKQUOTE>
<P><B>Rationale:</B></P>
<P>Going through the types one by one: Iterators don't have a 
<TT>size_type</TT>. We already know that the difference types are identical, 
because the container requirements already say that the difference types of both 
X::iterator and X::const_iterator are both X::difference_type. The standard does 
not require that X::iterator and X::const_iterator have the same iterator 
category, but the LWG does not see this as a defect: it's possible to imagine 
cases in which it would be useful for the categories to be different.</P>
<P>It may be desirable to require X::iterator and X::const_iterator to have the 
same value type, but that is a new issue. (Issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#322">322</A>.)</P>
<HR>
<A name=287>
<H3>287.&nbsp;conflicting ios_base fmtflags</H3></A>
<P><B>Section:</B>&nbsp;27.4.2.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.fmtflags.state">[lib.fmtflags.state]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Judy Ward&nbsp; <B>Date:</B>&nbsp;30 Dec 2000</P>
<P>The Effects clause for ios_base::setf(fmtflags fmtfl) says "Sets fmtfl in 
flags()". What happens if the user first calls ios_base::scientific and then 
calls ios_base::fixed or vice-versa? This is an issue for all of the conflicting 
flags, i.e. ios_base::left and ios_base::right or ios_base::dec, ios_base::hex 
and ios_base::oct. </P>
<P>I see three possible solutions: </P>
<OL>
  <LI>Set ios_base::failbit whenever the user specifies a conflicting flag with 
  one previously explicitly set. If the constructor is supposed to set 
  ios_base::dec (see discussion below), then the user setting hex or oct format 
  after construction will not set failbit. 
  <LI>The last call to setf "wins", i.e. it clears any conflicting previous 
  setting. 
  <LI>All the flags that the user specifies are set, but when actually 
  interpreting them, fixed always override scientific, right always overrides 
  left, dec overrides hex which overrides oct. </LI></OL>
<P>Most existing implementations that I tried seem to conform to resolution #3, 
except that when using the iomanip manipulator hex or oct then that always 
overrides dec, but calling setf(ios_base::hex) doesn't. </P>
<P>There is a sort of related issue, which is that although the ios_base 
constructor says that each ios_base member has an indeterminate value after 
construction, all the existing implementations I tried explicitly set 
ios_base::dec. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P><TT>adjustfield</TT>, <TT>basefield</TT>, and <TT>floatfield</TT> are each 
multi-bit fields. It is possible to set multiple bits within each of those 
fields. (For example, <TT>dec</TT> and <TT>oct</TT>). These fields are used by 
locale facets. The LWG reviewed the way in which each of those three fields is 
used, and believes that in each case the behavior is well defined for any 
possible combination of bits. See for example Table 58, in 22.2.2.2.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.facet.num.put.virtuals">[lib.facet.num.put.virtuals]</A>, 
noting the requirement in paragraph 6 of that section. </P>
<P>Users are advised to use manipulators, or else use the two-argument version 
of <TT>setf</TT>, to avoid unexpected behavior. </P>
<HR>
<A name=289>
<H3>289.&nbsp;&lt;cmath&gt; requirements missing C float and long double 
versions</H3></A>
<P><B>Section:</B>&nbsp;26.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.c.math">[lib.c.math]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Judy Ward&nbsp; <B>Date:</B>&nbsp;30 Dec 2000</P>
<P>In ISO/IEC 9899:1990 Programming Languages C we find the following concerning 
&lt;math.h&gt;: </P>
<BLOCKQUOTE>7.13.4 Mathematics &lt;math.h&gt; <BR>The names of all existing 
  functions declared in the &lt;math.h&gt; header, suffixed with f or l, are 
  reserved respectively for corresponding functions with float and long double 
  arguments are return values. </BLOCKQUOTE>
<P>For example, <TT>float&nbsp;sinf(float)</TT> is reserved. </P>
<P>In the C99 standard, &lt;math.h&gt; must contain declarations for these 
functions. </P>
<P>So, is it acceptable for an implementor to add these prototypes to the C++ 
versions of the math headers? Are they required? </P>
<P><B>Proposed resolution:</B></P>
<P>Add these Functions to Table 80, section 26.5 and to Table 99, section C.2: 
</P><PRE>    acosf asinf atanf atan2f ceilf cosf coshf 
    expf fabsf floorf fmodf frexpf ldexpf 
    logf log10f modff powf sinf sinhf sqrtf 
    tanf tanhf 
    acosl asinl atanl atan2l ceill cosl coshl 
    expl fabsl floorl fmodl frexpl ldexpl 
    logl log10l modfl powl sinl sinhl sqrtl 
    tanl tanhl
</PRE>
<P>There should probably be a note saying that these functions are optional and, 
if supplied, should match the description in the 1999 version of the C standard. 
In the next round of C++ standardization they can then become mandatory. </P>
<P><B>Rationale:</B></P>
<P>The C90 standard, as amended, already permits (but does not require) these 
functions, and the C++ standard incorporates the C90 standard by reference. C99 
is not an issue, because it is never referred to by the C++ standard.</P>
<HR>
<A name=293>
<H3>293.&nbsp;Order of execution in transform algorithm</H3></A>
<P><B>Section:</B>&nbsp;25.2.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-algorithms.html#lib.alg.transform">[lib.alg.transform]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Angelika Langer&nbsp; <B>Date:</B>&nbsp;04 Jan 2001</P>
<P>This issue is related to issue 242. In case that the resolution proposed for 
issue 242 is accepted, we have have the following situation: The 4 numeric 
algorithms (accumulate and consorts) as well as transform would allow a certain 
category of side effects. The numeric algorithms specify that they invoke the 
functor "for every iterator i in the range [first, last) in order". transform, 
in contrast, would not give any guarantee regarding order of invocation of the 
functor, which means that the functor can be invoked in any arbitrary order. 
</P>
<P>Why would that be a problem? Consider an example: say the transformator that 
is a simple enumerator ( or more generally speaking, "is order-sensitive" ). 
Since a standard compliant implementation of transform is free to invoke the 
enumerator in no definite order, the result could be a garbled enumeration. 
Strictly speaking this is not a problem, but it is certainly at odds with the 
prevalent understanding of transform as an algorithms that assigns "a new 
_corresponding_ value" to the output elements. </P>
<P>All implementations that I know of invoke the transformator in definite 
order, namely starting from first and proceeding to last - 1. Unless there is an 
optimization conceivable that takes advantage of the indefinite order I would 
suggest to specify the order, because it eliminate the uncertainty that users 
would otherwise have regarding the order of execution of their potentially 
order-sensitive function objects. </P>
<P><B>Proposed resolution:</B></P>
<P>In section 25.2.3 - Transform [lib.alg.transform] change:</P>
<BLOCKQUOTE>-1- Effects: Assigns through every iterator i in the range 
  [result, result + (last1 - first1)) a new corresponding value equal to 
  op(*(first1 + (i - result)) or binary_op(*(first1 + (i - result), *(first2 + 
  (i - result))). </BLOCKQUOTE>
<P>to:</P>
<BLOCKQUOTE>-1- Effects: Computes values by invoking the operation op or 
  binary_op for every iterator in the range [first1, last1) in order. Assigns 
  through every iterator i in the range [result, result + (last1 - first1)) a 
  new corresponding value equal to op(*(first1 + (i - result)) or 
  binary_op(*(first1 + (i - result), *(first2 + (i - result))). </BLOCKQUOTE>
<P><B>Rationale:</B></P>
<P>For Input Iterators an order is already guaranteed, because only one order is 
possible. If a user who passes a Forward Iterator to one of these algorithms 
really needs a specific order of execution, it's possible to achieve that effect 
by wrapping it in an Input Iterator adaptor.</P>
<HR>
<A name=296>
<H3>296.&nbsp;Missing descriptions and requirements of pair operators</H3></A>
<P><B>Section:</B>&nbsp;20.2.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.pairs">[lib.pairs]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Martin Sebor&nbsp; <B>Date:</B>&nbsp;14 Jan 2001</P>
<P>The synopsis of the header <TT>&lt;utility&gt;</TT> in 20.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.utility">[lib.utility]</A> 
lists the complete set of equality and relational operators for <TT>pair</TT> 
but the section describing the template and the operators only describes 
<TT>operator==()</TT> and <TT>operator&lt;()</TT>, and it fails to mention any 
requirements on the template arguments. The remaining operators are not 
mentioned at all. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>20.2.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.operators">[lib.operators]</A> 
paragraph 10 already specifies the semantics. That paragraph says that, if 
declarations of operator!=, operator&gt;, operator&lt;=, and operator&gt;= 
appear without definitions, they are defined as specified in 20.2.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.operators">[lib.operators]</A>. 
There should be no user confusion, since that paragraph happens to immediately 
precede the specification of <TT>pair</TT>.</P>
<HR>
<A name=302>
<H3>302.&nbsp;Need error indication from codecvt&lt;&gt;::do_length</H3></A>
<P><B>Section:</B>&nbsp;22.2.1.5.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.codecvt.virtuals">[lib.locale.codecvt.virtuals]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Gregory Bumgardner&nbsp; <B>Date:</B>&nbsp;25 Jan 
2001</P>
<P>The effects of <TT>codecvt&lt;&gt;::do_length()</TT> are described in 
22.2.1.5.2, paragraph 10. As implied by that paragraph, and clarified in issue 
<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#75">75</A>, 
<TT>codecvt&lt;&gt;::do_length()</TT> must process the source data and update 
the <TT>stateT</TT> argument just as if the data had been processed by 
<TT>codecvt&lt;&gt;::in()</TT>. However, the standard does not specify how 
<TT>do_length()</TT> would report a translation failure, should the source 
sequence contain untranslatable or illegal character sequences. </P>
<P>The other conversion methods return an "error" result value to indicate that 
an untranslatable character has been encountered, but <TT>do_length()</TT> 
already has a return value (the number of source characters that have been 
processed by the method). </P>
<P><B>Proposed resolution:</B></P>
<P>This issue cannot be resolved without modifying the interface. An exception 
cannot be used, as there would be no way to determine how many characters have 
been processed and the state object would be left in an indeterminate state. 
</P>
<P>A source compatible solution involves adding a fifth argument to length() and 
do_length() that could be used to return position of the offending character 
sequence. This argument would have a default value that would allow it to be 
ignored: </P><PRE>  int length(stateT&amp; state, 
             const externT* from, 
             const externT* from_end, 
             size_t max,
             const externT** from_next = 0);

  virtual
  int do_length(stateT&amp; state, 
                const externT* from, 
                const externT* from_end, 
                size_t max,
                const externT** from_next);
</PRE>
<P>Then an exception could be used to report any translation errors and the 
from_next argument, if used, could then be used to retrieve the location of the 
offending character sequence. </P>
<P><B>Rationale:</B></P>
<P>The standard is already clear: the return value is the number of "valid 
complete characters". If it encounters an invalid sequence of external 
characters, it stops.</P>
<HR>
<A name=304>
<H3>304.&nbsp;Must <TT>*a</TT> return an lvalue when <TT>a</TT> is an input 
iterator?</H3></A>
<P><B>Section:</B>&nbsp;24.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.iterator.requirements">[lib.iterator.requirements]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Dave Abrahams&nbsp; <B>Date:</B>&nbsp;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>
<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). </P>
<P>The problem occurs in the following entry:</P><PRE>  a-&gt;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-&gt;()</TT> must return a pointer for <TT>a-&gt;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. </P>
<P>I don't think this was intentional.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The current standard is clear and consistent. Input iterators that return 
rvalues are in fact implementable. They may in some cases require extra work, 
but it is still possible to define an operator-&gt; in such cases: it doesn't 
have to return a T*, but may return a proxy type. No change to the standard is 
justified.</P>
<HR>
<A name=313>
<H3>313.&nbsp;set_terminate and set_unexpected question</H3></A>
<P><B>Section:</B>&nbsp;18.6.3.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-support.html#lib.terminate">[lib.terminate]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Judy Ward&nbsp; <B>Date:</B>&nbsp;3 Apr 2001</P>
<P>According to section 18.6.3.3 of the standard, std::terminate() is supposed 
to call the terminate_handler in effect immediately after evaluating the throw 
expression. </P>
<P>Question: what if the terminate_handler in effect is itself std::terminate? 
</P>
<P>For example:</P><PRE>  #include &lt;exception&gt;

  int main () {
      std::set_terminate(std::terminate);
      throw 5;
      return 0;
  }
</PRE>
<P>Is the implementation allowed to go into an infinite loop? </P>
<P>I think the same issue applies to std::set_unexpected. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Infinite recursion is to be expected: users who set the terminate handler to 
<TT>terminate</TT> are explicitly asking for <TT>terminate</TT> to call 
itself.</P>
<HR>
<A name=314>
<H3>314.&nbsp;Is the stack unwound when terminate() is called?</H3></A>
<P><B>Section:</B>&nbsp;18.6.3.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-support.html#lib.terminate">[lib.terminate]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Detlef Vollmann&nbsp; <B>Date:</B>&nbsp;11 Apr 2001</P>
<P>The standard appears to contradict itself about whether the stack is unwound 
when the implementation calls terminate(). </P>
<P>From 18.6.3.3p2:</P>
<BLOCKQUOTE>Calls the terminate_handler function in effect immediately after 
  evaluating the throw-expression (lib.terminate.handler), if called by the 
  implementation [...] </BLOCKQUOTE>
<P>So the stack is guaranteed not to be unwound.</P>
<P>But from 15.3p9:</P>
<BLOCKQUOTE>[...]whether or not the stack is unwound before this call to 
  terminate() is implementation-defined (except.terminate). </BLOCKQUOTE>
<P>And 15.5.1 actually defines that in most cases the stack is unwound. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>There is definitely no contradiction between the core and library clauses; 
nothing in the core clauses says that stack unwinding happens after 
<TT>terminate</TT> is called. 18.6.3.3p2 does not say anything about when 
terminate() is called; it merely specifies which <TT>terminate_handler</TT> is 
used.</P>
<HR>
<A name=323>
<H3>323.&nbsp;abs() overloads in different headers</H3></A>
<P><B>Section:</B>&nbsp;26.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.c.math">[lib.c.math]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Dave Abrahams&nbsp; <B>Date:</B>&nbsp;4 June 2001</P>
<P>Currently the standard mandates the following overloads of abs():</P><PRE>    abs(long), abs(int) in &lt;cstdlib&gt;

    abs(float), abs(double), abs(long double) in &lt;cmath&gt;

    template&lt;class T&gt; T abs(const complex&lt;T&gt;&amp;) in &lt;complex&gt;

    template&lt;class T&gt; valarray&lt;T&gt; abs(const valarray&lt;T&gt;&amp;); in &lt;valarray&gt;
</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. </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: complex, and 
int_max_abs.</P>
<P>Related issue: <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#343">343</A>.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The programs that could potentially be broken by this situation are already 
fragile, and somewhat contrived: For example, a user-defined class that has 
conversion overloads both to <TT>long</TT> and to <TT>float</TT>. If <TT>x</TT> 
is a value of such a class, then <TT>abs(x)</TT> would give the <TT>long</TT> 
version if the user included &lt;cstdlib&gt;, the <TT>float</TT> version if the 
user included &lt;cmath&gt;, and would be diagnosed as ambiguous at compile time 
if the user included both headers. The LWG couldn't find an example of a program 
whose meaning would be changed (as opposed to changing it from well-formed to 
ill-formed) simply by adding another standard header.</P>
<P>Since the harm seems minimal, and there don't seem to be any simple and 
noninvasive solutions, this is being closed as NAD. It is marked as "Future" for 
two reasons. First, it might be useful to define an <TT>&lt;all&gt;</TT> header 
that would include all Standard Library headers. Second, we should at least make 
sure that future library extensions don't make this problem worse.</P>
<HR>
<A name=326>
<H3>326.&nbsp;Missing typedef in moneypunct_byname</H3></A>
<P><B>Section:</B>&nbsp;22.2.6.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.moneypunct.byname">[lib.locale.moneypunct.byname]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Martin Sebor&nbsp; <B>Date:</B>&nbsp;05 Jul 2001</P>
<P>The definition of the moneypunct facet contains the typedefs char_type and 
string_type. Only one of these names, string_type, is defined in the derived 
facet, moneypunct_byname.</P>
<P><B>Proposed resolution:</B></P>
<P>For consistency with the numpunct facet, add a typedef for char_type to the 
definition of the moneypunct_byname facet in 22.2.6.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.moneypunct.byname">[lib.locale.moneypunct.byname]</A>.</P>
<P><B>Rationale:</B></P>
<P>The absence of the typedef is irrelevant. Users can still access the typedef, 
because it is inherited from the base class.</P>
<HR>
<A name=330>
<H3>330.&nbsp;Misleading "exposition only" value in class locale 
definition</H3></A>
<P><B>Section:</B>&nbsp;22.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale">[lib.locale]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Martin Sebor&nbsp; <B>Date:</B>&nbsp;15 Jul 2001</P>
<P>The "exposition only" value of the std::locale::none constant shown in the 
definition of class locale is misleading in that it on many systems conflicts 
with the value assigned to one if the LC_XXX constants (specifically, LC_COLLATE 
on AIX, LC_ALL on HP-UX, LC_CTYPE on Linux and SunOS). This causes incorrect 
behavior when such a constant is passed to one of the locale member functions 
that accept a locale::category argument and interpret it as either the C LC_XXX 
constant or a bitmap of locale::category values. At least three major 
implementations adopt the suggested value without a change and consequently 
suffer from this problem. </P>
<P>For instance, the following code will (presumably) incorrectly copy facets 
belonging to the collate category from the German locale on AIX: </P><PRE>  std::locale l (std::locale ("C"), "de_DE", std::locale::none);
</PRE>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The LWG agrees that it may be difficult to implement locale member functions 
in such a way that they can take either <TT>category</TT> arguments or the LC_ 
constants defined in &lt;cctype&gt;. In light of this requirement (22.1.1.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.category">[lib.locale.category]</A>, 
paragraph 2), and in light of the requirement in the preceding paragraph that it 
is possible to combine <TT>category</TT> bitmask elements with bitwise 
operations, defining the <TT>category</TT> elements is delicate, particularly if 
an implementor is constrained to work with a preexisting C library. (Just using 
the existing LC_ constants would not work in general.) There's no set of 
"exposition only" values that could give library implementors proper guidance in 
such a delicate matter. The non-normative example we're giving is no worse than 
any other choice would be.</P>
<P>See issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#347">347</A>.</P>
<HR>
<A name=332>
<H3>332.&nbsp;Consider adding increment and decrement operators to std::fpos&lt; 
T &gt; </H3></A>
<P><B>Section:</B>&nbsp;27.4.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.fpos">[lib.fpos]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;PremAnand M. Rao&nbsp; <B>Date:</B>&nbsp;27 Aug 2001</P>
<P>Increment and decrement operators are missing from Table 88 -- Position type 
requirements in 27.4.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.fpos">[lib.fpos]</A>. 
</P>
<P><B>Proposed resolution:</B></P>
<P>Table 88 (section 27.4.3) -- Position type requirements be updated to include 
increment and decrement operators. </P><PRE>expression        return type     operational    note

++p               fpos&amp;           p += O(1)
p++               fpos            { P tmp = p;
                                    ++p;
                                    return tmp; }
--p               fpos&amp;           p -= O(1)
p--               fpos            { P tmp = p;
                                    --p;
                                    return tmp; }
</PRE>
<P><B>Rationale:</B></P>
<P>The LWG believes this is a request for extension, not a defect report. 
Additionally, nobody saw a clear need for this extension; <TT>fpos</TT> is used 
only in very limited ways.</P>
<HR>
<A name=343>
<H3>343.&nbsp;Unspecified library header dependencies</H3></A>
<P><B>Section:</B>&nbsp;21 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.strings">[lib.strings]</A>, 
23 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.containers">[lib.containers]</A>, 
27 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.input.output">[lib.input.output]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Martin Sebor&nbsp; <B>Date:</B>&nbsp;09 Oct 2001</P>
<P>The synopses of the C++ library headers clearly show which names are required 
to be defined in each header. Since in order to implement the classes and 
templates defined in these headers declarations of other templates (but not 
necessarily their definitions) are typically necessary the standard in 17.4.4, 
p1 permits library implementers to include any headers needed to implement the 
definitions in each header. </P>
<P>For instance, although it is not explicitly specified in the synopsis of 
&lt;string&gt;, at the point of definition of the std::basic_string template the 
declaration of the std::allocator template must be in scope. All current 
implementations simply include &lt;memory&gt; from within &lt;string&gt;, either 
directly or indirectly, to bring the declaration of std::allocator into scope. 
</P>
<P>Additionally, however, some implementation also include &lt;istream&gt; and 
&lt;ostream&gt; at the top of &lt;string&gt; to bring the declarations of 
std::basic_istream and std::basic_ostream into scope (which are needed in order 
to implement the string inserter and extractor operators (21.3.7.9 
[lib.string.io])). Other implementations only include &lt;iosfwd&gt;, since 
strictly speaking, only the declarations and not the full definitions are 
necessary. </P>
<P>Obviously, it is possible to implement &lt;string&gt; without actually 
providing the full definitions of all the templates std::basic_string uses 
(std::allocator, std::basic_istream, and std::basic_ostream). Furthermore, not 
only is it possible, doing so is likely to have a positive effect on 
compile-time efficiency. </P>
<P>But while it may seem perfectly reasonable to expect a program that uses the 
std::basic_string insertion and extraction operators to also explicitly include 
&lt;istream&gt; or &lt;ostream&gt;, respectively, it doesn't seem reasonable to 
also expect it to explicitly include &lt;memory&gt;. Since what's reasonable and 
what isn't is highly subjective one would expect the standard to specify what 
can and what cannot be assumed. Unfortunately, that isn't the case. </P>
<P>The examples below demonstrate the issue.</P>
<P>Example 1:</P>
<P>It is not clear whether the following program is complete:</P><PRE>#include &lt;string&gt;

extern std::basic_ostream&lt;char&gt; &amp;strm;

int main () {
    strm &lt;&lt; std::string ("Hello, World!\n");
}
</PRE>
<P>or whether one must explicitly include &lt;memory&gt; or &lt;ostream&gt; (or 
both) in addition to &lt;string&gt; in order for the program to compile.</P>
<P>Example 2:</P>
<P>Similarly, it is unclear whether the following program is complete:</P><PRE>#include &lt;istream&gt;

extern std::basic_iostream&lt;char&gt; &amp;strm;

int main () {
    strm &lt;&lt; "Hello, World!\n";
}
</PRE>
<P>or whether one needs to explicitly include &lt;ostream&gt;, and perhaps even 
other headers containing the definitions of other required templates:</P><PRE>#include &lt;ios&gt;
#include &lt;istream&gt;
#include &lt;ostream&gt;
#include &lt;streambuf&gt;

extern std::basic_iostream&lt;char&gt; &amp;strm;

int main () {
    strm &lt;&lt; "Hello, World!\n";
}
</PRE>
<P>Example 3:</P>
<P>Likewise, it seems unclear whether the program below is complete:</P><PRE>#include &lt;iterator&gt;

bool foo (std::istream_iterator&lt;int&gt; a, std::istream_iterator&lt;int&gt; b)
{
    return a == b;
}

int main () { }
</PRE>
<P>or whether one should be required to include &lt;istream&gt;.</P>
<P>There are many more examples that demonstrate this lack of a requirement. I 
believe that in a good number of cases it would be unreasonable to require that 
a program explicitly include all the headers necessary for a particular template 
to be specialized, but I think that there are cases such as some of those above 
where it would be desirable to allow implementations to include only as much as 
necessary and not more.</P>
<P><B>Proposed resolution:</B></P>
<P>For every C++ library header, supply a minimum set of other C++ library 
headers that are required to be included by that header. The proposed list is 
below (C++ headers for C Library Facilities, table 12 in 17.4.1.2, p3, are 
omitted): </P><PRE>+------------+--------------------+
| C++ header |required to include |
+============+====================+
|&lt;algorithm&gt; |                    |
+------------+--------------------+
|&lt;bitset&gt;    |                    |
+------------+--------------------+
|&lt;complex&gt;   |                    |
+------------+--------------------+
|&lt;deque&gt;     |&lt;memory&gt;            |
+------------+--------------------+
|&lt;exception&gt; |                    |
+------------+--------------------+
|&lt;fstream&gt;   |&lt;ios&gt;               |
+------------+--------------------+
|&lt;functional&gt;|                    |
+------------+--------------------+
|&lt;iomanip&gt;   |&lt;ios&gt;               |
+------------+--------------------+
|&lt;ios&gt;       |&lt;streambuf&gt;         |
+------------+--------------------+
|&lt;iosfwd&gt;    |                    |
+------------+--------------------+
|&lt;iostream&gt;  |&lt;istream&gt;, &lt;ostream&gt;|
+------------+--------------------+
|&lt;istream&gt;   |&lt;ios&gt;               |
+------------+--------------------+
|&lt;iterator&gt;  |                    |
+------------+--------------------+
|&lt;limits&gt;    |                    |
+------------+--------------------+
|&lt;list&gt;      |&lt;memory&gt;            |
+------------+--------------------+
|&lt;locale&gt;    |                    |
+------------+--------------------+
|&lt;map&gt;       |&lt;memory&gt;            |
+------------+--------------------+
|&lt;memory&gt;    |                    |
+------------+--------------------+
|&lt;new&gt;       |&lt;exception&gt;         |
+------------+--------------------+
|&lt;numeric&gt;   |                    |
+------------+--------------------+
|&lt;ostream&gt;   |&lt;ios&gt;               |
+------------+--------------------+
|&lt;queue&gt;     |&lt;deque&gt;             |
+------------+--------------------+
|&lt;set&gt;       |&lt;memory&gt;            |
+------------+--------------------+
|&lt;sstream&gt;   |&lt;ios&gt;, &lt;string&gt;     |
+------------+--------------------+
|&lt;stack&gt;     |&lt;deque&gt;             |
+------------+--------------------+
|&lt;stdexcept&gt; |                    |
+------------+--------------------+
|&lt;streambuf&gt; |&lt;ios&gt;               |
+------------+--------------------+
|&lt;string&gt;    |&lt;memory&gt;            |
+------------+--------------------+
|&lt;strstream&gt; |                    |
+------------+--------------------+
|&lt;typeinfo&gt;  |&lt;exception&gt;         |
+------------+--------------------+
|&lt;utility&gt;   |                    |
+------------+--------------------+
|&lt;valarray&gt;  |                    |
+------------+--------------------+
|&lt;vector&gt;    |&lt;memory&gt;            |
+------------+--------------------+
</PRE>
<P><B>Rationale:</B></P>
<P>The portability problem is real. A program that works correctly on one 
implementation might fail on another, because of different header dependencies. 
This problem was understood before the standard was completed, and it was a 
conscious design choice.</P>
<P>One possible way to deal with this, as a library extension, would be an 
&lt;all&gt; header.</P>
<HR>
<A name=344>
<H3>344.&nbsp;grouping + showbase</H3></A>
<P><B>Section:</B>&nbsp;22.2.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.category.numeric">[lib.category.numeric]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Howard Hinnant&nbsp; <B>Date:</B>&nbsp;13 Oct 2001</P>
<P>When both grouping and showbase are active and the basefield is octal, does 
the leading 0 participate in the grouping or not? For example, should one format 
as: 0,123,456 or 0123,456? </P>
<P>An analogy can be drawn with hexadecimal. It appears that 0x123,456 is 
preferred over 0x,123,456. However, this analogy is not universally accepted to 
apply to the octal base. The standard is not clear on how to format (or parse) 
in this manner. </P>
<P><B>Proposed resolution:</B></P>
<P>Insert into 22.2.3.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.facet.numpunct.virtuals">[lib.facet.numpunct.virtuals]</A> 
paragraph 3, just before the last sentence: </P>
<BLOCKQUOTE>The leading hexadecimal base specifier "0x" does not participate 
  in grouping. The leading '0' octal base specifier may participate in grouping. 
  It is unspecified if the leading '0' participates in formatting octal numbers. 
  In parsing octal numbers, the implementation is encouraged to accept both the 
  leading '0' participating in the grouping, and not participating (e.g. 
  0123,456 or 0,123,456). </BLOCKQUOTE>
<P><B>Rationale:</B></P>
<P>The current behavior may be unspecified, but it's not clear that it matters. 
This is an obscure corner case, since grouping is usually intended for the 
benefit of humans and oct/hex prefixes are usually intended for the benefit of 
machines. There is not a strong enough consensus in the LWG for action. </P>
<HR>
<A name=348>
<H3>348.&nbsp;Minor issue with std::pair operator&lt;</H3></A>
<P><B>Section:</B>&nbsp;20.2.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.pairs">[lib.pairs]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Andy Sawyer&nbsp; <B>Date:</B>&nbsp;23 Oct 2001</P>
<P>The current wording of 20.2.2 [lib.pairs] p6 precludes the use of 
operator&lt; on any pair type which contains a pointer. </P>
<P><B>Proposed resolution:</B></P>
<P>In 20.2.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.pairs">[lib.pairs]</A> 
paragraph 6, replace:</P><PRE>    Returns: x.first &lt; y.first || (!(y.first &lt; x.first) &amp;&amp; x.second &lt;
        y.second).
</PRE>
<P>With:</P><PRE>    Returns: std::less&lt;T1&gt;()( x.first, y.first ) ||
             (!std::less&lt;T1&gt;()( y.first, x.first) &amp;&amp; 
             std::less&lt;T2&gt;()( x.second, y.second ) )
</PRE>
<P><B>Rationale:</B></P>
<P>This is an instance of a much more general problem. If we want operator&lt; 
to translate to std::less for pairs of pointers, where do we draw the line? The 
same issue applies to individual pointers, smart pointer wrappers, 
std::vector&lt;T*&gt;, and so on.</P>
<P>Andy Koenig suggests that the real issue here is that we aren't 
distinguishing adequately between two different orderings, a "useful ordering" 
and a "canonical ordering" that's used just because we sometimes need 
<I>some</I> ordering without caring much which ordering it is. Another example 
of the later is typeinfo's <TT>before</TT>.</P>
<HR>
<A name=350>
<H3>350.&nbsp;allocator&lt;&gt;::address</H3></A>
<P><B>Section:</B>&nbsp;20.4.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.allocator.members">[lib.allocator.members]</A>, 
20.1.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.allocator.requirements">[lib.allocator.requirements]</A>, 
17.4.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-intro.html#lib.contents">[lib.contents]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Nathan Myers&nbsp; <B>Date:</B>&nbsp;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&amp;() 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&amp;(); };
  std::vector&lt;A&gt; aa;

  class B { };
  B* operator&amp;(B&amp;) { return 0; }
  std::vector&lt;B&gt; ba;
</PRE>
<P>In particular, the requirements table for Allocator (Table 32) specifies no 
semantics at all for member address(), and allocator&lt;&gt;::address is defined 
in terms of unadorned operator &amp;. </P>
<P><B>Proposed resolution:</B></P>
<P>In 20.4.1.1, Change the definition of allocator&lt;&gt;::address from:</P>
<BLOCKQUOTE>Returns: &amp;x </BLOCKQUOTE>
<P>to:</P>
<P>Returns: The value that the built in operator&amp;(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&lt;T&gt;::address(r)
  allocator&lt;T&gt;::address(s)
</PRE>
<P>In addition, in clause 17.4.1.1, add a statement:</P>
<BLOCKQUOTE>The Standard Library does not apply operator&amp; to any type for 
  which operator&amp; may be overloaded. </BLOCKQUOTE>
<P><B>Rationale:</B></P>
<P>The LWG believes both examples are ill-formed. The contained type is required 
to be CopyConstructible (20.1.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.copyconstructible">[lib.copyconstructible]</A>), 
and that includes the requirement that &amp;t return the usual types and values. 
Since allocators are intended to be used in conjunction with containers, and 
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.</P>
<P>It may well be that the CopyConstructible requirements are too restrictive 
and that either the container requirements or the CopyConstructive requirements 
should be relaxed, but that's a far larger issue. Marking this issue as "future" 
as a pointer to that larger issue.</P>
<HR>
<A name=351>
<H3>351.&nbsp;unary_negate and binary_negate: struct or class?</H3></A>
<P><B>Section:</B>&nbsp;20.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.function.objects">[lib.function.objects]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Dale Riley&nbsp; <B>Date:</B>&nbsp;12 Nov 2001</P>
<P>In 20.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.function.objects">[lib.function.objects]</A> 
the header &lt;functional&gt; synopsis declares the unary_negate and 
binary_negate function objects as struct. However in 20.3.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.negators">[lib.negators]</A> 
the unary_negate and binary_negate function objects are defined as class. Given 
the context, they are not "basic function objects" like negate, so this is 
either a typo or an editorial oversight. </P>
<P><I>[Taken from comp.std.c++]</I></P>
<P><B>Proposed resolution:</B></P>
<P>Change the synopsis to reflect the useage in 20.3.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.negators">[lib.negators]</A></P>
<P><I>[Curaao: Since the language permits "struct", the LWG views this as NAD. 
They suggest, however, that the Project Editor might wish to make the change as 
editorial.]</I></P>
<HR>
<A name=353>
<H3>353.&nbsp;<TT>std::pair</TT> missing template assignment</H3></A>
<P><B>Section:</B>&nbsp;20.2.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.pairs">[lib.pairs]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Martin Sebor&nbsp; <B>Date:</B>&nbsp;2 Dec 2001</P>
<P>The class template <TT>std::pair</TT> defines a template ctor (20.2.2, p4) 
but no template assignment operator. This may lead to inefficient code since 
assigning an object of <TT>pair&lt;C, D&gt;</TT> to <TT>pair&lt;A, B&gt;</TT> 
where the types <TT>C</TT> and <TT>D</TT> are distinct from but convertible to 
<TT>A</TT> and <TT>B</TT>, respectively, results in a call to the template copy 
ctor to construct an unnamed temporary of type <TT>pair&lt;A, B&gt;</TT> 
followed by an ordinary (perhaps implicitly defined) assignment operator, 
instead of just a straight assignment. </P>
<P><B>Proposed resolution:</B></P>
<P>Add the following declaration to the definition of <TT>std::pair</TT>: </P><PRE>    template&lt;class U, class V&gt;
    pair&amp; operator=(const pair&lt;U, V&gt; &amp;p);
</PRE>
<P>And also add a paragraph describing the effects of the function template to 
the end of 20.2.2: </P><PRE>    template&lt;class U, class V&gt;
    pair&amp; operator=(const pair&lt;U, V&gt; &amp;p);
</PRE>
<P><B>Effects</B>: <TT>first = p.first;</TT> <TT>second = p.second;</TT> 
<B>Returns</B>: <TT>*this</TT> </P>
<P><I>[Curaao: There is no indication this is was anything other than a design 
decision, and thus NAD.&nbsp; May be appropriate for a future standard.]</I></P>
<HR>
<A name=357>
<H3>357.&nbsp;&lt;cmath&gt; float functions cannot return HUGE_VAL</H3></A>
<P><B>Section:</B>&nbsp;26.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.c.math">[lib.c.math]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Ray Lischner&nbsp; <B>Date:</B>&nbsp;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>[Curaao: 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>Curaao: 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 Curaao 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>
<P><B>Rationale:</B></P>
<P>Will be fixed as part of more general work in the TR.</P>
<HR>
<A name=361>
<H3>361.&nbsp;num_get&lt;&gt;::do_get (..., void*&amp;) checks grouping</H3></A>
<P><B>Section:</B>&nbsp;22.2.2.2.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.facet.num.put.virtuals">[lib.facet.num.put.virtuals]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Martin Sebor&nbsp; <B>Date:</B>&nbsp;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>Change the first sentence of 22.2.2.2.2, p12 from </P>
<BLOCKQUOTE>Digit grouping is checked. That is, the positions of discarded 
  separators is examined for consistency with use_facet&lt;numpunct&lt;charT&gt; 
  &gt;(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>
<P><B>Rationale:</B></P>
<P>This would be a change: as it stands, the standard clearly specifies that 
grouping applies to void*. A survey of existing practice shows that most 
existing implementations do that, as they should.</P>
<HR>
<A name=367>
<H3>367.&nbsp;remove_copy/remove_copy_if and Input Iterators</H3></A>
<P><B>Section:</B>&nbsp;25.2.7 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-algorithms.html#lib.alg.remove">[lib.alg.remove]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Anthony Williams&nbsp; <B>Date:</B>&nbsp;13 May 2002</P>
<P>remove_copy and remove_copy_if (25.2.7 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/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="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-algorithms.html#lib.alg.remove">[lib.alg.remove]</A> 
paragraph 6. </P>
<P><B>Rationale:</B></P>
<P>The assumption is that an input iterator can't be dereferenced twice. There's 
no basis for that assumption in the Standard.</P>
<HR>
<A name=372>
<H3>372.&nbsp;Inconsistent description of stdlib exceptions</H3></A>
<P><B>Section:</B>&nbsp;17.4.4.8 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-intro.html#lib.res.on.exception.handling">[lib.res.on.exception.handling]</A>, 
18.6.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-support.html#lib.exception">[lib.exception]</A>, 
&nbsp; <B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Randy Maddox&nbsp; <B>Date:</B>&nbsp;22 Jul 2002</P>
<P>Paragraph 3 under clause 17.4.4.8 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/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="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/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><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Clause 17 is setting the overall library requirements, and it's clear and 
consistent. This sentence from Clause 18 is descriptive, not setting a 
requirement on any other class. </P>
<HR>
<A name=374>
<H3>374.&nbsp;moneypunct::frac_digits returns int not unsigned</H3></A>
<P><B>Section:</B>&nbsp;22.2.6.3.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.moneypunct.members">[lib.locale.moneypunct.members]</A>, 
22.2.6.3.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.moneypunct.virtuals">[lib.locale.moneypunct.virtuals]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Ray Lischner&nbsp; <B>Date:</B>&nbsp;8 Aug 2002</P>
<P>In section 22.2.6.3.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/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="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/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>
<P><B>Rationale:</B></P>
<P>Regardless of whether the return value is int or unsigned, it's always 
conceivable that frac_digits might return a nonsensical value. (Is 4294967295 
really any better than -1?) The clients of moneypunct, the get and put facets, 
can and do perform range checks.</P>
<HR>
<A name=377>
<H3>377.&nbsp;basic_string::insert and length_error</H3></A>
<P><B>Section:</B>&nbsp;21.3.5.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.string::insert">[lib.string::insert]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Ray Lischner&nbsp; <B>Date:</B>&nbsp;16 Aug 2002</P>
<P>Section 21.3.5.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-strings.html#lib.string::insert">[lib.string::insert]</A>, 
paragraph 4, contains the following, "Then throws length_error if size() &gt;= 
npos - rlen." </P>
<P>Related to DR 83, this sentence should probably be removed. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>This requirement is redundant but correct. No change is needed.</P>
<HR>
<A name=388>
<H3>388.&nbsp;Use of complex as a key in associative containers</H3></A>
<P><B>Section:</B>&nbsp;26.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.complex.numbers">[lib.complex.numbers]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Gabriel Dos Reis&nbsp; <B>Date:</B>&nbsp;8 Nov 2002</P>
<P>Practice with std::complex&lt;&gt; and the associative containers 
occasionally reveals artificial and distracting issues with constructs 
resembling: std::set&lt;std::complex&lt;double&gt; &gt; s; </P>
<P>The main reason for the above to fail is the absence of an approriate 
definition for std::less&lt;std::complex&lt;T&gt; &gt;. That in turn comes from 
the definition of the primary template std::less&lt;&gt; in terms of 
operator&lt;. </P>
<P>The usual argument goes as follows: Since there is no ordering over the 
complex field compatible with field operations it makes little sense to define a 
function operator&lt; operating on the datatype std::complex&lt;T&gt;. That is 
fine. However, that reasoning does not carry over to std::less&lt;T&gt; which is 
used, among other things, by associative containers as an ordering useful to 
meet complexity requirements. </P>
<P>Related issue: <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#348">348</A>.</P>
<P><B>Proposed resolution:</B></P>
<P>Informally: Add a specialization of std::less for std::complex.</P>
<P><B>Rationale:</B></P>
<P>Discussed in Santa Cruz. An overwhelming majority of the LWG believes this 
should not be treated a DR: it's a request for a design change, not a defect in 
the existing standard. Most people (10-3) believed that we probably don't want 
this change, period: as with issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#348">348</A>, 
it's hard to know where to draw the line. The LWG noted that users who want to 
put objects into an associative container for which <TT>operator&lt;</TT> isn't 
defined can simply provide their own comparison function object.</P>
<HR>
<A name=390>
<H3>390.&nbsp;CopyConstructible requirements too strict</H3></A>
<P><B>Section:</B>&nbsp;20.1.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-utilities.html#lib.copyconstructible">[lib.copyconstructible]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Future">Future</A>&nbsp; 
<B>Submitter:</B>&nbsp;Doug Gregor&nbsp; <B>Date:</B>&nbsp;24 Oct 2002</P>
<P>The CopyConstructible requirements in Table 30 state that for an object t of 
type T (where T is CopyConstructible), the expression &amp;t returns the address 
of t (with type T*). This requirement is overly strict, in that it disallows 
types that overload operator&amp; to not return a value of type T*. This occurs, 
for instance, in the <A href="http://www.boost.org/libs/lambda">Boost.Lambda</A> 
library, where operator&amp; is overloaded for a Boost.Lambda function object to 
return another function object. </P>
<P>Example:</P><PRE>  std::vector&lt;int&gt; u, v;
  int x;
  // ...
  std::transform(u.begin(), u.end(), std::back_inserter(v), _1 * x);
</PRE>
<P>_1 * x returns an unnamed function object with operator&amp; overloaded to 
not return T* , therefore rendering the std::transform call ill-formed. However, 
most standard library implementations will compile this code properly, and the 
viability of such binder libraries is severely hindered by the unnecessary 
restriction in the CopyConstructible requirements. </P>
<P>For reference, the address of an object can be retrieved without using the 
address-of operator with the following function template: </P><PRE>  template &lt;typename T&gt; T* addressof(T&amp; v)
  {
    return reinterpret_cast&lt;T*&gt;(
         &amp;const_cast&lt;char&amp;&gt;(reinterpret_cast&lt;const volatile char &amp;&gt;(v)));
  }
</PRE>
<P>Note: this relates directly to library issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-closed.html#350">350</A>, 
which will need to be reexamined if the CopyConstructible requirements change. 
</P>
<P><B>Proposed resolution:</B></P>
<P>Remove the last two rows of Table 30, eliminating the requirements that 
&amp;t and &amp;u return the address of t and u, respectively. </P>
<P><B>Rationale:</B></P>
<P>This was a deliberate design decision. Perhaps it should be reconsidered for 
C++0x. </P>
<HR>
<A name=392>
<H3>392.&nbsp;'equivalence' for input iterators</H3></A>
<P><B>Section:</B>&nbsp;24.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.input.iterators">[lib.input.iterators]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Corwin Joy&nbsp; <B>Date:</B>&nbsp;11 Dec 2002</P>
<P>In section 24.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.input.iterators">[lib.input.iterators]</A> 
table 72 - 'Input Iterator Requirements' we have as a postcondition of *a: "If 
a==b and (a, b) is in the domain of == then *a is equivalent to *b". </P>
<P>In section 24.5.3.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.istreambuf.iterator::equal">[lib.istreambuf.iterator::equal]</A> 
it states that "istreambuf_iterator::equal returns true if and only if both 
iterators are at end-of-stream, or neither is at end-of-stream, <I>regardless of 
what streambuf object they use</I>." (My emphasis). </P>
<P>The defect is that either 'equivalent' needs to be more precisely defined or 
the conditions for equality in 24.5.3.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.istreambuf.iterator::equal">[lib.istreambuf.iterator::equal]</A> 
are incorrect. (Or both). </P>
<P>Consider the following example:</P><PRE>   #include &lt;iostream&gt;
   #include &lt;fstream&gt;
   #include &lt;iterator&gt;
   using namespace std;

   int main() {
    ifstream file1("file1.txt"), file2("file2.txt");
    istreambuf_iterator&lt;char&gt; f1(file1), f2(file2);
    cout &lt;&lt; "f1 == f2 : " &lt;&lt; boolalpha &lt;&lt; (f1 == f2) &lt;&lt; endl;
    cout &lt;&lt; "f1 = " &lt;&lt; *f1 &lt;&lt; endl;
    cout &lt;&lt; "f2 = " &lt;&lt; *f2 &lt;&lt; endl;
    return 0;
   }
</PRE>
<P>Now assuming that neither f1 or f2 are at the end-of-stream then f1 == f2 by 
24.5.3.5 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iterators.html#lib.istreambuf.iterator::equal">[lib.istreambuf.iterator::equal]</A>.</P>
<P>However, it is unlikely that *f1 will give the same value as *f2 except by 
accident.</P>
<P>So what does *f1 'equivalent' to *f2 mean? I think the standard should be 
clearer on this point, or at least be explicit that this does not mean that *f1 
and *f2 are required to have the same value in the case of input iterators.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The two iterators aer not in the domain of ==</P>
<HR>
<A name=399>
<H3>399.&nbsp;volations of unformatted input function requirements</H3></A>
<P><B>Section:</B>&nbsp;27.6.1.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.istream.unformatted">[lib.istream.unformatted]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Martin Sebor&nbsp; <B>Date:</B>&nbsp;5 Jan 2003</P>
<P>The Effects clauses for the two functions below violate the general 
requirements on unformatted input functions outlined in 27.6.1.3: they do not 
begin by constructing a sentry object. Instead, they begin by calling widen 
('\n'), which may throw an exception. The exception is then allowed to propagate 
from the unformatted input function irrespective of the setting of exceptions(). 
</P>
<P>Note that in light of 27.6.1.1, p3 and p4, the fact that the functions allow 
exceptions thrown from widen() to propagate may not strictly speaking be a 
defect (but the fact that the functions do not start by constructing a sentry 
object still is). However, since an exception thrown from ctype&lt;charT&gt; 
::widen() during any other input operation (say, from within a call to 
num_get&lt;charT&gt;::get()) will be caught and cause badbit to be set, these 
two functions should not be treated differently for the sake of consistency. 
</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Not a defect. The standard is consistent, and the behavior required by the 
standard is unambiguous. Yes, it's theoretically possible for widen to throw. 
(Not that this will happen for the default ctype facet or for most real-world 
replacement ctype facets.) Users who define ctype facets that can throw, and who 
care about this behavior, can use alternative signatures that don't call widen. 
</P>
<HR>
<A name=429>
<H3>429.&nbsp;typo in basic_ios::clear(iostate)</H3></A>
<P><B>Section:</B>&nbsp;27.4.4.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.iostate.flags">[lib.iostate.flags]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Martin Sebor&nbsp; <B>Date:</B>&nbsp;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 &amp;&amp; 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() &amp; exceptions()) == 
0, returns. ..." <BR>to <BR>"If (state &amp; exceptions()) == 0, returns. ..." 
</P>
<P><B>Rationale:</B></P>
<P>This is a duplicate of issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#412">412</A>.</P>
<HR>
<A name=433>
<H3>433.&nbsp;Contradiction in specification of unexpected()</H3></A>
<P><B>Section:</B>&nbsp;18.6.2.4 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-support.html#lib.unexpected">[lib.unexpected]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Vyatcheslav Sysoltsev&nbsp; <B>Date:</B>&nbsp;29 Sep 
2003</P>
<P>Clause 15.5.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/except.html#except.unexpected">[except.unexpected]</A> 
paragraph 1 says that "void unexpected(); is called (18.6.2) immediately after 
completing the stack unwinding for the former function", but 18.6.2.4 (Effects) 
says that "void unexpected(); . . . Calls the unexpected_handler function in 
effect immediately after evaluating the throwexpression (18.6.2.2),". Isn't here 
a contradiction: 15.5.2 requires stack have been unwound when in void 
unexpected() and therefore in unexpected_handler but 18.6.2.4 claims that 
unexpected_handler is called "in effect immediately" after evaluation of throw 
expression is finished, so there is no space left for stack to be unwound 
therefore? I think the phrase "in effect immediately" should be removed from the 
standard because it brings ambiguity in understanding. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>There is no contradiction. The phrase "in effect immediately" is just to 
clarify which handler is to be called.</P>
<HR>
<A name=437>
<H3>437.&nbsp;Formatted output of function pointers is confusing</H3></A>
<P><B>Section:</B>&nbsp;27.6.2.5.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-iostreams.html#lib.ostream.inserters.arithmetic">[lib.ostream.inserters.arithmetic]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Ivan Godard&nbsp; <B>Date:</B>&nbsp;24 Oct 2003</P>
<P>Given: </P><PRE>void f(int) {}
void(*g)(int) = f;
cout &lt;&lt; g;
</PRE>
<P>(with the expected #include and usings), the value printed is a rather 
surprising "true". Rather useless too. </P>
<P>The standard defines:</P><PRE>ostream&amp; operator&lt;&lt;(ostream&amp;, void*);</PRE>
<P>which picks up all data pointers and prints their hex value, but does not 
pick up function pointers because there is no default conversion from function 
pointer to void*. Absent that, we fall back to legacy conversions from C and the 
function pointer is converted to bool. </P>
<P>There should be an analogous inserter that prints the address of a function 
pointer.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>This is indeed a wart, but there is no good way to solve it. C doesn't 
provide a portable way of outputting the address of a function point either.</P>
<HR>
<A name=439>
<H3>439.&nbsp;Should facets be copyable?</H3></A>
<P><B>Section:</B>&nbsp;22.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.categories">[lib.locale.categories]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Matt Austern&nbsp; <B>Date:</B>&nbsp;2 Nov 2003</P>
<P>The following facets classes have no copy constructors described in the 
standard, which, according to the standard, means that they are supposed to use 
the compiler-generated defaults. Default copy behavior is probably 
inappropriate. We should either make these classes uncopyable or else specify 
exactly what their constructors do.</P>
<P>Related issue: <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#421">421</A>.</P><PRE>        ctype_base
        ctype
        ctype_byname
        ctype&lt;char&gt;
        ctype_byname&lt;char&gt;
        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
</PRE>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>The copy constructor in the base class is private.</P>
<HR>
<A name=440>
<H3>440.&nbsp;Should std::complex use unqualified transcendentals?</H3></A>
<P><B>Section:</B>&nbsp;26.2.8 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.complex.transcendentals">[lib.complex.transcendentals]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#NAD">NAD</A>&nbsp; 
<B>Submitter:</B>&nbsp;Matt Austern&nbsp; <B>Date:</B>&nbsp;5 Nov 2003</P>
<P>Operations like <TT>pow</TT> and <TT>exp</TT> on <TT>complex&lt;T&gt;</TT> 
are typically implemented in terms of operations like <TT>sin</TT> and 
<TT>cos</TT> on <TT>T</TT>. Should implementations write this as 
<TT>std::sin</TT>, or as plain unqualified <TT>sin</TT>? </P>
<P>The issue, of course, is whether we want to use argument-dependent lookup in 
the case where <TT>T</TT> is a user-defined type. This is similar to the issue 
of valarray transcendentals, as discussed in issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#226">226</A>.</P>
<P>This issue differs from valarray transcendentals in two important ways. 
First, "the effect of instantiating the template <TT>complex</TT> for types 
other than float, double or long double is unspecified." (26.2.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-numerics.html#lib.complex.synopsis">[lib.complex.synopsis]</A>) 
Second, the standard does not dictate implementation, so there is no guarantee 
that a particular real math function is used in the implementation of a 
particular complex function.</P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>If you instantiate std::complex for user-defined types, all bets are off.</P>
<HR>
<A name=447>
<H3>447.&nbsp;Wrong template argument for time facets</H3></A>
<P><B>Section:</B>&nbsp;22.1.1.1.1 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-locales.html#lib.locale.category">[lib.locale.category]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Pete Becker&nbsp; <B>Date:</B>&nbsp;26 Dec 2003</P>
<P>22.1.1.1.1/4, table 52, "Required Instantiations", lists, among others: </P><PRE>    time_get&lt;char,InputIterator&gt;
    time_get_byname&lt;char,InputIterator&gt;
    time_get&lt;wchar_t,OutputIterator&gt;
    time_get_byname&lt;wchar_t,OutputIterator&gt;
</PRE>
<P>The second argument to the last two should be InputIterator, not 
OutputIterator. </P>
<P><B>Proposed resolution:</B></P>
<P>Change the second template argument to InputIterator. </P>
<P><B>Rationale:</B></P>Duplicate of issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#327">327</A> 

<HR>
<A name=450>
<H3>450.&nbsp;set::find is inconsistent with associative container 
requirements</H3></A>
<P><B>Section:</B>&nbsp;23.3.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.set">[lib.set]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Bill Plauger&nbsp; <B>Date:</B>&nbsp;30 Jan 2004</P>
<P>map/multimap have:</P><PRE>	iterator find(const key_type&amp; x) const;
	const_iterator find(const key_type&amp; x) const;
</PRE>
<P>which is consistent with the table of associative container requirements. But 
set/multiset have: </P><PRE>	iterator find(const key_type&amp;) const;
</PRE>
<P>set/multiset should look like map/multimap, and honor the requirements table, 
in this regard. </P>
<P><B>Proposed resolution:</B></P>
<P><B>Rationale:</B></P>
<P>Duplicate of issue <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-defects.html#214">214</A>.</P>
<HR>
<A name=451>
<H3>451.&nbsp;Associative erase should return an iterator</H3></A>
<P><B>Section:</B>&nbsp;23.1.2 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.associative.reqmts">[lib.associative.reqmts]</A>, 
23.3 <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lib-containers.html#lib.associative">[lib.associative]</A>&nbsp; 
<B>Status:</B>&nbsp;<A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#Dup">Dup</A>&nbsp; 
<B>Submitter:</B>&nbsp;Bill Plauger&nbsp; <B>Date:</B>&nbsp;30 Jan 2004</P>
<P>map/multimap/set/multiset have:</P><PRE>	void erase(iterator);
	void erase(iterator, iterator);
</PRE>
<P>But there's no good reason why these can't return an iterator, as for 
vector/deque/list:</P><PRE>	iterator erase(iterator);
	iterator erase(iterator, iterator);
</PRE>
<P><B>Proposed resolution:</B></P>
<P>Informally: The table of associative container requirements, and the relevant 
template classes, should return an iterator designating the first element beyond 
the erased subrange. </P>
<P><B>Rationale:</B></P>
<P>Duplicate of <A 
href="file:///C:/Documents%20and%20Settings/jward4/Local%20Settings/Temp/lwg-active.html#130">130</A></P>
<P>----- End of document -----</P></BODY></HTML>
