Re: A bug in scan.l - Mailing list pgsql-hackers

From Gokulakannan Somasundaram
Subject Re: A bug in scan.l
Date
Msg-id 9362e74e0909012237w4726a226t30a00ef66b88048d@mail.gmail.com
Whole thread Raw
In response to Re: A bug in scan.l  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: A bug in scan.l
List pgsql-hackers
Well, i am at a very beginner level with Flex. I could see how flex works with it even if it is a ambiguity. Since it matches the rule with the maximum text and we don't allow a new line character in the rule, it works fine.  Even in LL(1), it works fine, but throws warnings. So i just thought of suggesting to remove the ambiguity.
But do we need to allow comments as part of unicode escapes?

Thanks,
Gokul.

On Wed, Sep 2, 2009 at 8:37 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Gokulakannan Somasundaram <gokul007@gmail.com> writes:
> I have replaced whitespace with space. This has to be done because
> whitespace allows comments. This would cause conflict between some of the
> alternatives. I found this, while trying to make this rule work with LL(1).

Um, if it's ambiguous, why doesn't flex complain?

                       regards, tom lane

pgsql-hackers by date:

Previous
From: Jaime Casanova
Date:
Subject: Re: remove flatfiles.c
Next
From: Itagaki Takahiro
Date:
Subject: Re: make installcheck is broken in HEAD on mingw