|
From: <sv...@va...> - 2005-05-12 13:46:26
|
Author: njn
Date: 2005-05-12 14:46:24 +0100 (Thu, 12 May 2005)
New Revision: 117
Modified:
trunk/docs/FAQ/faq.unexpected.html
Log:
Update FAQ about GLIBCXX_FORCE_NEW name-change.
Modified: trunk/docs/FAQ/faq.unexpected.html
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/docs/FAQ/faq.unexpected.html 2005-05-10 13:04:23 UTC (rev 116)
+++ trunk/docs/FAQ/faq.unexpected.html 2005-05-12 13:46:24 UTC (rev 117)
@@ -129,9 +129,11 @@
<li><p>With gcc 2.91, 2.95, 3.0 and 3.1, compile all source
using the STL with <tt class=3D"literal">-D__USE_MALLOC</tt>. Beware=
!
This is removed from gcc starting with version 3.3.</p></li>
-<li><p>With 3.2.2 and later, you should export the environment
+<li><p>With gcc 3.2.2 and later, you should export the environment
variable <tt class=3D"literal">GLIBCPP_FORCE_NEW</tt> before running
your program.</p></li>
+<li><p>With gcc 3.4 and later, that variable has changed name to
+ <tt class=3D"literal">GLIBCXX_FORCE_NEW</tt>.</p></li>
</ul></div>
<p>There are other ways to disable memory pooling: using the
<tt class=3D"literal">malloc_alloc</tt> template with your objects (no=
t
|