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,3b05f12bd7a2a871 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: Lexical Conundrum Date: 1998/02/23 Message-ID: #1/1 X-Deja-AN: 327883703 References: <01bd3d80$101287c0$LocalHost@xhv46.dial.pipex.com> <6crnal$9ei$1@peuplier.wanadoo.fr> X-Complaints-To: usenet@news.nyu.edu X-Trace: news.nyu.edu 888252451 6922 (None) 128.122.140.58 Organization: New York University Newsgroups: comp.lang.ada Date: 1998-02-23T00:00:00+00:00 List-Id: JPR says <> It is a difficulty in lexical analysis I would say, rather than parsing. If you absorb the lexical rules into the grammar accepted by the parser, there are no ambiguities, and no need for look ahead. The only "difficulty" arises in doing separate lexical analysis, and as I showed from the GNAT code, this difficulty is so trivial to resolve that I see no reason to even describe it as a difficulty, hence my quotes. As for one character attributes, not so fast, when you have wide characters, the test for whether the thing following a quote is or is not a valid character literal is not that simple, and indeed that test would probably be more work than the simple test done in the GNAT lexical analyzer. There are no one character attributes in GNAT currently, but if we ever found a case where a one character name was the right choice, we could add this without any difficulties or special processing being required.