OSNews article about C++09 degenerates into C++ vs. D discussion

[Unknown W. Brackets]

My mistake, this will only work if each is addRange()'d instead of 
searched by pool.

-[Unknown]


> Yes.
> 
> std.gc.removeRange(myArray);
> 
> As far as I recall.
> 
> But, iirc you do have to do this on a full range (e.g., not a sliced 
> array but the whole allocated array.)
> 
> -[Unknown]
> 
> 
>> Mars wrote:
>>> http://www.osnews.com/comment.php?news_id=16526
>>
>> RE[2]: Not much of an update
>>  > By luzr (2.10) on 2006-11-19 19:44:17 UTC in reply to "RE: Not much of
>>  > an update"
>>  >>I second that. D is a very nice language with a clear focus. My 
>> first  >>impression was that it has the best of Java, the best of C++ 
>> and none  >>of they're major weaknesses.
>>  >
>>  >Adds one major weekness - its memory model is based on conservative 
>> GC, >which makes it unpredictable and in reality unusable for some 
>> important >applications (like cryptography or any other software that 
>> deals with >noise-like data).
>>
>> This is one thing that bothers me with the current GC. If you store 
>> data with a lot of entropy in an array (Sound, encrypted data, sensor 
>> data, etc...) you start to experience memory leaks because the GC 
>> starts to see the data as references to other objects.
>>
>> Is there a way to tell the garbage collector "don't look for 
>> references here" without using malloc and friends?
>>
>> This would be for a standard sliceable garbage collected array with 
>> any kind of data except references. Something like 
>> gc.doNotLookForReferences(myArray) would be nice.