0003545: Shadowing not handled correctly in .ml-generated .cmi

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0003545

OCaml

OCaml general

public

2005-03-17 04:04

2005-08-08 11:52

Reporter

administrator

Assigned To

Priority

normal

Severity

feature

Reproducibility

always

Status

acknowledged

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Summary

0003545: Shadowing not handled correctly in .ml-generated .cmi

Description

Full_Name: Aleksey Nogin
Version: 3.08.2
OS: Mandrake Linux 10.0
Submission from: wasco.cs.caltech.edu (131.215.44.173)

If I have a .cmi that is generated by compiling a ".mli-free" .ml, and the .ml
has shadowing, then an attempt to re-compile .ml while type-checking against the
.cmi will fail with a type error!

% ocamlc -version
3.08.2

% ls x.*
x.ml

% cat x.ml
let x = 1

let x = "s"

% ocamlc -c x.ml

% ls x.*
x.cmi x.cmo x.ml

% ocamlopt -c -intf-suffix .cmi x.ml
The implementation x.ml does not match the interface x.cmi:
Values do not match: val x : string is not included in val x : int

P.S. You might wonder why one would want to do something like this in the first
place. Basically, I want to have build rules that would allow:
a) building both native and bytecode versions of an OCaml project
b) parallelized builds.

I want to be able to say that in the absence of .mli, the way to generate .cmi
file is to run ocamlc on .ml. The problem with is is that once the .cmi is
generated by the ocamlc, some "consumer" of that .cmi may end up running in
parallel with the ocamlopt for the .ml. Since ocamlopt would create the .cmi
again and will actually overwrite it in place, I am likely to get a "corrupted
.cmi" error message from the "consumer" process.

I was hoping to be able to solve this by using "ocamlopt -intf-suffix .cmi" for
compiling .ml files whenever building both native and bytecode versions. This
did not work because of this bug.

This "build rules" issue is discussed in slightly more detail in a bug report
for the OMake build system is http://bugzilla.metaprl.org/show_bug.cgi?id=421 [^]

Issue History
Date Modified	Username	Field	Change
2005-11-18 10:13	administrator	New Issue

Notes
(0000253) administrator (administrator) 2005-08-08 11:52	Obvious fix (attempted 2005-08-02 by XL) doesn't work. This bug is not critical, so I'll leave it as feature wish.

Relationships