Re: [Caml-list] Why are modules handled differently by the interpreter and the compiler

[Alain Coste <alaincoste@club-internet.fr>]

Hello
Thank you for your answers, and for the patch. Cool for debugging without 
modifying the files !

Alain Coste

----- Original Message ----- 
From: "Grégoire Henry" <henry@pps.univ-paris-diderot.fr>
To: "Gerd Stolpmann" <info@gerd-stolpmann.de>
Cc: "Alain Coste" <alaincoste@club-internet.fr>; <caml-list@inria.fr>
Sent: Monday, November 05, 2012 3:30 AM
Subject: Re: [Caml-list] Why are modules handled differently by the 
interpreter and the compiler


>> What could be implemented as an extension is a #use_as_module
>> directive that adds the implicit module. This could be in deed
>> useful for debugging, especially when it overlooks the mli file if
>> present - if you #load, the definition hiding of the mli file takes
>> place, and you cannot see unexported definitions anymore. Of course,
>> this is sometimes in the way when you test things out.
>>
>> Now that compiler-libs is installed this extension could probably
>> even be implemented outside the compiler. Anyone up for it?
>
> Well, here it is:
>
>  $ ocamlmktop -o myocaml mod_use.ml
>  $ cat test.ml
>  let x = 53
>  $ ./myocaml
>        OCaml version 4.00.1
>
>  # #mod_use "test.ml";;
>  module Test : sig val x : int end
>  # Test.x;;
>  - : int = 53
>
> Regards,
> Grégoire
>
> -- 
> Caml-list mailing list.  Subscription management and archives:
> https://sympa.inria.fr/sympa/arc/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs