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-Thread: 103376,92748798eb3c95c4 X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news2.google.com!proxad.net!news.cs.univ-paris8.fr!newsfeed.vmunix.org!newsfeed01.sul.t-online.de!t-online.de!news.belwue.de!LF.net!news.enyo.de!not-for-mail From: Florian Weimer Newsgroups: comp.lang.ada Subject: Re: Ada has garbage collection Date: Tue, 24 Aug 2004 10:05:14 +0200 Message-ID: <87oel1j70l.fsf@deneb.enyo.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: codeneb.enyo.de 1093335108 13798 212.9.189.171 (24 Aug 2004 08:11:48 GMT) X-Complaints-To: Cancel-Lock: sha1:sHx1OaO2LtcCQi1CuXYpCSExA00= Xref: g2news1.google.com comp.lang.ada:2954 Date: 2004-08-24T10:05:14+02:00 List-Id: * Wes Groleau: > OK, we could argue semantics, but every language with > parameters/data on the call stack has garbage collection > for all those objects. That's a sure way to lose an argument with a garbage collection advocate. > Of course, some problems/data structures almost demand > pointers, but with sensible encapsulation and package > designed, controlled types provide all the GC those things need. Of course you can implement an ownership policy manually (or some simple form of garbage collection like reference counting, especially if your data structures aren't cyclic). This is a tedious task, and if you implement the wrong ownership policy, you often prevent code reuse. It's quite a bit of work to make something completely safe against misuse. Memory management errors are hard to debug.