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,495ea95198cfe20f X-Google-Attributes: gid103376,public From: jsa@organon.com (Jon S Anthony) Subject: Re: Package names & visibility Date: 1996/07/05 Message-ID: #1/1 X-Deja-AN: 163912278 sender: news@organon.com (news) references: organization: Organon Motives, Inc. newsgroups: comp.lang.ada Date: 1996-07-05T00:00:00+00:00 List-Id: In article woodruff@calaveras.llnl.gov (John Woodruff B481) writes: > with Motor ; > package Info_About.Motor is > A : Motor.Yes_It_Is ; > -- (I'm not *really* going to declare a visible object!) > end ; > > My thinking was that Info_about.Motor will hold some data values (which > are of types defined by the Motor package). > > But I can't seem to refer to the type Yes_It_Is! My friend Gnat tells me > info_about-motor.ads:3:13: "Yes_It_Is" not declared in "Motor" > > This message clearly states that the visibility of info_about.motor is > hiding the package Motor where the type is declared. > > Please suggest a way that I can refer to the identifiers that are > declared in Motor from inside the package Info_about.motor. Thx! Maybe this should (is?) in the FAQ. Two ways: 1. Everything is rooted at Standard, so refer to the "outside" Motor as Standard.Motor: A : Standard.Motor.Yes_It_Is; 2. Provide a renaming for "outside" Motor before entering scope of child Motor. Maybe in Info_About or at library level. Option #1 is really the preferred IMO. /Jon -- Jon Anthony Organon Motives, Inc. 1 Williston Road, Suite 4 Belmont, MA 02178 617.484.3383 jsa@organon.com