From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,13d6cd0af0d0d769,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1995-03-22 01:38:32 PST Path: nntp.gmd.de!news.rwth-aachen.de!news.rhrz.uni-bonn.de!RRZ.Uni-Koeln.DE!uni-duisburg.de!zib-berlin.de!news.mathworks.com!usenet.eel.ufl.edu!spool.mu.edu!uwm.edu!math.ohio-state.edu!jussieu.fr!nef.ens.fr!sands From: sands@clipper.ens.fr (Duncan Sands) Newsgroups: comp.lang.ada Subject: Does memory leak? Date: 22 Mar 1995 09:06:31 GMT Organization: Ecole Normale Superieure, PARIS, France Distribution: world Message-ID: <3kopao$ekg@nef.ens.fr> NNTP-Posting-Host: bireme.ens.fr Date: 1995-03-22T09:06:31+00:00 List-Id: Does Ada leak memory? I would like to believe it doesn't, but how does it manage not to (without having to use unchecked deallocation)? For example, if I have a pointer to a block of memory, and I set that pointer to null, in simple cases I am ready to believe that the compiler knows I'm finished with the block... but if the pointer is to a complicated self-referential structure, some sort of black magic seems needed to work out whether I'm really finished with that structure or not. Can this truly be done efficiently? You can see that I know nothing about how garbage collection works, and precious little about what Ada requires for memory management. I suspect I'm not the only one. If someone could demystify all this for me, I would be very grateful... Thanks a lot, Duncan Sands.