Mantis Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0004871OCaml~DO NOT USE (was: OCaml general)public2009-09-21 12:022012-07-11 14:20
Assigned To 
PlatformOSOS Version
Product Version3.11.0 
Target VersionFixed in Version 
Summary0004871: ocamlyacc and type clash between ml and mli

Ocamlyacc handles type scopes differently in the mli and ml.

For instance, suppose I have a file 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 does not.
If I write t, B.mli does not compile but would.

Ok, it is probably bad practice to shadow module names.
Yet the current behaviour is a little inconsistent...


TagsNo tags attached.
Attached Files

- Relationships

-  Notes
doligez (administrator)
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
2017-02-23 16:36 doligez Category OCaml general => -OCaml general
2017-03-03 17:55 doligez Category -OCaml general => -(deprecated) general
2017-03-03 18:01 doligez Category -(deprecated) general => ~deprecated (was: OCaml general)
2017-03-06 17:04 doligez Category ~deprecated (was: OCaml general) => ~DO NOT USE (was: OCaml general)

Copyright © 2000 - 2011 MantisBT Group
Powered by Mantis Bugtracker