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,2d56530d3025e324
X-Google-Attributes: gid103376,public
From: "David C. Hoos, Sr." <david.c.hoos.sr@ada95.com>
Subject: Re: Program error from assignment??
Date: 1998/07/22
Message-ID: <QmKA8wYt9GA.205@samson.airnet.net>#1/1
X-Deja-AN: 373888633
References: <6p3070$bvn$1@nnrp1.dejanews.com>
 <6p4skk$j73$1@nnrp1.dejanews.com>
Newsgroups: comp.lang.ada
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Date: 1998-07-22T00:00:00+00:00
List-Id: <comp.lang.ada>


dennison@telepath.com wrote in message <6p4skk$j73$1@nnrp1.dejanews.com>...
<snip>
>
>So now this turns into an "accessability level" question. The object that
is
>pointed to is declared in the declaration section of the main routine. It
>exists the entire program. I don't understand the exact rules on
accessability
>levels, but in my book I should *never* fail an accessability check with
this
>object. The access type is declared in a package spec.
>
The probelem with that reasoning is that there is nothing which
distibguishes your "main program" from any other library procedure which
could be called from another "ain" progeam.  Thus, the lifetime of the
object in question is only diring the execution of the subprogram.in which
it is declared.

Hope this helps,

David C. Hoos, Sr.