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.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,13d6cd0af0d0d769 X-Google-Attributes: gid103376,public From: Theodore Dennison Subject: Re: Does memory leak? Date: 1995/03/30 Message-ID: <3lec74$7n4@theopolis.orl.mmc.com>#1/1 X-Deja-AN: 100540658 references: <3kopao$ekg@nef.ens.fr> <3kql6c$1b3@porte-de-st-ouen.ics.uci.edu> <3kuba0$8kd@gnat.cs.nyu.edu> <3l6gf6$h05@theopolis.orl.mmc.com> content-type: text/plain; charset=iso-8859-1 organization: IPL InterNetNews site x-url: news:milodD67p8t.5xK@netcom.com mime-version: 1.0 newsgroups: comp.lang.ada Date: 1995-03-30T00:00:00+00:00 List-Id: John DiCamillo writes: > Huh? Haven't you ever worked with a garbage-collected language? > Languages like Smalltalk allow you to allocate stuff all day, > and they don't even have a deallocate operation; the run-time > system figures out when the program is done with a piece of storage > and deallocates it for you. > Unfortunately, I never had a working copy of Smalltalk to learn from. I have used Lisp, but as I remember, Lisp is different. Lisp doesn't really have an "allocate" call. Lisp varibles are more like Ada variables, so it is natural to let the compiler worry about managing them. The point is, if a language provides "allocate" and "deallocate" functions, you should "deallocate" what you "allocate". T.E.D.