Re: C++ Memory Management Innovation: GC Allocator

<marlow.andrew@[EMAIL PROTECTED]
> wrote in message
news:a0074c8e-e576-4efb-bb9e-0cd97ae3fec6@[EMAIL PROTECTED]
> On 21 Apr, 19:13, xu****wei <xu****we...@[EMAIL PROTECTED]
> wrote:
>> To obtain a copy of this paper in pdf format click here (http://
>> xu****wei.com/local--files/gc-allocator/GCAllocator.pdf
>
[...]
> One final point, it seems to me that there is a need
> to bear thread safety in mind. You just say "it's not
> needed". Can you explain why please?

I just want to know if I can use this proposal to efficiently allocate in
one thread and free in another. As for the GC aspect, well, that's fine as
long as there are no mandatory requirements. I personally would think
about
dropping C++ _if_ it "forced" me to use a GC. Even if the GC was
transparent, I need to be able to manually manage memory most of the time.
I
don't want a GC running under my nose, so-to-speak... IMVHO, that would go
against the low-level nature of C++. I want to be able to use C++ to
create
state-of-the-art allocators and garbage collectors... OS kernels, device
drivers and other low-level applications... Its the low-level nature of
C++
that's particularly attractive... This is only my personal take on the
matter... Indeed.


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