RE: [Caml-list] automatic extaction of the .mli (and a little more) from the .ml

[David Allsopp <dra-news@metastack.com>]

Alain Frisch wrote:
> On 06/04/2013 09:53 AM, David Allsopp wrote:
> > I have wondered if this problem is perhaps looked at the wrong way
> > around - in other words, the complaint takes the form "how can we
> > export to the .mli file automatically" rather than "how can we
> > *import* from the .ml file automatically". The thing I do find
> > irritating maintaining .mli/.ml files is having to type anything out
> > twice - and for the most part that means fully exported type
> > declarations. Say you have a simple module:
> 
> I'd rather do it the other way around: maintain the type declaration in
> the .mli and import it in the .ml file.

My thinking was that the type declaration is part of the implementation at that point so should be in the .ml file - but actually I agree that it's better to do it the other way around (given that installing .mli files is quite common, for example).
 
> And, guess what, there is also a POC of such a tool in the
> extension_points branch.  It allows you to write in the .ml file:
> 
>    type t = [%copy_typedef]

This is very cool - will have to check out this branch and have a play when I have a moment!


David