[PATCH] Slightly better way to __USE_MALLOC

Phil Edwards phil@jaj.com
Thu Oct 17 17:42:00 GMT 2002

Very nice, gentlemen.  And as an unexpected bonus, this dovetails
nicely (I think, so far) with my plans to unify stl_alloc.h and

> !       high-speed caching memory allocator.  If you want to test
> !       or run your application without the cache, then please add
> !       GLIBCPP_FORCE_NEW to your environment before running the program.

Two notes:

1)  We should note, if you didn't do so, which versions support this
    technique.  (I think the "extensions howto" is already split up to
    do this, depending on whether this is backported for 3.2.)

2)  Please add some phrase about "the /value/ of the environment variable
    doesn't matter in version <foo>, just as long as it's present in the
    environment."  I could see the value making a difference later.

Again, most excellent work.  (I wish I'd helped.  *grin*)


I would therefore like to posit that computing's central challenge, viz. "How
not to make a mess of it," has /not/ been met.
                                                 - Edsger Dijkstra, 1930-2002

More information about the Libstdc++ mailing list