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.1 required=5.0 tests=BAYES_40,INVALID_DATE autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,9697af769c7c74cc X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 1993-04-02 08:54:14 PST Newsgroups: comp.lang.ada Path: gmd.de!newsserver.jvnc.net!darwin.sura.net!haven.umd.edu!uunet!news.crd.ge.com!e7sa!groleau From: groleau@e7sa.crd.ge.com (Wes Groleau X7574) Subject: Re: Language lawyer needed Message-ID: Sender: usenet@crdnns.crd.ge.com (USENET News System) Nntp-Posting-Host: 144.219.40.1 Organization: GE Corp R&D Center, Schenectady NY Date: Fri, 2 Apr 1993 16:39:46 GMT Date: 1993-04-02T16:39:46+00:00 List-Id: Hey, everyone, please don't flame the poor guy! writes: >Here's a question for language lawyers. > >Consider the following pathological program: > > procedure Q(x : integer) is > begin > declare > x : integer; -- (1) > begin > Q(x => 0); -- (2) > end; > end Q; > The "x" in (2) is NOT a variable; it is there to tell the compiler (which knows anyway) WHICH of the parameters of Q needs to get the value zero. Study up in all your Ada books, including the LRM, about named associations, if you really want to know about this. On the other hand, if you're just nit-picking to make Ada look bad, it didn't work: we adults can tell the difference between "bad" and "not perfect"