[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: parse error from bison.simple

From: Hans Aberg
Subject: Re: parse error from bison.simple
Date: Sat, 2 Feb 2002 10:39:38 +0100

At 17:02 -0800 2002/02/01, Karin Salt wrote:
>I am getting Parse error 'parse error' from
>bison.simple whenever the string contains "@"
>or "$" or "%". Are theose considered as special
>*invlaid* characters? why?

The Bison generated parser does not parse characters, but token numbers as
handed over by the lexer (scanner), and does not know anything about
characters and streams. So it depends on what your lexer sends to the Bison
generated parser.

You do not tell what kind of error you get, but if it says
"...undefined..." something, it may happen that you have a Flex type
generated lexer with a rule
  . { return yytext[0]; }
Then the lexer may hand over characters with token numbers that the Bison
generated scanner does not recognize. Check the .l and .y sources.

  Hans Aberg

reply via email to

[Prev in Thread] Current Thread [Next in Thread]