Re: Object.Operation and child package

["Jeffrey R. Carter" <spam.jrcarter.not@spam.acm.org>]

pascal.malaise@gmail.com wrote:
> 
> Is it normal to reject compilation of Object.Operation notation when
> operation is in a child package:

Yes. ARM 4.1.3:

Quote : begin

9.1/2

     * A view of a subprogram whose first formal parameter is of a tagged type 
or is an access parameter whose designated type is tagged:

9.2/2

       The prefix (after any implicit dereference) shall resolve to denote an 
object or value of a specific tagged type T or class-wide type T'Class. The 
selector_name shall resolve to denote a view of a subprogram declared 
immediately within the declarative region in which an ancestor of the type T is 
declared. The first formal parameter of the subprogram shall be of type T, or a 
class-wide type that covers T, or an access parameter designating one of these 
types. The designator of the subprogram shall not be the same as that of a 
component of the tagged type visible at the point of the selected_component. The 
selected_component denotes a view of this subprogram that omits the first formal 
parameter. This view is called a prefixed view of the subprogram, and the prefix 
of the selected_component (after any implicit dereference) is called the prefix 
of the prefixed view.

end Quote;

(In interpreting this, it's important to remember that a tagged type T in an 
ancestor of itself: ARM 3.4.1.)

The operation declared in your child package is not declared immediately within 
the declarative region in which Typ is declared, so you cannot use 
Object.Operation notation for it.

-- 
Jeff Carter
"Sons of a silly person."
Monty Python & the Holy Grail
02