This is the mail archive of the
mailing list for the libstdc++ project.
Re: Circumventing __USE_MALLOC and templatized containers
- From: Jason Merrill <jason at redhat dot com>
- To: Wolfgang Bangerth <wolfgang dot bangerth at iwr dot uni-heidelberg dot de>
- Cc: Carlo Wood <carlo at alinoe dot com>, libstdc++ at gcc dot gnu dot org
- Date: Tue, 27 Nov 2001 10:36:55 +0000
- Subject: Re: Circumventing __USE_MALLOC and templatized containers
- References: <Pine.SOL.4.10.10111261816320.18931-100000@eros>
>>>>> "Wolfgang" == Wolfgang Bangerth <firstname.lastname@example.org> writes:
> That's my opinion as well. I am led to think that this wholesale
> replacement of one allocator by another is not what was intended.
> In my view, selecting between malloc-based or other allocators should be
> possible either by a mechanism like __USE_MALLOC, or, as I understand the
> ABI concerns that were raised, by a special flag that is set once per
> program execution.
AFAIK, the problem is 'string'. Every plain function in the rest of the
library that currently refers to string ought to be a template <class