RE: Bison Windows m4 problems

2010-03-10 Thread Supervisor Root
Don't install Bison for windows in a directory which contain spaces, it causes the error. For example, you can install bison in "d:\GNU32\bin", but not in "d:\program files\gnu32\bin". > Date: Thu, 11 Mar 2010 13:33:23 +1100 > From: effb...@gmail.com > To: herron.phi...@googlemail.com >

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]+ ; [\

Bison perhaps has a bug.

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" %} %% [ \

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]+ ;