FreeChainXenon/gcc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

guide.html (GLIBCXX_FORCE_NEW): Update remaining places for the name change from GLIBCPP_FORCE_NEW to...

Browse source 
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

From-SVN: r70363
This commit is contained in:
John Levon 2003-08-12 08:46:43 +00:00 • committed by Jonathan Wakely
parent 825d7d648c
commit e885821fff
2 changed files with 13 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

7
libstdc++-v3/ChangeLog
View file

@ -1,3 +1,10 @@
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
2003-08-11 Benjamin Kosnik <bkoz@redhat.com> 2003-08-11 Benjamin Kosnik <bkoz@redhat.com>
* include/bits/basic_ios.h: Remove *_iter typedefs, change num* * include/bits/basic_ios.h: Remove *_iter typedefs, change num*

11
libstdc++-v3/docs/html/ext/howto.html
View file

@ -285,20 +285,21 @@
SGI STL days. We have removed it in gcc 3.3. See next section SGI STL days. We have removed it in gcc 3.3. See next section
for the new way to get the same effect. for the new way to get the same effect.
</p> </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 <p>Starting with gcc 3.3, if you want to globally disable memory
caching within the library for the default allocator (i.e. caching within the library for the default allocator (i.e.
the one you get for all library objects when you do not specify 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 with any value) into your environment before running the
program. You will obtain a similar effect without having to program. You will obtain a similar effect without having to
recompile your entire program and the entire library (the new recompile your entire program and the entire library (the new
operator in gcc is a light wrapper around malloc). If your 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 it likely means that you linked against objects built against
the older library. Code to support this extension is fully the older library. Code to support this extension is fully
compatible with 3.2 code if GLIBCPP_FORCE_NEW is not in the compatible with 3.2 code if GLIBCXX_FORCE_NEW is not in the
environment. environment. Prior to GCC 3.4, this variable was spelt
GLIBCPP_FORCE_NEW.
</p> </p>
<h3>Writing your own allocators</h3> <h3>Writing your own allocators</h3>
<p>Depending on your application (a specific program, a generic library, <p>Depending on your application (a specific program, a generic library,