This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [wwwdocs] 4.2 libstdc++ entry
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Benjamin Kosnik <bkoz at redhat dot com>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>, libstdc++ <libstdc++ at gcc dot gnu dot org>
- Date: Mon, 2 Apr 2007 23:28:05 +0200 (CEST)
- Subject: Re: [wwwdocs] 4.2 libstdc++ entry
- References: <4611481B.90003@redhat.com>
On Mon, 2 Apr 2007, Benjamin Kosnik wrote:
And, here's the gcc-4.2 version. Or, first crack at it. (Whoops!)
Good stuff, thanks! I'll make some minor editorial comments, the
contents is obviously your area of expertise, not mine. ;-)
Index: gcc-4.2/changes.html
===================================================================
+ <li>Support for TR1 random, complex, and C compatibility
+ headers. In addition, a lock-free version of
Perhaps mark up the header names as <random> and <complex>?
Or as <code>random</code> and <code>complex</code>?
+ Jordan's Google Summer of Code project on lock-free
+ containers. The implementation status for TR1 can be tracked in <a
+ href="http://gcc.gnu.org/onlinedocs/libstdc++/ext/tr1.html">
+ tr1.html </a> </li>
^^^
Extra blank, and we'll probably get one as the first character of the
link due to the line break. We could accept the overly long line to
avoid this.
+ __gnu_cxx</code>, and consolidate usage. Affected interfaces are
+ the functions <code> __exchange_and_add, __atomic_add</code>, and
<code>__exchange_and_add</code>, <code>__atomic_add</code>
+ the objects <code> __mutex, __recursive_mutex</code>, and <code>
<code>__mutex</code>, <code<__recursive_mutex</code>
+ <li>Support for versioning weak symbol names via namespace
+ association. Because this changes the names of exported symbols,
+ this is turned off by default in the current ABI. </li>
How can this be turned on? :-)
+ <li>Revised, simplified, and expanded policy-based associative
At the beginning of the patch, you use present tense, here it's past
tense. I believe the latter is more in line with what we generally
use.
+ containers, including data types for tree and trie forms
+ (<code>basic_tree, tree, trie</code>), lists
<code>basic_tree</code>, <code>tree</code>, <code>trie</code>
+ (<code>list_update</code>), and both collision-chaining and probing
+ hash-based containers (<code>basic_hash_table, cc_hash_table,
+ gp_hash_table</code>). More details per the <a
Same here.
+ <li> Extensions for type traits: <code> __conditional_type,
+ __numeric_traits, __add_unsigned, __removed_unsigned,
+ __enable_if</code>.
<code>__conditional_type</code>, <code>__numeric_traits</code>,
<code>__add_unsigned</code>, <code>__removed_unsigned</code>,
<code>__enable_if</code>.
An impressive list. :-)
Gerald