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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,e44790cdcea9da82
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII-7-bit
Path: 
 g2news1.google.com!news2.google.com!news.maxwell.syr.edu!newsfeeds.sol.net!posts.news.twtelecom.net!nnrp2.twtelecom.net!not-for-mail
From: "Matthew Heaney" <mheaney@on2.com>
Newsgroups: comp.lang.ada
References: <41651D37.4030805@mailinator.com> <c0a9d.3371$4b.445@trndny09>
 <2skt9qF1ljjdtU1@uni-berlin.de> <4165472D.2030704@mailinator.com>
 <416573FA.4010003@mailinator.com> <87k6u2mj08.fsf@insalien.org>
 <4166538E.6090907@mailinator.com>
 <41702af7$0$91003$39cecf19@news.twtelecom.net>
 <417377F7.7050506@mailinator.com>
 <4173f0ed$0$91003$39cecf19@news.twtelecom.net>
 <417409AB.8040702@mailinator.com> <ud5zftpbi.fsf@earthlink.net>
 <sa43c0b5t15.fsf@snoopy.apana.org.au> <u8ya3thjg.fsf@earthlink.net>
 <4174BF2F.8050306@mailinator.com>
 <41752742$0$91006$39cecf19@news.twtelecom.net>
 <417536DE.3060405@mailinator.com>
Subject: Re: Problem with -gnatt
Date: Tue, 19 Oct 2004 16:03:04 -0400
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-ID: <41756ffe$0$91007$39cecf19@news.twtelecom.net>
Organization: Time-Warner Telecom
NNTP-Posting-Date: 19 Oct 2004 19:50:22 GMT
NNTP-Posting-Host: 3b86dcb9.news.twtelecom.net
X-Trace: 
 DXC=8K]n[3]`J_U;Y2[mY9c]5PC_A=>8kQj6]hHXa^^g6TZT<4TLheeGkdQdYZAA8S:<lP98B:eOVeI8[
X-Complaints-To: abuse@twtelecom.net
Xref: g2news1.google.com comp.lang.ada:5471
Date: 2004-10-19T19:50:22+00:00
List-Id: <comp.lang.ada>


"Alex R. Mosteo" <devnull@mailinator.com> wrote in message 
news:417536DE.3060405@mailinator.com...
>
> I coulnd't forget to write that as a protected procedure, since the data 
> reported is protected. If I must read it, I must do it inside the 
> protected procedure.

That just pushes back the argument.  If you can "remember" to declare the 
data inside a protected object, then surely you can "remember" to guard it 
with a semaphore.


> If I unprotect that collection and start using semaphores, nobody will 
> warn me when I forget that a lock is to be honored.

Who is "me"?  The data in question is inside a package body, and the only 
way to manipulate that data is to use the operations provided by the 
package.  So clearly a client of the package cannot forget to "honor a 
lock," since he sees neither the data nor the semaphore.