Re: C++ Memory Management Innovation: GC Allocator

"xu****wei" <xu****weizh@[EMAIL PROTECTED]
> wrote in message
news:6b243176-271e-44f6-ad16-66df03ab1284@[EMAIL PROTECTED]
> In fact, "GC Allocator" is NOT "GC".
>
> "GC Allocator" focus:
>
> 1. It is a better "Smart Pointer".
> 2. Deleting objects manually is no need if you use "GC Allocator".
> 3. Use non-static allocator instances to allocate memory instead of
> global new/delete procedures. Then multithreads locks are OPTIONAL and
> you can use explicit locks if you need.

Why not just use a thread-safe allocator based on per-thread heaps? I get
all the benefits of using zero synchronization for local allocations and
deallocations... The only time any sync is needed is when I do a remote
deallocation. Read here for more information:

http://people.cs.vt.edu/~scschnei/papers/ismm06.pdf

> You can consider "GC Allocator" as a "Smart Pointer" or a "Allocator",
> but It isn't a "GC".
[...]

-- 
      [ See http://www.gotw.ca/resources/clcm.htm
for info about ]
      [ comp.lang.c++.moderated.    First time posters: Do this! ]