Re: Bison/flex compatibility revisited

[John]

> 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.

No. If you use the accessor methods everywhere, there is no problem
and you code works in actions as well as externally.


> 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.

That's the point of the prefix! If you choose the prefix "foo", you
can not expect to call any "yy*" functions. They have all been renamed
to "foo*".