bison2.4.1 perhaps has a bug under winxp platform.

2010-02-09 Thread Supervisor Root
I used bison2.4.1, yacc1.9.1 and flex2.5.4 to create a simple parser under windows XP platform, but I found that yyparse return zero when syntax is error, this is or not a bug? The parser's yacc grammar is as follows: /*statement.flex*/ /* */ %{ #include #include "y.tab.h" %} %% [ \t]+ ; [\

Re: bison2.4.1 perhaps has a bug under winxp platform.

2010-02-08 Thread Joel E. Denny
On Mon, 8 Feb 2010, Supervisor Root wrote: > I used bison2.4.1, Okay. > yacc1.9.1 We only support Bison here. > and flex2.5.4 Flex 2.5.4 is very old. I'm using Flex 2.5.34 at the moment. However, off the top of my head, I don't see how updating would address your problem. > to create a s

bison2.4.1 perhaps has a bug under winxp platform.

2010-02-08 Thread Supervisor Root
Through my testing, I found there was a bug in bison2.5.4. I used bison2.4.1, yacc1.9.1 and flex2.5.4 to create a simple parser under windows XP platform and Linux platform. The parser's yacc grammar is as follows: /*statement.flex*

bison2.4.1 perhaps has a bug under winxp platform.

2010-02-08 Thread Supervisor Root
I used bison2.4.1, yacc1.9.1 and flex2.5.4 to create a simple parser under windows XP platform, but I found that yyparse return zero when syntax is error, this is or not a bug? The parser's yacc grammar is as follows: /*statement.flex*/ /* */ %{ #include #include "y.tab.h" %} %% [ \t]+ ;