This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: [PATCH] fix doc references to GLIBCPP_FORCE_NEW
On Mon, Aug 11, 2003 at 02:05:08AM -0400, Phil Edwards wrote:
> IIRC, 3.3 introduced the variable using the PP form, 3.4+ will have the
> renamed form.
How about this one.
2003-08-11 John Levon <levon@movementarian.org>
* docs/html/ext/howto/guide.html (GLIBCXX_FORCE_NEW): Update
remaining places for the name change from GLIBCPP_FORCE_NEW
to GLIBCXX_FORCE_NEW
Index: docs/html/ext/howto.html
===================================================================
RCS file: /cvsroot/gcc/gcc/libstdc++-v3/docs/html/ext/howto.html,v
retrieving revision 1.33
diff -u -p -r1.33 howto.html
--- docs/html/ext/howto.html 28 Jul 2003 04:13:58 -0000 1.33
+++ docs/html/ext/howto.html 11 Aug 2003 15:03:53 -0000
@@ -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.
</p>
- <h3>Globally disabling memory caching:<code> GLIBCPP_FORCE_NEW</code></h3>
+ <h3>Globally disabling memory caching:<code> GLIBCXX_FORCE_NEW</code></h3>
<p>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.
</p>
<h3>Writing your own allocators</h3>
<p>Depending on your application (a specific program, a generic library,