Re: C++ Memory Management Innovation: GC Allocator

{ Please do not quote extraneous material, such as the clc++m banner.
  Please also note that top posting is discouraged in this group.

  Please help the moderators from having to repeat the same notes. -mod }

The difference between StreamFlow and ScopeAlloc (or AutoFreeAlloc)
are:

1. StreamFlow uses thread local storage, while ScopeAlloc doesn't.
2. StreamFlow provides global allocation procedures, while ScopeAlloc
uses non-static allocator instances to allocate memory.
3. ScopeAlloc forbid you to deallocate memory by yourself.

GC Allocator doesn't forbid you to create in thread A and free in
thread B. But it is not recommended. However, GC Allocator forbid you
to deallocate memory manually. So, if you implement algorithms that
are related to t (that is, how many time of the algorithm spent is
unsure.), GC Allocator doesn't fit you directly.

Last, "GC Allocator" is OPTIONAL, not a MUST. I don't think it is all
of C++ memory management.

Regards,

****wei Xu

On 4ÔÂ23ÈÕ, ÉÏÎç5ʱ19·Ö, "Chris Thomasson" <cris...@[EMAIL PROTECTED]
> wrote:
>
> What's the difference between xu****wei's work and all of the allocators
out
> there that are based on per-thread heaps? Answer, xu****wei's design does
not
> allow you to pass memory between threads, and the others do. This is
MAJOR
> problem. Please explain how your going to implement message-passing? How
are
> you going to implement ANY producer/consumer patters using xu****wei's
> design? Allocators like StreamFlow and Hoard don't use any atomic
operations
> or memory barriers to allocate from a per-thread heap, yet they still
allow
> one to create in thread A and free in thread B.

{ banner removed -mod }

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