Boost logo

Boost :

From: Lance.Diduck_at_[hidden]
Date: 2008-04-25 09:55:34

I think the best thing to do is package up your allocators, and present
them for a boost peer review. I have a strong interest in seeing more
specialty allocators in C++ so I will be glad to help, and even donate
some of my own, as I am sure others would to. Even bringing up
HeapLayers to boost quality standards would be worthwhile.

There are lots of ways of getting C++ classes and libraries to use
specialty allocators, but hardly any allocators nor docs on why you
might want to. Nor ways to actually write an allocator that could be
used in a library. For some reason people attach a lot of unwarranted
hype to GC and allocators -- esp to try and sell new "revolutionary"
programming models. Sigh. All we really need is a library of allocators
and ways to apply them without getting in trouble, and keep them out of
sight when I don't care. That is all the innovation I want.

-----Original Message-----
From: boost-bounces_at_[hidden]
[mailto:boost-bounces_at_[hidden]] On Behalf Of shiwei xu
Sent: Friday, April 25, 2008 5:01 AM
To: boost_at_[hidden]
Subject: Re: [boost] C++ Memory Management Innovation: GC Allocator

Hello all,

I add a new class: TlsBlockPool. And now you can define a ScopeAlloc
instance without given parameters:

  ScopeAlloc alloc;

It is same as:

  ScopeAlloc alloc(TlsBlockPool::instance());

class TlsBlockPool
  TlsBlockPool() { init(); }
  ~TlsBlockPool() { term(); }
  static void init();
  static void term();
  static BlockPool& instance();
Note: TlsBlockPool::init() can be called more than once. each call to
TlsBlockPool::init() must be balanced by a corresponding call to
On Tue, Apr 22, 2008 at 8:58 PM, shiwei xu <xushiweizh_at_[hidden]> wrote:
> Most of the C++ programmers do not benefit from "Garbage Collection"
> technique (GC). They are sick of deleting objects but have to do this.
> There are some C/C++ memory GC implementations, but they are complex 
> and are not widely used.
> I am going to introduce a new memory management technique named "GC 
> Allocator". "GC Allocator" isn't an implementation, but a concept.
> Now, we have two "GC Allocator" implementations, named "AutoFreeAlloc"
> and "ScopeAlloc".
> This article consists of three parts:
>    1. What is GC Allocator?
>    2. GC Allocator implementations: ScopeAlloc and AutoFreeAlloc
>    3. Applications based on GC Allocator  For more information, see 
> To obtain a copy of this paper in pdf format click 
> here<>(or
from google code <>).
Unsubscribe & other changes:
Visit our website at
This message contains confidential information and is intended only 
for the individual named.  If you are not the named addressee you 
should not disseminate, distribute or copy this e-mail.  Please 
notify the sender immediately by e-mail if you have received this 
e-mail by mistake and delete this e-mail from your system.
E-mails are not encrypted and cannot be guaranteed to be secure or 
error-free as information could be intercepted, corrupted, lost, 
destroyed, arrive late or incomplete, or contain viruses.  The sender 
therefore does not accept liability for any errors or omissions in the 
contents of this message which arise as a result of e-mail transmission.  
If verification is required please request a hard-copy version.  This 
message is provided for informational purposes and should not be 
construed as a solicitation or offer to buy or sell any securities 
or related financial instruments.

Boost list run by bdawes at, gregod at, cpdaniel at, john at