|Anonymous | Login | Signup for a new account||2016-08-24 23:32 CEST|
|Main | My View | View Issues | Change Log | Roadmap|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0005978||OCaml||OCaml documentation||public||2013-04-09 05:58||2013-04-10 13:52|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Status||closed||Resolution||no change required|
|Target Version||Fixed in Version|
|Summary||0005978: the BNF for expression seems to be incorrect|
| 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.
|Tags||No tags attached.|
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.
|2013-04-09 05:58||hongboz||New Issue|
|2013-04-09 08:05||garrigue||Note Added: 0009046|
|2013-04-10 13:52||doligez||Note Added: 0009061|
|2013-04-10 13:52||doligez||Status||new => closed|
|2013-04-10 13:52||doligez||Resolution||open => no change required|
|Copyright © 2000 - 2011 MantisBT Group|