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=0.6 required=5.0 tests=BAYES_20,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: milod@netcom.com (John DiCamillo) Subject: Re: Does memory leak? Date: 1995/03/29 Message-ID: #1/1 X-Deja-AN: 100540704 sender: milod@netcom20.netcom.com 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> organization: NETCOM On-line Communication Services (408 261-4700 guest) newsgroups: comp.lang.ada Date: 1995-03-29T00:00:00+00:00 List-Id: Theodore Dennison writes: >Perhaps I'm missing something here...what exactly is wrong with using >UNCHECKED_DEALLOCATION? >I mean, if you don't deallocate what you allocate, your program will >leak memory no matter what language it is written in. This isn't an Ada >issue, it's an issue of sloppy coding. 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. >T.E.D. -- ciao, milo ================================================================ John DiCamillo Fiery the Angels Fell milod@netcom.com Deep thunder rode around their shores