Use exclusive start conditions. Have flex (or a wrapper) issue a token that is particular to the situation at hand. Of course, you are carrying the overhead of larger tables.
On 6 February 2011 14:39, Martin Alexander Neumann < hotpotatorout...@googlemail.com> wrote: > Hi, > > some time ago I designed a flex + bison system for an embedded system > for which I needed selective compilation -- different systems needed > different language subsets of my flex and bison files. I threw together > a solution using the C preprocessor to selective compile in only the > relevant stuff. It is working pretty well but how about a solution > natively integrated into flex and bison? > > Cheers, Martin > > > _______________________________________________ > help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison > _______________________________________________ help-bison@gnu.org http://lists.gnu.org/mailman/listinfo/help-bison
