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!Hx95GBhnJb0Xc8StPhH8AA.user.46.165.242.91.POSTED!not-for-mail From: "Dmitry A. Kazakov" Newsgroups: comp.lang.ada Subject: Re: Custom Storage Pool questions Date: Sat, 18 Sep 2021 18:19:23 +0200 Organization: Aioe.org NNTP Server Message-ID: References: <1d2551f4-8189-44ec-a54d-4a56a672bedcn@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: gioia.aioe.org; logging-data="64861"; posting-host="Hx95GBhnJb0Xc8StPhH8AA.user.gioia.aioe.org"; mail-complaints-to="abuse@aioe.org"; User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 X-Notice: Filtered by postfilter v. 0.9.2 Content-Language: en-US Xref: reader02.eternal-september.org comp.lang.ada:62776 List-Id: On 2021-09-18 17:59, Niklas Holsti wrote: > So you want a way to specify that for a given access type, although the > accessed object type has a Finalize operation or needs finalization, the > objects left over in the (at least conceptually) associated collection > should _not_ be finalized when the scope of the access type is left? Exactly, especially because these objects are not deallocated, as you say they are left over. If they wanted GC they should do that. If they do not, then they should keep their hands off the objects maintained by the programmer. > To me it seems a risky think to do, subverting the normal semantics of > initialization and finalization. Quite the opposite, it is the collection rule that subverts semantics because objects are not freed, yet mangled. -- Regards, Dmitry A. Kazakov http://www.dmitry-kazakov.de