| Hans Aberg writes:
| > You can use the Bison %left command on your "or" operator (see the manual
| > for calculator example).
|
| OR is already %left. The actual lines look like this:
| answer_statement: ANSWER expr answer_btn_list { ... }
|
| | ANSWER_FILE { ... }
| | ANSWER_FILE expr { ... }
| | ANSWER_FILE expr OF TYPE expr { ... }
| ; answer_btn_list: WITH answer_btn_list_oneplus { ... }
|
| | { ... }
| ;
| answer_btn_list_oneplus: answer_btn_list_oneplus OR expr { ... }
| | expr { ... }
| ; Now, expr contains, among many other lines,
|
| expr: ...
| | expr OR expr { ... }
| ...
| ; The problem is a line which looks like this ANSWER expr WITH expr
| ; OR expr
|
| ^^ Bison chooses the resolve the ambiguous
| grammar by shifting at the
Well, if the problem is on a sentence such as
ANSWER expr WITH expr OR expr
and you want it too be understood as
ANSWER expr WITH (expr OR expr)
then you need to say that WITH has a very low priority: lower than any
operator that can appear in the second expr of ANSWER/WITH.
_______________________________________________
Freecard-general mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/freecard-general
