| Anonymous | Login | Signup for a new account | 2013-06-19 14:05 CEST | ![]() |
| Main | My View | View Issues | Change Log | Roadmap |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
| 0004871 | OCaml | OCaml general | public | 2009-09-21 12:02 | 2012-07-11 14:20 | |||||||
| Reporter | fbesson | |||||||||||
| Assigned To | ||||||||||||
| Priority | normal | Severity | minor | Reproducibility | always | |||||||
| Status | resolved | Resolution | suspended | |||||||||
| Platform | OS | OS Version | ||||||||||
| Product Version | 3.11.0 | |||||||||||
| Target Version | Fixed in Version | |||||||||||
| Summary | 0004871: ocamlyacc and type clash between ml and mli | |||||||||||
| Description | Hello, Ocamlyacc handles type scopes differently in the mli and ml. For instance, suppose I have a file A.ml which defines a type t and a module A. In B.mly, in the header I "open A" and my start symbol has type A.t If I write A.t, B.mli compiles but B.ml does not. If I write t, B.mli does not compile but B.ml would. Ok, it is probably bad practice to shadow module names. Yet the current behaviour is a little inconsistent... Best, | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
Notes |
|
|
(0005943) doligez (manager) 2011-05-31 16:35 |
This will probably never be fixed. The official suggestion is that people should use menhir instead of ocamlyacc. |
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-09-21 12:02 | fbesson | New Issue | |
| 2011-05-31 16:35 | doligez | Note Added: 0005943 | |
| 2011-05-31 16:35 | doligez | Status | new => acknowledged |
| 2012-07-11 14:20 | doligez | Status | acknowledged => resolved |
| 2012-07-11 14:20 | doligez | Resolution | open => suspended |
| Copyright © 2000 - 2011 MantisBT Group |