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,d121cc76e012fcca X-Google-Attributes: gid103376,public From: "Steve Doiel" Subject: Re: Library Level Question Date: 1999/02/16 Message-ID: <36ca3e87.0@news.pacifier.com>#1/1 X-Deja-AN: 445637445 References: <36c853cb.0@news.pacifier.com> <36c8d860.0@news.pacifier.com> <7aam8p$g7i@drn.newsguy.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Trace: 16 Feb 1999 19:59:03 PST, 216.65.138.220 Newsgroups: comp.lang.ada Date: 1999-02-16T00:00:00+00:00 List-Id: >>If I understand correctly, your example is in slight error in that package >>Diagram is at the library level, but its contents are not. >> > >huh? > >package diagram is NOT at library level. That is the whole point of >the example! > Back to the example, with a couple of procedures added: package Book is procedure Read is begin end Read; package Diagram is procedure Draw ... ... end Diagram; ... end Book; In this example the procedure "Read" is a the library level and the procedure "Draw" is not at the library level. Any declarations between "procedure Read" and "end Read" are not at the library level (only the interface is at the library level). Similarly anything between "package Diagram" and "end Diagram" is not at the library level, but the interface is at the library level. Suppose the diagram package were made a generic. I could create an instance of the generic since it is at the library level, but I could not see inside the generic. If I'm off base, let me know. SteveD