From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.6 Path: eternal-september.org!reader02.eternal-september.org!aioe.org!RKN7TKnHC01q0gdg6EhkbQ.user.46.165.242.75.POSTED!not-for-mail From: Simon Wright Newsgroups: comp.lang.ada Subject: Re: Custom Storage Pool questions Date: Tue, 28 Sep 2021 08:52:31 +0100 Organization: Aioe.org NNTP Server Message-ID: References: <1d2551f4-8189-44ec-a54d-4a56a672bedcn@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: gioia.aioe.org; logging-data="60879"; posting-host="RKN7TKnHC01q0gdg6EhkbQ.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org"; User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.2 (darwin) Cancel-Lock: sha1:ahtCH0kTVYvAvIyno9W1edHtth4= X-Notice: Filtered by postfilter v. 0.9.2 Xref: reader02.eternal-september.org comp.lang.ada:62853 List-Id: "Dmitry A. Kazakov" writes: > On 2021-09-28 06:31, Randy Brukardt wrote: >> "Dmitry A. Kazakov" wrote in message >> news:sibvcr$1ico$1@gioia.aioe.org... >>> On 2021-09-21 02:26, Randy Brukardt wrote: > >>>> How else would you ensure that Finalize is always called on an allocated >>>> object? >>> >>> I would not, because it is plain wrong. Finalize must be called for each >>> *deallocated* object. >> Deallocation is irrelevant. Finalization is called when objects are >> about to >> be destroyed, by any method. > > And no object may be destroyed unless deallocated. Well, if it's important that an allocated object not be destroyed, don't allocate it from a storage pool that can go out of scope!