Re: C++ Memory Management Innovation: GC Allocator

On Apr 23, 5:22 am, xu****wei <xu****we...@[EMAIL PROTECTED]
> wrote:
> 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".

I found it difficult to justify your statement.  How do you deallocate
objects, really?  You did not explain well in the PDF, and a glance at
the code indicated that you simply do *not* deallocate objects in the
middle of a function.  If I did not read wrong, your work is not
suitable in most real-world cases that require a program to run for
more than a short while.

> 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.
>
> You can consider "GC Allocator" as a "Smart Pointer" or a "Allocator",
> but It isn't a "GC".

I do not think your allocators are GC at all.  And it should not
called in the current name.

Best regards,

Yongwei


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