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=0.2 required=5.0 tests=BAYES_00,INVALID_MSGID, REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,3b05f12bd7a2a871 X-Google-Attributes: gid103376,public From: Mats Weber Subject: Re: Lexical Conundrum Date: 1998/02/24 Message-ID: <34F2BC0A.694AD65F@elca-matrix.ch>#1/1 X-Deja-AN: 328152991 Content-Transfer-Encoding: 7bit References: <01bd3d80$101287c0$LocalHost@xhv46.dial.pipex.com> <34F1BC2B.529629AF@lmco.com> Mime-Version: 1.0 Reply-To: Mats.Weber@elca-matrix.ch Content-Type: text/plain; charset=us-ascii Organization: ELCA Matrix SA Newsgroups: comp.lang.ada Date: 1998-02-24T00:00:00+00:00 List-Id: Mark A Biggar wrote: > Not really, as section 2.2(7) only talks about cases that require white space > between tokens to be legal. The real point in this example is the "or" is > a keyword not an identifier, so the following "'" must be the start of > a character literal, not the start of an attribute. If you look at the > LM grammar, you will find that there are NO cases where an attribute follows > a key word and also NO cases where a character literal follows an identifier, Not true: e.g. X.all'Address is legal. > so you can always determine the meaning of "'" just by remembering the > classification of the previous token. True, but you have to treat all as a special case.