[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: flex question
From: |
Hans-Bernhard Broeker |
Subject: |
Re: flex question |
Date: |
Thu, 18 Oct 2001 19:23:15 +0200 (MET DST) |
On Thu, 18 Oct 2001, W. L. Estes wrote:
> > fatal flex scanner internal error--end of buffer missed
[...]
> > This problem happens only on one test case, and other 75 tests passes OK.
> > gcc version I'm using on the Linux system (Red Hat 7.1) is egcs-2.91.66.
> > The same input works fine if I use 'lex' on a Sun Solaris machine.
Hmm... has this same scanner ever been used with 'flex' instead of
classical AT&T lex? I.e. did you try "flex" on Solaris?
If not, the problem may well be that the scanner is assuming it can rely
on undocumented implementation details of AT&T lex. One thing to watch
out for is modification of yyleng (including calls of yyless()) in any
rule that also uses yymore(). I got bitten by that one myself when
porting a time-approved lexer source from lex to flex.
--
Hans-Bernhard Broeker (address@hidden)
Even if all the snow were burnt, ashes would remain.
- Re: flex question, W. L. Estes, 2001/10/18
- Re: flex question,
Hans-Bernhard Broeker <=