Le 11 oct. 2012 à 16:46, Adam Smalin a écrit : > hmm, I never thought about just building it with bison and including > it later (so no input). > The only issues I see is I will need to force the user to specify if > it should be function, class or namespace level. It may be a lot of > work to make another set of rules that is all levels. I already have > 1K lines (look like 1300 lines of rules. I'm counting between the two > %%) but I think I'll give it a try if it will make this higher > quality.
It looks like a _very_ large grammar. > I'd still like to know how I can check state and stack in case its > easier to do that. I'm relooking at the code and the conflicts You still have not explained if parsing inside @start/@end is wanted or not. If it is not, then these questions are not related to Bison, but for instance to Flex. In that case, have a look at start conditions, and to functions such as yy_push_state. Or just deal with counters. I don't understand what you mean by "check state and stack". You're not expected to check the state and stack of your parser at runtime (unless you mean reading the *.output file), that the parser's business. _______________________________________________ help-bison@gnu.org https://lists.gnu.org/mailman/listinfo/help-bison
