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.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,7f1e0b399cd01cb0
X-Google-Attributes: gid103376,public
From: Robert Dewar <robert_dewar@my-dejanews.com>
Subject: Re: Unreferenced lock variables
Date: 1999/04/13
Message-ID: <7eujaa$53c$1@nnrp1.dejanews.com>#1/1
X-Deja-AN: 465749334
References: <x7v4smnszvu.fsf@pogner.moho> <7ero31$n46$1@nnrp1.dejanews.com>
 <x7vk8viqsla.fsf@pogner.moho> <7esrmv$k1n$1@nnrp1.dejanews.com>
 <7eta1t$pp0$2@wanadoo.fr>
X-Http-Proxy: 1.0 x3.dejanews.com:80 (Squid/1.1.22) for client 205.232.38.14
Organization: Deja News - The Leader in Internet Discussion
X-Article-Creation-Date: Tue Apr 13 05:05:18 1999 GMT
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.04 [en] (OS/2; I)
Date: 1999-04-13T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <7eta1t$pp0$2@wanadoo.fr>,
  "Jean-Pierre Rosen" <rosen.adalog@wanadoo.fr> wrote:
> Only for non-limited controlled types. If you don't use
> the variable, make the type limited. It makes no
> difference, and the AI ensures that
> Initialization/Finalization is NOT optimized away.

Note that a quite natural style is to declare such a
variable with an initialization expression that does
something, and that will lead you naturally to a
non-limited type, which is the case that can cause
you trouble, but perhaps not immediately if your
compiler feels that it should NOT optimize this away.

I hope at least that compilers that perform this
unwise optimization will warn users that they are
doing it.

Warning: I have removed the Initialization/Finalization
calls for the object "Critical_Lock_Do_Not_Remove".

Or some such message ....

-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/       Search, Read, Discuss, or Start Your Own