From 07a6e20be91fb7d10ade34cf5c8edb07efdc80ae Mon Sep 17 00:00:00 2001 From: Phil Edwards Date: Thu, 27 Jun 2002 22:09:02 +0000 Subject: stl_alloc.h: Deprecate all 'reallocate' memfns. 2002-06-27 Phil Edwards * include/bits/stl_alloc.h: Deprecate all 'reallocate' memfns. * docs/html/ext/howto.html: Update allocator notes. From-SVN: r55044 --- libstdc++-v3/docs/html/ext/howto.html | 27 ++++++++++++++++++--------- 1 file changed, 18 insertions(+), 9 deletions(-) (limited to 'libstdc++-v3/docs') diff --git a/libstdc++-v3/docs/html/ext/howto.html b/libstdc++-v3/docs/html/ext/howto.html index 7562652..d5755c6 100644 --- a/libstdc++-v3/docs/html/ext/howto.html +++ b/libstdc++-v3/docs/html/ext/howto.html @@ -37,7 +37,8 @@ @@ -154,7 +155,7 @@

-

Allocators

+

Allocators (versions 3.0, 3.1, 3.2)

Thread-safety, space efficiency, high speed, portability... this is a mess. Where to begin?

@@ -220,17 +221,18 @@

Available allocators in namespace std

First I'll describe the situation as it exists for the code which - was released in GCC 3.1. Then I'll - describe the differences for 3.0.x, which will not change much in - this respect. + was released in GCC 3.1 and 3.2. Then I'll describe the differences + for 3.0. The allocator classes also have source documentation, + which is described here (you + will need to retrieve the maintainer-level docs, as almost none of + these entities are in the ISO standard).

As a general rule of thumb, users are not allowed to use names which begin with an underscore. This means that to be portable between compilers, none of the following may be used in your program directly. (If you decide to be unportable, then you're free do do what you want, but it's not our fault if stuff breaks.) They are presented here for - information for maintainers and contributors in addition to users, but - we will probably make them available for users in 3.2 somehow. + information for maintainers and contributors in addition to users.

These classes are always available: