Hi Martin,
If I understand your question correctly, here is a way to have multiple
scanners and parsers in the same program.
In Flex, you can use the --prefix = NEW_PREFIX. This will change the default
"yy" prefix to NEW_PREFIX, So yylex, yytext, yyout, etc., *including
yywrap()*, will change to N
On 07/02/2011 23:13, Tejas Kajarekar wrote:
Hi Martin,
If I understand your question correctly, here is a way to have multiple
scanners and parsers in the same program.
No, he's asking about using a subset of an existing grammar in a new parser.
Example: I have a language which includes a comp
Hi Martin,
If I understand your question correctly, here is a way to have multiple
scanners and parsers in the same program.
In Flex, you can use the --prefix = NEW_PREFIX. This will change the default
"yy" prefix to NEW_PREFIX, So yylex, yytext, yyout, etc., *including
yywrap()*, will change to N
Hai ,
I am using xM Beagle Board. While compiling kernel for my board, I
am getting the following error. I have installed bison-2.3 and flex-2.5.33
in my login. Can any one please clarify why I am getting these errors?
vijay@linux-m2nd:~/Kernel/External/buildroot-adi> make
whi
Use exclusive start conditions. Have flex (or a wrapper) issue a token that
is particular to the situation at hand. Of course, you are carrying the
overhead of larger tables.
On 6 February 2011 14:39, Martin Alexander Neumann <
hotpotatorout...@googlemail.com> wrote:
> Hi,
>
> some time ago I d
Hi,
some time ago I designed a flex + bison system for an embedded system
for which I needed selective compilation -- different systems needed
different language subsets of my flex and bison files. I threw together
a solution using the C preprocessor to selective compile in only the
relevant stuff
