Re: C++ Memory Management Innovation: GC Allocator

xu****wei wrote:
> { 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.

I have to admit that I find it hard to understand why we would want to
introduce this kind of GC into C++. GC is of greatest benefit in MT
code, using it in single-threaded code just leads (IMHO) to lazy
programming which will bite (severely) when that same code gets re-used
in an MT context.

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