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=0.7 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD, FREEMAIL_FROM,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 Path: backlog1.nntp.ams3.giganews.com!backlog1.nntp.ams2.giganews.com!backlog1.nntp.ams.giganews.com!border3.nntp.ams.giganews.com!border1.nntp.ams.giganews.com!nntp.giganews.com!newsfeed.tele2net.at!feeder.erje.net!eu.feeder.erje.net!feeds.news.ox.ac.uk!news.ox.ac.uk!zen.net.uk!hamilton.zen.co.uk!reader01.nrc01.news.zen.net.uk.POSTED!not-for-mail From: Phil Thornley Newsgroups: comp.lang.ada Subject: Re: Q: SPARK: visibility of private child in parent's body Date: Sun, 25 Aug 2013 20:35:59 +0100 Message-ID: References: <521a0149$0$9514$9b4e6d93@newsspool1.arcor-online.net> Reply-To: phil.jpthornley@gmail.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit User-Agent: MicroPlanet-Gravity/3.0.4 Organization: Zen Internet NNTP-Posting-Host: d89f5ddb.news.zen.co.uk X-Trace: DXC=Jg0[IXP1QIRTQOo@SCFGj^a0UP_O8AJo\=dR0\ckLKGPWeZ<[7LZNRVh3K<`==d:G^UhLi?]0KG=[8a@D]61DD8X@__W9[:iOAV X-Complaints-To: abuse@zen.co.uk Xref: number.nntp.dca.giganews.com comp.lang.ada:183131 Date: 2013-08-25T20:35:59+01:00 List-Id: 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