Re: Bison/flex compatibility revisited

[Bruce Lilly]

John wrote:

> That's what the function yyget_out() is for. See the section titled,
> "Functions and Macros Available in Reentrant C Scanners", in the flex
> manual.

Yes, but the shorthand yyout described in that section only works
directly in pattern actions, not in code in a separate module
which is called from a pattern action (unless exposed along with
everything else via the flex-generated header or redefined longhand),
and yyget_out() doesn't work in a static (non-reentrant) lexical
analyzer, does it?  So if I either move code from an action to a
separate module or switch from a static to reentrant (or vice
versa) lexical analyzer, there's a great deal of rewriting to be
done unless everything in the header is exposed.

And there's still the issue of the macro renaming yyget_out to
fooget_out, which isn't available unless everything in the header
is exposed.  Couldn't the macros related to prefix renaming be
left visible; there won't be any if there's no prefix option, and
if a prefix is being used, surely the programmer expects to get
the right functions rather than an undefined reference?