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,FREEMAIL_FROM autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,31f4d595a05ede7d X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news1.google.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: "Alex R. Mosteo" Newsgroups: comp.lang.ada Subject: Re: Abnormal objects - how they can become normal again? Date: Thu, 22 Dec 2005 11:50:37 +0100 Message-ID: <43AA84FD.7050601@mailinator.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: individual.net 37wSTWGRk+6UaRMCKKPwjQt0v4AmLJbZAktyRc8ejOEs3L2mw= User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051013) X-Accept-Language: en-us, en In-Reply-To: Xref: g2news1.google.com comp.lang.ada:6962 Date: 2005-12-22T11:50:37+01:00 List-Id: Robert A Duff wrote: > (snip) > > Another way to deal with abnormal (possibly controlled) objects is to > add a level of indirection. I believe you can Unchecked_Deallocate an > abnormal object (not sure). Assignment of access values does not > involve finalization. So when you have a possibly-abnormal object, you > could simply throw it away and create a new one. I guess you can indeed free abnormal controlled objects, but this will trigger finalization, and I think the OP wanted to avoid this (as this happens too when overwriting the abnormal object during asignation).