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: tmoran@bix.com (Tom Moran)
Subject: Re: Unreferenced lock variables
Date: 1999/04/16
Message-ID: <3717869e.7448255@news.pacbell.net>#1/1
X-Deja-AN: 467237332
References: <x7v4smnszvu.fsf@pogner.moho> <7ero31$n46$1@nnrp1.dejanews.com>
 <x7vk8viqsla.fsf@pogner.moho> <7esrmv$k1n$1@nnrp1.dejanews.com>
 <3713b417.22324981@news.pacbell.net> <7f57g5$rpq$1@nnrp1.dejanews.com>
 <371658a7.19974365@news.pacbell.net> <7f6ei7$tvl$1@nnrp1.dejanews.com>
X-Complaints-To: abuse@pacbell.net
X-Trace: typhoon-sf.pbi.net 924289005 206.170.24.12 (Fri,
 16 Apr 1999 11:56:45 PDT)
Organization: SBC Internet Services
NNTP-Posting-Date: Fri, 16 Apr 1999 11:56:45 PDT
Newsgroups: comp.lang.ada
Date: 1999-04-16T00:00:00+00:00
List-Id: <comp.lang.ada>

I found AI-00147, which as far as I can see gives no significant
arguments *for* eliminating in the non-limited case, except "doing
Initialization/Finalization is expensive".  It seems to that either
the programmer intended the object to be declared, even though he
doesn't use it, or it was a mistake on his part and a warning should
be generated (as for unused Integer, Boolean, and other non-controlled
types).  So possibly such a warning in the non-limited case would be
reasonable, but simply assuming the programmer did not really intend
to declare the controlled object, is hubris.
  Or is there another AI that I missed?