<html>
<head>
<title>LWG Paper Summary</title>
<style>
p {text-align:justify}
li {text-align:justify}
blockquote.note
{
    background-color:#E0E0E0;
    padding-left: 15px;
    padding-right: 15px;
    padding-top: 1px;
    padding-bottom: 1px;
}
ins {background-color:#FFFFA0}
del {background-color:#FFFFA0}
</style>
</head>

<body>

<address align=right>
Document number: N2003=06-0073<br>
<br>
<a href="mailto:howard.hinnant@gmail.com">Howard E. Hinnant</a><br>
2006-04-21
</address>
<hr>
<h1 align=center>LWG Paper Summary</h1>

<h2>Contents</h2>

<ul>
<li><a href="#General Documentation">General Documentation</a></li>
<li><a href="#Improvements to existing facilities">Improvements to existing facilities</a></li>
<li><a href="#C compatibility">C compatibility</a></li>
<li><a href="#Basic Utilities">Basic Utilities</a></li>
<li><a href="#Smart pointers">Smart pointers</a></li>
<li><a href="#Communication">Communication</a></li>
<li><a href="#Containers">Containers</a></li>
<li><a href="#Iterators">Iterators</a></li>
<li><a href="#Algorithms">Algorithms</a></li>
<li><a href="#Function Objects">Function Objects</a></li>
<li><a href="#Multithreading">Multithreading</a></li>
<li><a href="#Numerics">Numerics</a></li>
<li><a href="#Text Facilities">Text Facilities</a></li>
<li><a href="#Hardware">Hardware</a></li>
</ul>

<hr>
<hr>
<h2><a name="General Documentation"></a>General Documentation</h2>
<hr>
<hr>

<p><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">N1836</a>
&nbsp;<b>TR1</b>&nbsp;Date:&nbsp;2005-06-24</p>

<p><a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1901.html">N1901</a>
<b>C++0x Standard Library wishlist (revision 5)</b> Date: 2005-10-14<br>
Related papers:</p>
<blockquote>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1766.html">N1766</a>
<b>C++0x Standard Library wishlist (revision 4)</b> Date: 2005-03-04<br>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1752.html">N1752</a>
<b>C++0x Standard Library wishlist (revision 3)</b> Date: 2005-01-17<br>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1732.html">N1732</a>
<b>C++0x Standard Library wishlist (revision 2)</b> Date: 2004-11-05<br>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1689.html">N1689</a>
<b>C++0x Standard Library wishlist</b> Date: 2004-09-10
</blockquote>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1905.pdf">N1905</a>
<b>Working Draft, Standard for Programming Language C++</b> Date: 2005-10-19<br>
Related papers:</p><blockquote>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1804.pdf">N1804</a>
    <b>Working Draft, Standard for Programming Language C++</b> Date: 2005-04-27<br>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/prot/14882fdis/n1733.pdf">N1733</a>
    <b>Working Draft, Standard for Programming Language C++</b> Date: 2004-11-05<br>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/prot/14882fdis/n1655.pdf">N1655</a>
    <b>Unofficial Working Draft, Standard for Programming Language C++</b> Date: 2004-07-16<br>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/prot/14882fdis/n1577.pdf">N1577</a>
    <b>Working Draft, Standard for Programming Language C++</b> Date: 2004-02-07<br>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2001/n1316">N1316</a>
    <b>Draft Expanded Technical Corrigendum</b> Date: 2001-09-13<br>
</blockquote>

<hr>
<hr>
<h2><a name="Improvements to existing facilities"></a>Improvements to existing facilities</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1953.html">N1953</a>
<b>Upgrading the Interface of Allocators using API Versioning</b> Date:  2006-02-14<br>
Status: Open.<br>
</p>
<p>
Berlin [2006-04] Split interest.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1913.pdf">N1913</a>
<b>A Proposal to Improve const_iterator Use (version 3)</b> Date:  2005-10-20<br>
Status: C++0X.<br>
</p>
<p>
Berlin [2006-04]: Voted into the C++0X working draft.
</p>
<p>Related papers:</p>
<blockquote>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1865.pdf">N1865</a>
    <b>A Proposal to Improve const_iterator Use (version 2)</b> Date:  2005-08-24<br>
    </p>
    <blockquote>
        <p>
        Mont Tremblant [2005-10]:  Overall interest for C++0X.
        </p>
        <ul>
        <li>Yes on the member functions.</li>
        <li>Some sentiment against changing the container requirements.</li>
        <li>Prefer "cname" to "const_name".</li>
        <li>Not interested in free function variant.</li>
        </ul>
    </blockquote>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1674.pdf">N1674</a>
    <b>A Proposal to Improve const_iterator Use from C++0X Containers</b> Date: 2004-08-31<br>
    </p>
    <blockquote>
        <p>
        Lillehammer [2005-04]:  Mixed interest.  The no votes were just because
        people didn't see the need.
        </p>
    </blockquote>
</blockquote>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1880.htm">N1880</a>
<b>A proposal to extend numeric_limits for consistent range query (Revision 1)</b> Date: 2005-08-29<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  Interested for C++0X. Pete will provide improved wording.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>resize_capacity</b> Date:  2005-08-24<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  string already has this functionality (shrink to fit).
There is interest in providing it for vector.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>Require O(1) size</b> Date:  2005-08-24<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  Possible interest.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>zero()</b> Date:  2005-08-24<br>
Status: Closed.
</p>
<p>
Mont Tremblant [2005-10]: No interest at this time because auto is not part
of the language.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>map/set::splice()</b> Date:  2005-08-24<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]: Possible interest with other function names.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>vector/string::set_buffer()</b> Date:  2005-08-24<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]: Possible interest for vector, but difficult with allocators.
No interest for string because it is not contiguous  (but see
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html#530">lwg 530</a>).
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>assign(n, F)</b> Date:  2005-08-24<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]: Possible interest, signficant concerns.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>lazy_insert/lazy_find</b> Date:  2005-08-24<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]: Interest in solving problem, not sure this is the right approach.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1856.html">N1856-N1862</a>
<b>Rvalue Reference Recommendations for Chapters 20-27</b> Date: 2005-08-26<br>
Status: Ready, pending language support.<br>
Related papers:</p>
<blockquote>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1771.html">N1771</a>
    <b>Impact of the rvalue reference on the Standard Library</b> Date: 2005-03-03<br>
</blockquote>
<p>
Mont Tremblant [2005-10]:  Interested for C++0X, assuming the committee adopts
the necessary language support.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1822.pdf">N1822</a>
<b>A Proposal to add a max significant decimal digits value to the C++ Standard Library Numeric limits</b> Date: 2005-06-14<br>
Status: C++0X.
</p>
<p>
Berlin [2006-04]:  Voted into the C++0X working draft.
</p>
<p>
Mont Tremblant [2005-10]:  Interested for C++0X.
</p>
<hr>

<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1981.html">N1981</a>
<b>Uniform Use of std::string Revision 1</b> Date: 2006-04-05<br>
Status: C++0X.
</p>
<p>
Berlin [2006-04]:  Voted into the working draft with minor modfications.
</p>
<p>Related papers:</p>

<blockquote>
	<p>
	<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1802.html">N1802</a>
	<b>Uniform Use of std::string</b> Date: 2005-04-18<br>
	Status: Open.
	</p>
	<p>
	Mont Tremblant [2005-10]:  Interested for C++0X.  Pete and Beman tasked with
	working out conflicts between this and the
	<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1889.html">file system proposal</a>.
	</p>
</blockquote>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1780.html">N1780</a>
<b>Comments on LWG issue 233: Insertion hints in associative containers</b> Date: 2005-04-23<br>
Status: Open.<br>
Reference:  <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/lwg-active.html#233">lwg issue 233</a>.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1599.html">N1599</a>
<b>Issue 431: Swapping containers with unequal allocators</b> Date:  2004-02-11<br>
Status: Open.<br>
Reference: <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#431">lwg issue 431</a>.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1589.html">N1589</a>
<b>complex and Issue 387</b> Date:  2004-02-11<br>
Status: Open.<br>
Reference: <a href="http://anubis.dkuug.dk/jtc1/sc22/wg21/docs/lwg-active.html#387">lwg issue 387</a>.<br>
Related papers:
</p>
<blockquote>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2002/n1388.pdf">N1388</a>
    <b>Enhancing numerical support</b> Date:  2002-09-07<br>
</blockquote>
<hr>

<hr>
<h2><a name="C compatibility"></a>C compatibility</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a>
<b>C compatibility</b><br>
Status:  C++0X.
</p>
<p>
Related papers:
</p>
<blockquote>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1835.pdf">N1835</a>
    <b>&lt;stdint.h&gt; for C++</b> Date: 2005-06-23
</blockquote>
<p>
Mont Tremblant [2005-10]:  <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1835.pdf">N1835</a>
discussed with strong support for C++0X.  The more general TR1 C compatibility
package not yet specifically discussed.
</p>
<hr>

<hr>
<h2><a name="Basic Utilities"></a>Basic Utilities</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a>
<b>&lt;type_traits&gt;</b><br>
Status: C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a>
<b>reference_wrapper</b><br>
Status: C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1939.html">N1939</a>
<b>Any Library Proposal for TR2</b> Date: 2006-02-24<br>
Status: Open.
</p>

<p>
Berlin [2006-04]: Strong interest for TR2.
</p>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1900.pdf">N1900</a>
<b>Proposal to Add Date-Time to the C++ Standard Library</b> Date: 2005-10-02<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  Interested for TR2.  Needs formal proposed wording.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1879.htm">N1879</a>
<b>A proposal to add a general purpose ranged-checked numeric_cast&lt;&gt; (Revision 1)</b> Date: 2005-08-29<br>
Status: Review.
</p>
<p>
Mont Tremblant [2005-10]:  Interested for TR2.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1878.htm">N1878</a>
<b>A proposal to add an utility class to represent optional objects (Revision 1)</b> Date: 2005-08-29<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  Interested for TR2.  Significant concerns about the
interface including:
</p>
<ul>
<li>Do we want a pointer interface?</li>
<li>Appears to provide two ways of doing the same thing.</li>
<li>Depends on nullptr - is there a backup plan?</li>
<li>Concern over use of references.</li>
</ul>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>&lt;std&gt;/&lt;tr1&gt;</b> Date: 2005-08-24<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  There was some interest, but a majority opposed.  Leaving
open for now but will close soon without further support.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>restricted_bool</b> Date: 2005-08-24<br>
Status: Closed.
</p>
<p>
Berlin [2006-04]: No interest.
</p>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1508.htm">N1508</a>
<b>Proposal to add Deletion Traits to the Standard Library</b> Date: 2003-09-13<br>
Status: Unknown.
</p>
<hr>

<hr>
<h2><a name="Smart pointers"></a>Smart pointers</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a>
<b>shared_ptr/weak_ptr</b><br>
Status: C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1851.pdf">N1851</a>
<b>Improving Usability and Performance of TR1 Smart Pointers</b> Date:  2005-08-25<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  Interested in some parts of this proposal:
</p>
<ul>
<li>Interest in giving shared_ptr an allocator.</li>
<li>Interest in aliasing using free function syntax (instead of constructor syntax).</li>
<li>Mixed interest in providing factory functions.</li>
<li>No interest in managed_ptr, but there is interest in a standardized deleter
which would acheive the same functionality (say for unique_ptr).</li>
</ul>

<p>
Pre Berlin:  Peter has implemented:
</p>
<blockquote><pre>
shared_ptr::shared_ptr( Y * p, D d, A a );
shared_ptr::reset( Y * p, D d, A a );
</pre></blockquote>
<p>
in boost::shared_ptr. Stateful/non-equal allocators are supported,
allocations/deallocations are done via rebound copies of 'a'. A test that
exercises the functionality can be found
<a href="http://cvs.sourceforge.net/viewcvs.py/*checkout*/boost/boost/libs/smart_ptr/test/shared_ptr_alloc2_test.cpp">here</a>.
</p>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1739.pdf">N1739</a>
<b>Adding a Policy-Based Smart Pointer Framework to the Standard Library</b> Date:  2004-11-08<br>
Status: Closed.
</p>
<p>
Berlin [2006-04]: This is a presentation of N1681 which was reviewed and
rejected in Lillehammer.
</p>
<p>
Related papers:</p>
<blockquote>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1681.pdf">N1681</a>
    <b>A Proposal to Add a Policy-Based Smart Pointer Framework to the Standard Library</b> Date:  2004-09-01
    </p>
    <p>
    Lillehammer [2005-04]: No support for a policy-based framework at this time.
    This is a refinement of Loki, but, while Loki is in use, this refinement isn't.
    We'll consider such a proposal later, if there is widespread practice and
    strong arguments for it.
    </p>
</blockquote>
<hr>

<hr>
<h2><a name="Communication"></a>Communication</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1925.pdf">N1925</a>
<b>Networking proposal for TR2 (rev. 1)</b> Date:  2005-12-04<br>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1974.html">N1974</a>
<b>Boost Network Library Query</b> Date:  2006-03-31<br>
Status: Open.
</p>
<p>
Berlin [2006-04]: There is a lot of overlap in these two propsals and Gerhard has
offered to help combine them into one.  Strong interest for TR2.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1838.pdf">N1838</a>
<b>A Proposal to Add Sockets to the Standard Library</b> Date: 2005-06-24<br>
Status: Closed.
</p>
<p>
Mont Tremblant [2005-10]: There is clear interest for a proposal addressing this
issue, but the lwg does not believe the library presented herein is what we are
looking for.
</p>
<hr>

<hr>
<h2><a name="Containers"></a>Containers</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a> <b>tuple</b><br>
Status: C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a> <b>array</b><br>
Status: C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a> <b>unordered</b><br>
Status: C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1871.html">N1871</a>
<b>Range Library Proposal</b> Date: 2005-08-27<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]: Interested for TR2.  There were concerns about the use
of new language features which are not yet a sure thing.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1850.pdf">N1850</a>
<b>Towards a Better Allocator Model</b> Date: 2005-08-25<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]: No interest in making the default allocator polymorphic.
Possible interest in pursuing some system by which a container's allocator is
propagated to the container's value_type.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1847.pdf">N1847</a>
<b>vector&lt;bool&gt;: More Problems, Better Solutions</b> Date:  1999-10-20<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  There is interest in deprecating it and providing the
functionality in a different container (perhaps bitvector).  There currently is
no bitvector proposal.
</p>
<hr>

<hr>
<h2><a name="Iterators"></a>Iterators</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>next/prior</b> Date:  2005-08-24<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  Possible interest.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1672.html">N1672</a>
<b>Adapting N1640=04-0080 To C++0x</b> Date: 2004-09-10<br>
Related papers:</p>
<blockquote>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1640.html">N1640</a>
    <b>New Iterator Concepts</b> Date: 2004-04-10<br>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1550.htm">N1550</a>
    <b>New Iterator Concepts</b> Date: 2003-10-16<br>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1531.html">N1531</a>
    <b>New Iterator Concepts</b> Date: 2003-09-22<br>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1477.html">N1477</a>
    <b>New Iterator Concepts</b> Date: 2003-04-28<br>
</blockquote>
<p>
There is significant interest in moving forward with new iterator concepts for
C++0X, but there is no concrete proposal before the lwg at this time.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1641.html">N1641</a>
<b>Iterator Facade and Adaptor</b> Date: 2004-04-10<br>
Related papers:</p>
<blockquote>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1530.html">N1530</a>
    <b>Iterator Facade and Adaptor</b> Date: 2003-09-22<br>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2003/n1476.html">N1476</a>
    <b>Iterator Facade and Adaptor</b> Date: 2003-04-28<br>
</blockquote>
<p>
There is significant interest in moving forward with iterator adators for
C++0X, but there is no concrete proposal before the lwg at this time.  This is
blocked by iterator concepts.
</p>
<hr>

<hr>
<h2><a name="Algorithms"></a>Algorithms</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1873.html">N1873</a>
<b>The Cursor/Property Map Abstraction</b> Date: 2005-08-26<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  Possible interest for C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>is_sorted / nonunique_copy</b> Date:  2005-08-24<br>
Status: Open.
</p>
<p>
Berlin [2006-04]: Strong interested in is_sorted returning bool. Slightly less
interest in an sorted_up_to returning iterator.  Dietmar notes that is_sorted is
a trivial call to find_adjacent. Interest in is_heap (or is_heap_up_to)
returning bool or iterator as appropriate. No interest in nonunique_copy.
</p>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1990.html">N1990</a>
<b>Proposed Text for minmax (N1840)</b> Date: 2006-04-06<br>
Status: C++0X.<br>
</p>

<p>
Berlin [2006-04]:  Voted into the C++0X working draft except that <tt>reference_wrapper</tt>
was removed as it is no longer needed due to CWG issue 106 (references to references).
</p>

<p>
Related papers:
</p>
<blockquote>
	<p>
	<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1840.pdf">N1840</a>
	<b>C++0x Proposal: Function template std::minmax and / or algorithm std::minmax_element</b> Date: 2005-06-28<br>
	</p>
	<p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
    <b>minmax</b> Date:  2005-08-24<br>
    </p>
</blockquote>
<p>
Mont Tremblant [2005-10]:  Interested for C++0X.
</p>
<hr>

<hr>
<h2><a name="Function Objects"></a>Function Objects</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a> <b>result_of</b><br>
Status: C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a> <b>mem_fn</b><br>
Status: C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a> <b>bind</b><br>
Status: C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a> <b>function</b><br>
Status: C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>cast functors</b> Date:  2005-08-24<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  Possible interest.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1667.pdf">N1667</a>
<b>Accessing the target of a tr1::function object</b> Date:  2004-07-16<br>
Status:  Unknown.
</p>
<hr>

<hr>
<h2><a name="Multithreading"></a>Multithreading</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1907.html">N1907</a>
<b>A Multi-threading Library for Standard C++, Revision 1</b> Date:  2005-10-19<br>
Status: Open.
</p>
<p>
Berlin [2006-04]: Howard and Pete to work on some modifications to this proposal.  EWG
also very interested in closely cooperating on this.  Split feelings on whether this
should target C++0X or TR2.
</p>
<p>
Related papers:
</p>
<blockquote>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1682.html">N1682</a>
    <b>A Multi-threading Library for Standard C++</b> Date:  2004-09-10<br>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1834.html">N1834</a>
    <b>A Pleading for Reasonable Parallel Processing Support in C++</b> Date: 2005-06-24<br>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1815.html">N1815</a>
    <b>ISO C++ Strategic Plan for Multithreading</b> Date: 2005-05-02<br>
</blockquote>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1883.pdf">N1883</a>
<b>Preliminary Threading Library Proposal for TR2</b> Date:  2005-08-29<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]:  Strong interest in pursuing both this proposal, and
a proposal more along the lines of boost::threads (resulting in
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1907.html">N1907</a>).
</p>
<hr>

<hr>
<h2><a name="Numerics"></a>Numerics</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a> <b>&lt;random&gt;</b><br>
Status: C++0X.
</p>

<p>
Berlin:
</p>
<ul>
<li>Strongly in favor of dropping variant_generator and input_type.</li>
<li>Strongly in favor of adding helper function for engine return type conversion.</li>
<li>Mixed interest in making generator min/max const expressions.</li>
<li>Mixed interest in adding random number engine adaptor concept.</li>
<li>Strong interest in adding min(), max() for distributions.</li>
</ul>

<p>Related papers:</p>
<blockquote>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1933.pdf">N1933</a>
    <b>Improvements to TR1's Facility for Random Number Generation</b> Date: 2006-02-23<br>
    Status: New.
    </p>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1932.pdf">N1932</a>
    <b>Random Number Generation in C++0X: A Comprehensive Proposal</b> Date: 2006-02-23<br>
    Status: New.
    </p>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1914.pdf">N1914</a>
    <b>A Proposal to Add Random-Number Distributions to C++0x</b> Date: 2005-10-21<br>
    Status: New.
    </p>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1588.pdf">N1588</a>
    <b>On Random-Number Distributions for C++0x</b> Date: 2004-02-13<br>
    </p>
    <p>
    Lillehammer [2005-04]:  Roughly doubles the number of distributions, from
    9 to 19. Includes most of the distributions that are in common use in
    multiple fields. Strong support.
    </p>
</blockquote>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a> <b>special math functions</b><br>
Status: Open.
</p>
<p>
Berlin [2006-04]:  Had support of the LWG for C++0X, but not that of the full committee.
</p>
<p>Related papers:</p>
<blockquote>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1884.htm">N1884</a>
    <b>Further Restrictions on Special Math Functions</b> Date: 2005-08-26<br>
    Status: Ready.
    </p>
    <p>
    Mont Tremblant [2005-10]:  Strong interest in treating as a defect applied to TR1.
    Not voted on.  Will be applied if and when we move this library to the standard.
    </p>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1697.html">N1697</a>
    <b>Restrictions on Order Parameters for Bessels and Other Function Families</b> Date: 2004-09-10<br>
    Status:  Unknown.
    </p>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1665.pdf">N1665</a>
    <b>Guidelines for Domain Errors in Mathematical Special Functions</b> Date: 2004-07-15<br>
    Status:  Unknown.
    </p>
</blockquote>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1870.html">N1870</a>
<b>statistics</b> Date: 2005-08-24<br>
Status: Open.
</p>
<p>
Berlin [2006-04]: Strong interest in iterator-based statistic functions. No
interest in other functions in this proposal.
</p>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1869.html">N1869</a>
<b>Wording for imaginary numbers</b> Date: 2005-08-24<br>
Status: Closed.
Related papers:</p>
<blockquote>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1612.pdf">N1612</a>
    <b>How we might remove the remaining shortcomings of std::complex&lt;T&gt;</b> Date: 2004-03-29<br>
</blockquote>
<p>
Mont Tremblant [2005-10]:  Rejected. Not broadly useful enough for standardization.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1843.pdf">N1843</a>
<b>A Proposal to add Interval Arithmetic to the C++ Standard Library</b> Date: 2005-08-01<br>
Status: Open.
</p>
<p>
Berlin [2006-04]: Sylvain gave update, reviewed applications of the library.
Discussed pass-by-value vs pass by const ref. Steve gave update on user base (it
exists). User community actively discussing it. Sun has open source interval
library (looser than GPL).  Strong interest for TR2.
</p>
<p>
Mont Tremblant [2005-10]: Possible interest for TR2.  Concerns about sufficiently
large user base to justify standardizing. Concerns about implementing "extension"
functions. Hard to implement - worth the functionality?
</p>
<hr>

<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1977.html">N1977</a>
<b>Decimal Types for C++: Draft 4</b> Date: 2006-04-03<br>
Status: Decimal TR registered.
</p>
<p>
Berlin [2006-04]: Apply to ISO for registration of a Technical Report on decimal
types for C++. N1977 is the initial draft of that technical report.
</p>
<p>
Related papers:
</p>
<blockquote>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1965.html">N1965</a>
<b>Decimal Types for C++: Draft 3</b> Date: 2006-02-25<br>
</p>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1839.html">N1839</a>
<b>Decimal Types for C++: Second Draft</b> Date: 2005-06-24<br>
</p>
<p>
Mont Tremblant [2005-10]: Discussed.
</p>
</blockquote>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1744.pdf">N1744</a>
<b>Big Integer Library Proposal for C++0x</b> Date: 2005-01-13<br>
Status: Closed.
</p>
<p>
Lillehammer [2005-04]: We haven't seen an analysis of use cases, so we don't
know which communities this is important to, what their needs are, and whether
this type meets their needs.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1718.pdf">N1718</a>
<b>A Proposal to add the Infinite Precision Integer and Rational to the C++ Standard Library</b> Date: 2004-11-01<br>
Status: Open.

<p>
Berlin [2006-04]: Interest in infinite precision half of this paper. There
exists weak support for rational. Needs numeric_limits support. Interested more
in basic arithmetic than the math functions. gcd and lcm desired.
</p>

<p>Related papers:</p>
<blockquote>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1692.pdf">N1692</a>
    <b>A Proposal to add the Infinite Precision Integer to the C++ Standard Library</b>     Date:     2004-07-01<br>
    </p>
    <p>
    Lillehammer [2005-04]: No support for adopting this proposal.  Insufficient
    detail.
    </p>
</blockquote>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1668.pdf">N1668</a>
<b>A Proposal to add Mathematical Functions for Statistics to the C++ Standard Library</b> Date: 2004-08-11<br>
Status: Open.
</p>
<p>
Lillehammer [2005-04]: The main argument against this proposal is that a
high-quality implementation would be extremely hard; this is about 150 functions,
most of which have several parameters. Issue: are we willing to standardize
something with the expectation that most implementations will be low quality?
Are these functions ones where poor accuracy is acceptable? (If so, we could do
this for float only, and drop the double and long double versions.)
</p>
<p>
Mixed interest.
</p>
<p>
No consensus for bringing this forward at this meeting. What might change 
people's mind: 1. Reasoning for why to include these functions and exclude
others. 2. A smaller set of functions. 3. If this is intended to support an
easy-to-use statistical package, then show the interface for that statistical
package first.
</p>
<hr>

<hr>
<h2><a name="Text Facilities"></a>Text Facilities</h2>
<hr>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1836.pdf">TR1</a>
<b>&lt;regex&gt;</b><br>
Status: C++0X.
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1975.html">N1975</a>
<b>Filesystem Library Proposal for TR2 (Revision 3)</b> Date: 2006-04-04<br>
Status: TR2.
</p>
<p>
Berlin [2006-04]: Voted into TR2.
</p>
<p>Related papers:</p>
<blockquote>
	<p>
	<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1934.html">N1934</a>
	<b>Filesystem Library Proposal for TR2 (Revision 2)</b> Date: 2006-02-22<br>
	</p>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1889.html">N1889</a>
    <b>Filesystem Library Proposal for TR2 (Revision 1)</b> Date: 2005-09-30<br>
    </p>
    <p>
    N1889 updated in response to comments on N1841.  Not yet reviewed.
    </p>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1841.html">N1841</a>
    <b>Filesystem Library Proposal</b> Date: 2005-08-23<br>
    </p>
    <p>
    Mont Tremblant [2005-10]:  Strong interest for TR2.
    </p>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1576.html">N1576</a>
    <b>Filesystem library query</b>  Date: 2004-02-06<br>
    </p>
    <p>
    Lillehammer [2005-04]: Not yet a proposal, but a heads-up. Library to
    manipulate filenames, directories, etc. There was a little bit of discussion
    of how this interacts with fstream. People were generally favorable to the
    idea. Those who are interested should follow the link and read the library
    documentation.
    </p>
</blockquote>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1872.html">N1872</a>
<b>Proposal for new string algorithms in C++0x</b> Date: 2005-08-26<br>
Status: Open.
</p>
<p>
Mont Tremblant [2005-10]: Interested for TR2.  Some concern was expressed over
the interface and choice of functions.  There was not a clear concensus as to
whether it would be better to go with generic free functions, basic_string
free functions, or basic_string member functions (for the algorithms).
</p>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1991.html">N1991</a>
<b>Proposed Text for defaultfloat (N1842)</b> Date: 2006-04-06<br>
Status: C++0X.
</p>
<p>
Berlin [2006-04]: Voted into C++0X with the following changes:
</p>
<ul>
<li>Renamed <tt>automatic</tt> to <tt>defaultfloat</tt>.</li>
<li>Dropped <tt>noadjust</tt>.</li>
</ul>
<p>
Related papers:
</p>
<blockquote>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1842.pdf">N1842</a>
<b>A Proposal to add two iostream manipulators to the C++ Standard Library</b> Date: 2005-07-27<br>
</p>
<p>
Mont Tremblant [2005-10]: Strong support for the <tt>automatic</tt> manipulator
for C++0X except that no one liked the name.  Several alternatives were suggested
but there was no clear "right" name.
</p>
<p>
No support for the <tt>noadjust</tt>
manipulator because it means the same thing as the current manipulator <tt>right</tt>.
</p>
</blockquote>
<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1803.html">N1803</a>
<b>Simple Numeric Access</b> Date: 2005-04-18<br>
Status: Open.
</p>
<p>
Berlin [2006-04]: interest in wstring overloads.  Still split on targeting
C++0X or TR2.
</p>
<p>
Mont Tremblant [2005-10]:  Strong support for this proposal.  There is no
concensus as to whether it should target C++0X or TR2.
</p>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1973.html">N1973</a>
<b>Lexical Conversion Library Proposal for TR2</b> Date: 2006-03-21<br>
Status: Open.
</p>
<p>
Berlin [2006-04]: Interest for TR2.
</p>

<hr>
<p>
<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2006/n1957.html">N1957</a>
<b>Proposed Library Additions For Code Conversion</b> Date: 2006-02-21<br>
Status: Open.
</p>
<p>
Berlin [2006-04]: Ready for TR2. Delay one meeting from now to allow time for
alternate proposals.
</p>
<p>
Martin has two concerns:
</p>
<ol>
<li>You can't construct a wstring_convert object with a code_cvt object.</li>
<li>Error handling and recovery not robust enough.</li>
</ol>
<p>
Related papers:
</p>
<blockquote>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2005/n1750.html">N1750</a>
    <b>Critique of Code Conversion Proposal (N1683)</b> Date: 2005-01-13<br>
    </p>
    <p>
    <a href="http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2004/n1683.html">N1683</a>
    <b>Proposed Library Additions for Code Conversions</b> Date: 2004-09-10<br>
    </p>
</blockquote>
<p>
Lillehammer [2005-04]: Strong support for TR2, some support for C++0X.  The only
semantic issue that was controversial was whether to parameterize on containers
or iterators.  Strong support for the iterator parameterization.  Bill will
create a detailed proposal for the next pre-meeting mailing.
</p>

<hr>
<h2><a name="Hardware"></a>Hardware</h2>
<hr>

<a href="http://www.open-std.org/jtc1/sc22/wg21/docs/TR18015.pdf">Performance TR</a>
<b>Technical Report on C++ Performance</b> Date: 2006-02-15<br>
Status: Open.
</p>
<p>
Issue:  Interest in <tt>&lt;iohw.h&gt;</tt> and <tt>&lt;hardware&gt;</tt> for C++0X?
Not yet discussed.
</p>

<hr>
</body>
</html>
