diff options
| author | Phil Edwards <pme@gcc.gnu.org> | 2000-10-05 20:15:29 +0000 |
|---|---|---|
| committer | Phil Edwards <pme@gcc.gnu.org> | 2000-10-05 20:15:29 +0000 |
| commit | 9a200b0a07e87fd05d1cfcc8564d8db0e80fae26 (patch) | |
| tree | c5dece229304405fcb3ed60aaaa93518faa723f4 /libstdc++-v3/docs | |
| parent | 2296d1645dd5fe783674be3d5ed1f8b788041f4e (diff) | |
| download | gcc-9a200b0a07e87fd05d1cfcc8564d8db0e80fae26.zip gcc-9a200b0a07e87fd05d1cfcc8564d8db0e80fae26.tar.gz gcc-9a200b0a07e87fd05d1cfcc8564d8db0e80fae26.tar.bz2 | |
acinclude.m4 (GLIBCPP_CHECK_CTYPE): Tweaks to message texts for public relations purposes.
2000-10-05 Phil Edwards <pme@sources.redhat.com>
* acinclude.m4 (GLIBCPP_CHECK_CTYPE): Tweaks to message texts
for public relations purposes.
* aclocal.m4: Regenerated.
* configure: Regenerated.
* docs/ext/howto.html: Additional explanation about hashing.
From-SVN: r36731
Diffstat (limited to 'libstdc++-v3/docs')
| -rw-r--r-- | libstdc++-v3/docs/ext/howto.html | 14 |
1 files changed, 12 insertions, 2 deletions
diff --git a/libstdc++-v3/docs/ext/howto.html b/libstdc++-v3/docs/ext/howto.html index dd7e314..11a6366 100644 --- a/libstdc++-v3/docs/ext/howto.html +++ b/libstdc++-v3/docs/ext/howto.html @@ -9,7 +9,7 @@ <TITLE>libstdc++-v3 HOWTO: Extensions</TITLE> <LINK REL="home" HREF="http://sources.redhat.com/libstdc++/docs/ext/"> <LINK REL=StyleSheet HREF="../lib3styles.css"> -<!-- $Id: howto.html,v 1.5 2000/09/19 21:54:48 pme Exp $ --> +<!-- $Id: howto.html,v 1.1 2000/09/25 21:42:14 pme Exp $ --> </HEAD> <BODY> @@ -84,6 +84,16 @@ functions, as well as some extra constructors specifying the number of buckets, etc. </P> + <P>Why would you want to use a hashing class instead of the + "normal" implementations? Matt Austern writes: + <BLOCKQUOTE><EM>[W]ith a well chosen hash function, hash tables + generally provide much better average-case performance than binary + search trees, and much worse worst-case performance. So if your + implementation has hash_map, if you don't mind using nonstandard + components, and if you aren't scared about the possibility of + pathological cases, you'll probably get better performance from + hash_map.</EM></BLOCKQUOTE> + </P> <P>(Side note: for those of you wondering, <B>"Why wasn't a hash table included in the Standard in the first #!$@ place?"</B> I'll give a quick answer: it was proposed, but too late and in too @@ -139,7 +149,7 @@ Comments and suggestions are welcome, and may be sent to <A HREF="mailto:pme@sources.redhat.com">Phil Edwards</A> or <A HREF="mailto:gdr@egcs.cygnus.com">Gabriel Dos Reis</A>. -<BR> $Id: howto.html,v 1.5 2000/09/19 21:54:48 pme Exp $ +<BR> $Id: howto.html,v 1.1 2000/09/25 21:42:14 pme Exp $ </EM></P> |