[Patch] Saner ;) per_type defaults

[Paolo Carlini]

Hi everyone, hi Benjamin,

seriously, some time ago I noticed the below problem, easy to reproduce:
if we keep the size of the chunk fixed and scale only max_bytes, it can
easily happen that the allocator decide to take charge of the allocation
(i.e., not passed down to new) but cannot really fulfill it. The easiest
fix seems to me just scaling with sizeof the size of the chunk too (as
default, of course, other settings may be more suited in specific
circumstances).

Took also the occasion to wrap a bit ;)

Ok with you?

Tested x86-linux, also checked with the default allocator changed to
per_type.

Paolo.

////////////////
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: CL_saner
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20050126/3b7884c8/attachment.ksh>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch_saner
URL: <http://gcc.gnu.org/pipermail/libstdc++/attachments/20050126/3b7884c8/attachment-0001.ksh>