You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Original bug ID: 5978 Reporter:@bobzhang Status: closed (set by @damiendoligez on 2013-04-10T11:52:04Z) Resolution: not a bug Priority: normal Severity: minor Category: documentation
Bug description
expr :=
| value-path (* 1 )
| ....
| inst-var-name ( 2 *)
production 2 overlaps with production 1, and I did not see the production 2 in the yacc file either.
The text was updated successfully, but these errors were encountered:
This overlap does not make the BNF in the manual incorrect.
Actually, the BNFs in the manual intentionally choose a more semantical approach, and allow many overlaps. In this case the ambiguity is resolved during type-checking.
As jacques says, the BNF in the manual is ambiguous in many places, and that is by design. It's a documentation, not an implementation.
As a side remark, if you want to do anything serious with the BNF, you should make sure that you are using the one from the SVN version of the manual (v4.01), not the latest released one (v4.00). I have made many fixes between the two.
Original bug ID: 5978
Reporter: @bobzhang
Status: closed (set by @damiendoligez on 2013-04-10T11:52:04Z)
Resolution: not a bug
Priority: normal
Severity: minor
Category: documentation
Bug description
expr :=
| value-path (* 1 )
| ....
| inst-var-name ( 2 *)
production 2 overlaps with production 1, and I did not see the production 2 in the yacc file either.
The text was updated successfully, but these errors were encountered: