Re: C++ Memory Management Innovation: GC Allocator

"xu****wei" <xu****weizh@[EMAIL PROTECTED]
> wrote in message 
news:8c691ff1-f4c5-48dd-a87a-23957295f5cd@[EMAIL PROTECTED]
> On 4ÔÂ22ÈÕ, ÉÏÎç10ʱ43·Ö, marlow.and...@[EMAIL PROTECTED]
 wrote:
>>
>> I took a quick look with particular interest
>> in what you have to say about scoped allocators.
>> It seems to me that there is some overlap with
>> what you are doing and the work by Pablo Halpern in
>> his N2523 submission to WG21 entitled "The Scoped Allocator
>> Model". 
>> Seehttp://www.open-std.org/JTC1/SC22/WG21/docs/papers/2008/n2523.pdf
>>
>> IMO Pablo's proposal is more thought through.
>> I recommend you take a look.
>
[...]
>> 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?
>
> ** No Multithreaded Locks **
>
> Why doesn't GC Allocator need multithreaded locks?
>
> Memory allocation = System memory block management + Memory management
> algorithm
[...]

Your using per-thread allocation, what's new about that? Anyway, I don't 
think I can use your design in any of my programs. Most are based on 
message-passing or reader-writer patterns which require the ability to 
allocate in one thread and free in another. This is a must. AFAICT, your
not 
addressing this aspect, therefore, I cannot use your work. 



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