When is it time for a 1.0 feature freeze?

Stewart Gordon smjg_1998 at yahoo.com
Sat Sep 2 17:45:25 PDT 2006


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.

-- 
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCS/M d- s:-@ C++@ a->--- UB@ P+ L E@ W++@ N+++ o K-@ w++@ O? M V? PS- 
PE- Y? PGP- t- 5? X? R b DI? D G e++++ h-- r-- !y
------END GEEK CODE BLOCK------

My e-mail is valid but not my primary mailbox.  Please keep replies on 
the 'group where everyone may benefit.



More information about the Digitalmars-d mailing list