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=3.8 required=5.0 tests=BAYES_00,INVALID_MSGID, RATWARE_MS_HASH,RATWARE_OUTLOOK_NONAME autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ed6a891101ff4e06 X-Google-Attributes: gid103376,public From: "Bob Fletcher" Subject: Re: Freeing Pointers to classwide types Date: 1998/09/25 Message-ID: <01bde866$1be8ed00$5330ea9e@UKP014459.logica.co.uk>#1/1 X-Deja-AN: 394675675 References: <1ftmFTC69GA.191@samson.airnet.net> <360b26a1.41575272@SantaClara01.news.InterNex.Net> Organization: Logica UK Limited Newsgroups: comp.lang.ada Date: 1998-09-25T00:00:00+00:00 List-Id: Tom Moran wrote in article <360b26a1.41575272@SantaClara01.news.InterNex.Net>... > Of course one > would also hope > procedure something(....) is > type ptr is access .... > p : ptr: := new ... > ... > end something > to free the memory pointed to by 'p' when it leaves procedure > something. Really? Isn't the object that is created by the 'new' keyword similar in nature to a C++ 'heap' variable, in that although the pointer may go out of scope the object will not, and needs to be explicitly destroyed? -- Bob Fletcher Consultant, Logica UK #ifndef STANDARD_DISCLAIMER_H #define STANDARD_DISCLAIMER_H { // All opinions are my own, not my employers' } #endif