Re: Q: SPARK: visibility of private child in parent's body

[Phil Thornley <phil.jpthornley@gmail.com>]

In article <521a0149$0$9514$9b4e6d93@newsspool1.arcor-online.net>, 
rm.dash-bauhaus@futureapps.de says...
> 
> Hi,
> 
> a small hierarchy of packages has the body of parent P refer
> to entities of a private child package P.C.  According to
> Barnes (1997), this is possible. (I have placed supporting
> quotes before the body of P below.)
> 
> I'm hitting a wall.
> 
> Examiner does not accept the packages, warning that C of P.C
> is "either undeclared or not visible at this point".
> (There is no --# inherit for P.C, as none is required.)
> The Examiner then continues diagnosing semantic errors.
> 
> When I rearrange the source by embedding package P.C into the
> body of P instead of making it a private child package, then
> everything seems fine.
> 
> What am I doing wrong?
> 
> Can I at all refer to private packages in the parent's body
> when using somewhat recent editions of SPARK (2011 and 2012)?
> 
> 

This code works OK for me (with the "P." prefixes removed from within 
the body of P) with both the last standalone SPARK (2012) and the HiLite 
version (downloaded 2013-06-07).

Assuming you are using separate files for each unit, the next place I 
would look would be the index file. Does this identify the files that 
you think it does, and does it contain the private child announcement 
for P.C:
   P components are P.C

Cheers,

Phil