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,60338dc6410fd6ce
X-Google-Attributes: gid103376,public
From: dennison@telepath.com
Subject: Re: Safety of subprogram'unchecked_access
Date: 1998/08/27
Message-ID: <6s46kp$qse$1@nnrp1.dejanews.com>#1/1
X-Deja-AN: 385323067
References: <6s42l4$ll5$1@nnrp1.dejanews.com>
Organization: Deja News - The Leader in Internet Discussion
X-Article-Creation-Date: Thu Aug 27 17:56:41 1998 GMT
Newsgroups: comp.lang.ada
X-Http-User-Agent: Mozilla/4.05 [en] (WinNT; I)
Date: 1998-08-27T00:00:00+00:00
List-Id: <comp.lang.ada>

In article <6s42l4$ll5$1@nnrp1.dejanews.com>,
  dennison@telepath.com wrote:

> I have the following situation: a generic package's body instantiates another
> generic package. The other generic package has a routine that takes an
> "access function" parameter. The "outer" generic's body passes into that
> routine the 'access of a function declared in its body. When I try to compile
> the "outer" generic's body, I get an error on that call stating
> "LRM:3.10.2(32), If the subprogram denoted by the prefix is declared within a
> generic unit, the expected type must be declared within that same generic
> unit, Continuing"

Oddly enough, moving the instantiation of the "inner" generic from the spec to
the body of the other generic fixed the problem. Is this the expected behavior
for Ada compilers? On the surface, you wouldn't think there'd be a difference.

--
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