From: "Eric C. Cooper" <ecc@cmu.edu>
> Suppose I extend an existing module, like the standard List module,
> with some new functions:
> 
[...]
> 
> As far as I can tell, I can't write a list_extensions.mli file without
> textually including the standard List .mli file, which isn't very good
> software engineering practice.

I'm not sure of what is good (or bad) software engineering.
However I'm convinced that this is a real pain.

I had a simple proposal: a .mli file would not only be used as a
constraint for the corresponding .ml file, but would also define
a signature of the same name.
Then you could simply write 
  sig include List ... end

But it has not been accepted yet...

Jacques Garrigue

-------------------
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