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=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.224.10.6 with SMTP id n6mr37047684qan.4.1367870705096;
 Mon, 06 May 2013 13:05:05 -0700 (PDT)
X-Received: by 10.49.109.200 with SMTP id hu8mr1715550qeb.31.1367870705065;
 Mon, 06 May 2013 13:05:05 -0700 (PDT)
Path: 
 border1.nntp.dca3.giganews.com!border3.nntp.dca.giganews.com!border1.nntp.dca.giganews.com!nntp.giganews.com!l3no2855019qak.0!news-out.google.com!y6ni0qax.0!nntp.google.com!m7no2891499qam.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Mon, 6 May 2013 13:05:04 -0700 (PDT)
In-Reply-To: <5ryqq4azptqx.1evdyl7lvwwg2$.dlg@40tude.net>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=206.53.78.59;
 posting-account=ShYTIAoAAABytvcS76ZrG9GdaV-nXYKy
NNTP-Posting-Host: 206.53.78.59
References: <143a8db3-c14b-4983-a481-4b998aea42af@googlegroups.com>
 <km1e4q$j98$1@munin.nbi.dk>
 <7a248ba5-9fbc-4326-bbb8-eec3c125d455@googlegroups.com>
 <5ryqq4azptqx.1evdyl7lvwwg2$.dlg@40tude.net>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <56ae2d39-e3a1-4d3e-b9a1-8d4aa435ad8a@googlegroups.com>
Subject: Re: Accessing finalized values
From: sbelmont700@gmail.com
Injection-Date: Mon, 06 May 2013 20:05:05 +0000
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Original-Bytes: 1820
Xref: number.nntp.dca.giganews.com comp.lang.ada:181459
Date: 2013-05-06T13:05:04-07:00
List-Id: <comp.lang.ada>

On Monday, May 6, 2013 5:52:18 AM UTC-4, Dmitry A. Kazakov wrote:
>=20
> Finalize is a hack.
>=20

The more I delve into controlled types, the more I'm starting to come to th=
at conclusion.  This means, in general, that every controlled type must tra=
ck the state of its finalization and conditionally release resources (to si=
de-step the non-limited multiple finalization issue), as well as add a 'not=
 Is_Finalized' precondition to every single operation (to avoid access afte=
r finalization)?  Yuck.

-sb