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,start X-Google-Attributes: gid103376,public From: "Steve Doiel" Subject: Library Level Question Date: 1999/02/15 Message-ID: <36c853cb.0@news.pacifier.com>#1/1 X-Deja-AN: 444630271 X-Trace: 15 Feb 1999 09:05:15 PST, 216.65.137.77 Newsgroups: comp.lang.ada X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Date: 1999-02-15T00:00:00+00:00 List-Id: What exactly is meant by Library Level Section 13.10.2 of the LRM gives the following description: (22) The accessibility level of all library units is called the library level; a library-level declaration or entity is one whose accessibility level is the library level. Does this mean unit specifications? Implementations? Either? I'm obviously not a language lawyer, but am often able to figure things out from the LRM. this has been an exception. My observation has been that when I try to take the address ('access) of a function or procedure that is defined within my main procedure, I get a message about the wrong library level. But if I take the address of a function or procedure defined inside a package spec or body, the compiler is happy. Please respond in layman terms (if possible). SteveD