When is it time for a 1.0 feature freeze?

[Derek Parnell]

On Sun, 03 Sep 2006 01:45:25 +0100, Stewart Gordon wrote:

> Walter Bright wrote:
> <snip>
>> 1) Few programmers realize that C/C++'s malloc/free/new/delete *never* 
>> (and I emphasize NEVER) return memory to the operating system. All 
>> free/delete do is return memory to the memory pool managed by the 
>> runtime library, not the operating system. In order to actually return 
>> memory to the operating system, one has to write their own memory 
>> management code, which is a significant (and necessarily non-portable) 
>> effort. Hardly anyone does that.
> <snip>
> 
> Never?  I can't believe you've tried every implementation out there, 
> including your own, and found the same.
> 
> Or does the spec forbid free or delete to return memory to the OS?  I 
> can't for the life of me see why this would be.
> 
> Stewart.

>From memory, I believe the Manx-C for the Amiga used to return memory to
the operating system.

-- 
Derek Parnell
Melbourne, Australia
"Down with mediocrity!"