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: dennison@telepath.com
Subject: Re: Program error from assignment??
Date: 1998/07/22
Message-ID: <6p4skk$j73$1@nnrp1.dejanews.com>#1/1
X-Deja-AN: 373835674
References: <6p3070$bvn$1@nnrp1.dejanews.com>
Organization: Deja News - The Leader in Internet Discussion
X-Article-Creation-Date: Wed Jul 22 14:23:17 1998 GMT
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.0 (compatible; MSIE 4.0; Windows NT; Gateway2000)
Date: 1998-07-22T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <6p3070$bvn$1@nnrp1.dejanews.com>,
  dennison@telepath.com wrote:
> OK. I give up.
>
> I have the following code:
.
.
.
> The problem is that I'm getting a Program_Error on the second assignment at
> runtime. What could cause that?

OK. Since everyone seems to be completely speechless :-), here's what I've
found out so far:

Program_Error can happen on this assignment when the accessability level of
the source pointer's object is deeper than that of the target object's type.
That's so I can't keep around a pointer to an object after it goes away. Fair
enough.

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.

T.E.D.

-----== Posted via Deja News, The Leader in Internet Discussion ==-----
http://www.dejanews.com/rg_mkgrp.xp   Create Your Own Free Member Forum