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: Tucker Taft Subject: Re: Library Level Question Date: 1999/02/23 Message-ID: <36D2EC44.CDB22A0D@averstar.com>#1/1 X-Deja-AN: 447570645 Content-Transfer-Encoding: 7bit Sender: news@inmet.camb.inmet.com (USENET news) X-Nntp-Posting-Host: houdini.burl.averstar.com References: <36c853cb.0@news.pacifier.com> <36c8d860.0@news.pacifier.com> <7aam8p$g7i@drn.newsguy.com> <36ca3e87.0@news.pacifier.com> Content-Type: text/plain; charset=us-ascii Organization: AverStar (formerly Intermetrics) Burlington, MA USA Mime-Version: 1.0 Newsgroups: comp.lang.ada Date: 1999-02-23T00:00:00+00:00 List-Id: There are several mistaken replies here. Library unit packages are at library level, as are all their contents, both spec and body. You only "leave" library level by going inside a subprogram, a type, a generic, etc. You *stay* at the same level when you enter a sub-package. Accessibility level relates to "lifetime." The contents of a package live as long as the package itself. On the other hand, the declarations inside a subprogram last only as long as any given *call* on the subprogram, whereas the subprogram itself lasts as long as the enclosing scope lives. -- -Tucker Taft stt@averstar.com http://www.averstar.com/~stt/ Technical Director, Distributed IT Solutions (www.averstar.com/tools) AverStar (formerly Intermetrics, Inc.) Burlington, MA USA