Re: Bison 1.50 breaks reentrant yyerror() usage

[akim]

On Fri, Oct 11, 2002 at 02:01:36PM -0700, Paul Eggert wrote:
> 
> I don't think so.  Apparently we need to rethink subroutines within
> the parser; in the meantime the simplest fix is to undo the introduction
> of yyreport_parse_error, so I've installed the following patch.

Damn it!  I was really hoping nobody would be #defining yyerror :(
This is soo bad, but soo mandated by the brokenness of the current inter-
face :(

I have long been thinking about this (I have exactly the same problem,
and was also doing this attrocious thing, but I thought I was the only
one...) and thing that what we want is:

%param {struct foo *my_foo} {my_foo}
%param {char tab[10]}{tab}

or some similar syntax.  This would completely replace *_PARAM which
is very inconvenient (just look at the cascade of #-handling) and not
portable to other languages.

In addition, as demonstrated aove, one would have the possibility to
have several parameters.  Since I am still thinking of introducing
%include or %import some day, this increases the modularity.

What do you people think?