Re: Bison/flex interface (Was Re: [GNU bison 1.75b] testsuite.log: 14 failures)

[John Millaway]

> Akim Demaille wrote:
> > > Akim Demaille wrote:
> > > >  Bruce> Finally, there are some bad interactions between bison
> > > >  1.75b Bruce> and flex 2.5.23: bison unconditionally #defines
> > > >  YYLTYPE, which Bruce> causes grief when location tracking is
> > > >  undesired, Why  exactly did this cause a problem?
> > >
> > > Flex 2.5.2[345] %option header generates a header file that
> > > contains #ifdef YYLTYPE and that causes inappropriate
> > > declataions for yylex, etc. when the flex-generated header is
> > > included in the bison-generated parser.
> >
> > YYLTYPE was a name invented in the Bison world: how can they use
> > it without asking us?  It seems to me that Flex cannot know what
> > the signature of yylex will be, it also depends whether the parser
> > is pure or not.  Unless explicitly told by the user, I fail to see
> > how flex could decide what the prototype of yylex will be.

How can we use it without asking you?

YYLTYPE is documented in the bison manual. So are YYLEX_PARAM and
YYPARSE_PARAM. Do you we have to ask someone in order to use them?

Besides, this is no surprise. You knew about this over one year ago,
when we argued at length about it. See the flex-help list archives.