Re: [HACKERS] A bug in scan.l

2009-09-02 Thread Tom Lane
Gokulakannan Somasundaram gokul...@gmail.com writes: 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),

Re: [HACKERS] A bug in scan.l

2009-09-01 Thread Gokulakannan Somasundaram
The previous change should follow with this. uescape[uU][eE][sS][cC][aA][pP][eE]{space}*{quote}[^']{quote} Thanks, Gokul. On Wed, Sep 2, 2009 at 7:35 AM, Gokulakannan Somasundaram gokul...@gmail.com wrote: There is a rule like this in scan.l uescapefail

Re: [HACKERS] A bug in scan.l

2009-09-01 Thread Tom Lane
Gokulakannan Somasundaram gokul...@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,

Re: [HACKERS] A bug in scan.l

2009-09-01 Thread Gokulakannan Somasundaram
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