From e885821fff5b23afe3fd2358be556547d59f4d6c Mon Sep 17 00:00:00 2001 From: John Levon Date: Tue, 12 Aug 2003 08:46:43 +0000 Subject: [PATCH] guide.html (GLIBCXX_FORCE_NEW): Update remaining places for the name change from GLIBCPP_FORCE_NEW to... 2003-08-11 John Levon * docs/html/ext/howto/guide.html (GLIBCXX_FORCE_NEW): Update remaining places for the name change from GLIBCPP_FORCE_NEW to GLIBCXX_FORCE_NEW From-SVN: r70363 --- libstdc++-v3/ChangeLog | 7 +++++++ libstdc++-v3/docs/html/ext/howto.html | 11 ++++++----- 2 files changed, 13 insertions(+), 5 deletions(-) diff --git a/libstdc++-v3/ChangeLog b/libstdc++-v3/ChangeLog index 1f1db93b939..dab571de43b 100644 --- a/libstdc++-v3/ChangeLog +++ b/libstdc++-v3/ChangeLog @@ -1,3 +1,10 @@ +2003-08-11 John Levon + + * docs/html/ext/howto/guide.html (GLIBCXX_FORCE_NEW): Update + remaining places for the name change from GLIBCPP_FORCE_NEW + to GLIBCXX_FORCE_NEW + + 2003-08-11 Benjamin Kosnik * include/bits/basic_ios.h: Remove *_iter typedefs, change num* diff --git a/libstdc++-v3/docs/html/ext/howto.html b/libstdc++-v3/docs/html/ext/howto.html index 83cb50c365e..1c190a66613 100644 --- a/libstdc++-v3/docs/html/ext/howto.html +++ b/libstdc++-v3/docs/html/ext/howto.html @@ -285,20 +285,21 @@ SGI STL days. We have removed it in gcc 3.3. See next section for the new way to get the same effect.

-

Globally disabling memory caching: GLIBCPP_FORCE_NEW

+

Globally disabling memory caching: GLIBCXX_FORCE_NEW

Starting with gcc 3.3, if you want to globally disable memory caching within the library for the default allocator (i.e. the one you get for all library objects when you do not specify - which one to use), merely set GLIBCPP_FORCE_NEW (at this time, + which one to use), merely set GLIBCXX_FORCE_NEW (at this time, with any value) into your environment before running the program. You will obtain a similar effect without having to recompile your entire program and the entire library (the new operator in gcc is a light wrapper around malloc). If your - program crashes with GLIBCPP_FORCE_NEW in the environment, + program crashes with GLIBCXX_FORCE_NEW in the environment, it likely means that you linked against objects built against the older library. Code to support this extension is fully - compatible with 3.2 code if GLIBCPP_FORCE_NEW is not in the - environment. + compatible with 3.2 code if GLIBCXX_FORCE_NEW is not in the + environment. Prior to GCC 3.4, this variable was spelt + GLIBCPP_FORCE_NEW.

Writing your own allocators

Depending on your application (a specific program, a generic library,