bison - yacc shift/reduce conflict. It really serious complexity -


I was trying several times to solve this conflict.

But I do not know why. Conflict Here

2 Conflicts are at fault time

Yak (bison) error goes:. State: 314 Conflicts: 1 Inning / State Less 315 Conflict: 1 Change / Reducing State 314 7 c_complex_object_id: type_identifier 8 | Type_identifier V_LOCAL_TERM_CODE_REF V_LOCAL_TERM_CODE_REF shift, and go to state 77, decrease using the V_LOCAL_TERM_CODE_REF $ default rule 7 (c_complex_object_id) state 315 127 c_integer_spec using the [7 (c_complex_object_id) rule]: integer_value. 184 Sort by: integer_value SYM_INTERVAL_DELIM V_QUALIFIED_TERM_CODE_REF 201 integer_list_value: integer_value. ',' Round_value 203 | integer value . Go to the 'SYM_LIST_CONTINUE SYM_LIST_CONTINUE SYM_LIST_CONTINUE SYM_INTERVAL_DELIM change, and go to State 200 using the rule 127 (c_integer_spec)] Reduce the value of $ 128 by using the rule 127 (c_integer_spec) state 77 8 c_complex_object_id: type_identifier V_LOCAL_TERM_CODE_REF $ default rule 8 (c_complex_object_id) is reduced using state 380,184 Kramwatr: Puarnank_muly SYM_INTERVAL_DELIM V_QUALIFIED_TERM_CODE_REF V_QUALIFIED_TERM_CODE_REF shift, and go 422 state 200 201 integer_list_value state: integer_value ','. Round_name 203 integer value ',' . SYM_LIST_CONTINUE V_INTEGER innings, and state 2 SYM_LIST_CONTINUE go on shift, and to 276 '+' shift to the state, and the state go to 170 "-" shift, and go to state 277 ...

yacc source: 

  c_complex_object_id: type_identifier | Type_identifier V_LOCAL_TERM_CODE_REF; Type_identifier: '(' V_TYPE_IDENTIFIER ')' | '(' V_GENERIC_TYPE_IDENTIFIER ')' | V_TYPE_IDENTIFIER | V_GENERIC_TYPE_IDENTIFIER; C_integer_spec: integer_value | | Integer_list_value | Integer_interval_value; C_integer: c_integer_spec | C_integer_spec ';' Full_value | C_integer_spec ';' Error; Success: full_value SYM_INTERVAL_DELIM V_QUALIFIED_TERM_CODE_REF; Integer_list_value: integer_value ',' integer_value | Full_value ',' SYM_LIST_CONTINUE; Full_value: V_INTEGER | '+' V_INTEGER | '-' V_INTEGER;   
 I have two problems with what is wrong with it?   
 
 
 Let's period to reduce the message / conflict of the first inning as the pointer ( ".") what message in English or say less read,  
 "when I am in the 29 9, and I have a  type_identifier  is recognized, then I have to decide whether the rule is intended to reduce or No. 7 (Id  c_complex_object_id: type_identifier ) or to continue scanning) for up to 63 shifts from the state (a  V_LOCAL_TERM_CODE_REF  "  < P> Usually this comes about a struggle like this. When the output is not yet recognized ( V_LOCAL_TERM_CODE_REF ) is optional.  
 Your definition of Token V_LOCAL_TERM_CODE_REF, etc. looks exactly as far as I can tell from your comment.  
  It is difficult to diagnose further without seeing the YF diagnostic output for State 63. Can you edit your question to show output for State 63? It can tell us something   
 I got something that might be useful background for you. You can also read some of the other questions listed in the right column of this page under the "Related" heading.  
  Update   
 In the same way, you are right: a change / less conflict can be ignored. Bison / Waiseepi that will produce a parser which runs that  some  but it is important to understand that  do  you are ignoring a specific conflict. So you will understand that the parser, when presented with an input program, parses it in such a manner and produces the output that it does. It is not good to say, "Oh, this is very complicated, I can not understand it."

Comments

Post a Comment