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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Deallocating an object twice Date: Mon, 28 Jul 2014 17:15:35 +0100 Organization: A noiseless patient Spider Message-ID: References: <85bnsarfad.fsf@stephe-leake.org> <8538dlqzu8.fsf@stephe-leake.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: mx05.eternal-september.org; posting-host="f008dfb2a20cab2735f9b6a28e892fd7"; logging-data="28859"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19bxTam+WuSnoRiSffUqf13mlbNIKFoBK0=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3 (darwin) Cancel-Lock: sha1:5PRzv2Xt1szuv5woTzAz9EURSMY= sha1:Vh0+kkFNYJnmI/g+LHl7xB7Kptg= Xref: news.eternal-september.org comp.lang.ada:21311 Date: 2014-07-28T17:15:35+01:00 List-Id: Stephen Leake writes: > Don't copy pointers! It is the copy of the pointer that is bad, not > the behavior of Unchecked_Deallocation. I don't think pointers are always bad, so long as everyone knows whose responsibility it is to do the allocation and deallocation.