Browse thread
[Caml-list] non-exported functions
[
Home
]
[ Index:
by date
|
by threads
]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
| Date: | -- (:) |
| From: | skaller <skaller@o...> |
| Subject: | Re: [Caml-list] non-exported functions |
On Wed, 2003-10-29 at 18:52, Dustin Sallings wrote: > On Oct 28, 2003, at 10:50 PM, Jean-Baptiste Rouquier wrote: > > >> I kinda liked automatically generating my .mli, > > ocamlc -i foo.ml > foo.mli > > Right, like that. If I have to make a custom mli, I have to take this > out of my build system. :) That command is guarranteed to be useless in a build system. The generated interface is exactly the same as the one that is extracted from the compiled ml file anyhow. The -i command is only to get a text file for the purpose of subsequent manual editing. Mli files are ONLY needed when there's an actual constraint. Every ml file I write has a manually constructed mli file, because almost invariably I *do* have helper functions I dont wish to expose to clients. I sometime use ocamlc -i to get the interface generated by a functor application .. (is there another way to do that, its woefully crude ..) ------------------- To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/ Beginner's list: http://groups.yahoo.com/group/ocaml_beginners