> Another possibility is to disallow SET here, but not in other places > where ColId is used. That is, some hack like:
Quick point: If all you want to do if disallow SET here as ColID but allow SET in other places with a ColId, you don't have to change anything at all. Just make sure the rule for the want you prefer is earlier in the file. Shift/reduce and reduce/reduce errors still produce valid working parsers, it's just that bison has to resolve an ambiguity by the default (shift, otherwise earliest rule wins. maximum munch rule really). If you don't like relying on file order to resolve this, appropriate use of %prec would have the same effect (just like for operator precedence). The output file tell you which way bison went. Have a nice day, -- Martijn van Oosterhout <firstname.lastname@example.org> http://svana.org/kleptog/ > Patent. n. Genius is 5% inspiration and 95% perspiration. A patent is a > tool for doing 5% of the work and then sitting around waiting for someone > else to do the other 95% so you can sue them.
Description: Digital signature