|Removing GCC warnings from flex- and bison- generated C code firstname.lastname@example.org (Charlie Zender) (2004-01-09)|
|Re: Removing GCC warnings from flex- and bison- generated C code email@example.com (Paul Eggert) (2004-01-12)|
|Re: Removing GCC warnings from flex- and bison- generated C code firstname.lastname@example.org (Charlie Zender) (2004-01-16)|
|From:||Paul Eggert <email@example.com>|
|Date:||12 Jan 2004 12:40:30 -0500|
|Posted-Date:||12 Jan 2004 12:40:30 EST|
At 9 Jan 2004 23:49:52 -0500, Charlie Zender <firstname.lastname@example.org> writes:
> ncap_yacc.c:1216: warning: implicit declaration of function `yylex'
This indicates a minor bug in your parser's C code. Your parser is
supposed to declare 'yylex' (presumably in a file that your parser
includes), but it hasn't done so.
In traditional C and C89, 'yylex' didn't need to be declared, since it
is a function that returns 'int'. But C99 requires that such
functions be declared, and you are using a pedantic C99 compiler.
There's often a similar problem with 'yyerror'.
This is the only problem you had with Bison. I didn't look at your
Flex problems in detail, but many of them appear to be similar.
> [I hope this is on topic, if not where should I send it?]
Please send Bison bug reports to <email@example.com>.
For Flex please see <http://lex.sourceforge.net/>.
Return to the
Search the comp.compilers archives again.