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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,5df086f5b450f5c4 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2001-05-03 09:25:59 PST Path: newsfeed.google.com!newsfeed.stanford.edu!feed.textport.net!hammer.uoregon.edu!skates!not-for-mail From: Stephen Leake Newsgroups: comp.lang.ada Subject: Re: Ada95 BNF Date: 03 May 2001 12:24:01 -0400 Organization: NASA Goddard Space Flight Center Message-ID: References: <3af1541f$1@pull.gecm.com> NNTP-Posting-Host: anarres.gsfc.nasa.gov Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: skates.gsfc.nasa.gov 988907956 15439 128.183.220.71 (3 May 2001 16:39:16 GMT) X-Complaints-To: dscoggin@cne-odin.gsfc.nasa.gov NNTP-Posting-Date: 3 May 2001 16:39:16 GMT User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.6 Xref: newsfeed.google.com comp.lang.ada:7121 Date: 2001-05-03T16:39:16+00:00 List-Id: "Martin Dowie" writes: > Looking through the BNF on AdaPower.com and the LRM that comes with > adaguide, I noticed > that package_unit_name is defined as a name, which in turn can be all sorts > of things, > including a 'name', which in turn can be lots of things - including a type > conversion?! Just because something is allowed by the syntax, doesn't mean it is allowed by the language. See the appropriate LRM section for the real rules. In this case, 'parent_unit_name' is first discussed in 10.1.1, which doesn't actually help that much. > Shouldn't package_unit_name be defined as an Identifier?.. A 'parent_unit_name' can be of the form ancestor.parent, which is not an "identifier". So "name" is appropriate. -- -- Stephe