Re: Bison/flex compatibility revisited

[John]

> but there do seem to be too many public names by default with flex
> right now.

There are currently 16 macros exposed by the flex-generated header (of
a possible 97), and ALL of them are bugs. They crept in when one of us
added a macro to the skeleton, then forgot to append it to the #undef
list for the generated header.

There should be zero macros exposed by the flex header. Thus, there is
no namespace clash.