"Bohdan" <[EMAIL PROTECTED]> wrote
>
> All boost::pool library is about allocation of small objects
> of the same size. I'm just curious how malloc can be
> accelerated if it handles different size allocations?
> May be boost will also need something like that.
> I understand that "char" can be tre
> -Original Message-
> From: Bohdan [mailto:warever@;mail.i.com.ua]
>
> <[EMAIL PROTECTED]> wrote in message
> news:22602E7E3B92D411969B0090273CC28B1D235F@;cecexchange.cec.je
> rviswebb.com...
> > As John pointed out, you're not going to see much benefit (if any) when
the
> > standard libr
<[EMAIL PROTECTED]> wrote in message
news:22602E7E3B92D411969B0090273CC28B1D235F@;cecexchange.cec.jerviswebb.com...
> As John pointed out, you're not going to see much benefit (if any) when the
> standard library contains a pool allocator itself (as does STLport and
> glibc).
All boost::pool libra
"John Maddock" <[EMAIL PROTECTED]> wrote in message
news:00f801c288b3$70f93920$605787d9@;1016031671...
> C++ Builder 6 uses STLport, which has a pool based allocator by default
> anyway...
I'm using C++ builder 5.0, which uses RW STL.
regards,
bohdan
_
