[Top][All Lists]

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

Declaration of yyparse not moved into --defines header file

From: Guus Leeuw jr
Subject: Declaration of yyparse not moved into --defines header file
Date: Mon, 6 Jun 2011 07:55:24 +0100


Using bison 2.4.3, I generated a parser by invoking like so:
# bison -y  --defines=ds_config_parser.h -o config_parser.c config_parser.y

Surprisingly, the generated header file ds_config_parser.h does not contain
a declaration of yyparse.
The source config_parser.c does however.

Using a git clone and bootstrapping to check whether this still happens with
the bleeding edge, I come to the conclusion that this is still the case.

I am more than willing to provide some time to get this fixed, however would
need some guidance as to how bison decides which m4 to run in order to
create the header file, and therefore, which skeleton it uses to instantiate
the output.


reply via email to

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