[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
empty component causes shift/reduce conflict
From: |
Jibin Han |
Subject: |
empty component causes shift/reduce conflict |
Date: |
Fri, 07 Feb 2003 14:59:35 -0700 |
Hello,
I am new to bison, but from my experience, if there is an empty
component in a rule like this,
result: /* empty */
|
comp1 comp2 {...}
then it definetely causes shift/reduce conflict. But such conflict
in this case is harmless because the Bison default choice, shift comp1,
is always what we want.
Do you think so?
Thanks!
- empty component causes shift/reduce conflict,
Jibin Han <=