From: sbelmont700@gmail.com
Subject: Re: Accessing finalized values
Date: Mon, 6 May 2013 13:05:04 -0700 (PDT)
Date: 2013-05-06T13:05:04-07:00 [thread overview]
Message-ID: <56ae2d39-e3a1-4d3e-b9a1-8d4aa435ad8a@googlegroups.com> (raw)
In-Reply-To: <5ryqq4azptqx.1evdyl7lvwwg2$.dlg@40tude.net>
On Monday, May 6, 2013 5:52:18 AM UTC-4, Dmitry A. Kazakov wrote:
>
> Finalize is a hack.
>
The more I delve into controlled types, the more I'm starting to come to that conclusion. This means, in general, that every controlled type must track the state of its finalization and conditionally release resources (to side-step the non-limited multiple finalization issue), as well as add a 'not Is_Finalized' precondition to every single operation (to avoid access after finalization)? Yuck.
-sb
next prev parent reply other threads:[~2013-05-06 20:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-02 21:00 Accessing finalized values sbelmont700
2013-05-02 22:47 ` Adam Beneschan
2013-05-03 22:36 ` Randy Brukardt
2013-05-05 15:00 ` sbelmont700
2013-05-06 5:45 ` J-P. Rosen
2013-05-06 8:59 ` Stephen Leake
2013-05-06 9:52 ` Dmitry A. Kazakov
2013-05-06 20:05 ` sbelmont700 [this message]
2013-05-07 0:51 ` Randy Brukardt
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox