Hello,
Thank you for your attempts ...
I know of the double vision problem, and I am actually confused by
the post which you reference. I think it discusses an old version of
the typechecker, as the example which Xavier Leroy gives supposedly to
illustrate the flaw now (3.10.2) properly
Hello,
Can I look at the code which does not type check without Obj.magic?
Ideally something like if I comment out Obj.magic then I get a type
error, and if I comment it in then the code type checks, so that I can
identify the point of the issue? (In the context of this simplified
example of
Hello,
I'd always thought of separating specification and definition as
simply not possible in OCaml, but OCaml's reference manual (3.10,
which is, as far as I can tell, the most recent version of the
documentation) seems to contradict my assumption:
-c modrec.ml (with modrec.ml having the same contents as modrec.mli)
complains it has a syntax error.
Matthieu
- Message d'origine
De : Jérémie Lumbroso [EMAIL PROTECTED]
À : [EMAIL PROTECTED]
Envoyé le : Mercredi, 20 Août 2008, 16h31mn 51s
Objet : [Caml-list] Specifying
Hello,
I guess you need it to mirror the value shadowing on the implementation side:
include Foo
let bar = baz
This is legal if Foo already defines bar, and most of the time desired and
useful.
In the interface file you'll want to write :
include FOO (* Foo's signature *)
val
