From: mheaney@ni.net (Matthew Heaney)
Subject: Re: differentiating finalization causes
Date: 1997/11/01
Date: 1997-11-01T00:00:00+00:00 [thread overview]
Message-ID: <mheaney-ya023680000111971740030001@news.ni.net> (raw)
In-Reply-To: 01bce4a2$b0ad17e0$020c6dce@my-pc.neosoft.com
In article <01bce4a2$b0ad17e0$020c6dce@my-pc.neosoft.com>, "Pat Rogers"
<progers@acm.org> wrote:
>For a type descended from Controlled, I need to be able to differentiate
>finalization due to object destruction from finalization due to assignment
>("value destruction", if you will).
This issue pops up from time to time, but something about it strikes me as
odd. Can you explain more about why you need to differentiate between the
two cases?
What about making the type limited? That would make the issue disappear,
because no assignment is allowed. You could even export a Copy operation
if you need to.
--------------------------------------------------------------------
Matthew Heaney
Software Development Consultant
<mailto:matthew_heaney@acm.org>
(818) 985-1271
prev parent reply other threads:[~1997-11-01 0:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-29 0:00 differentiating finalization causes Pat Rogers
1997-11-01 0:00 ` Matthew Heaney [this message]
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox