On Fri, Jul 18, 2003 at 09:42:52AM +0100, Richard Jones wrote:
> There seems to be an informal standard right now. eg. camlimages which
> I've been wrestling with all week:
> 
> $OCAMLLIB/camlimages/ contains the code and names top-level module
> names. To compile you just use ocamlc -I +camlimages ...

Such a standard ensure no safety.

A naming schema should be used for all modules whose interfaces are used
in the final objects against which link to.

Camlimages itself is a good example of this property _not_ enforced
because it is named "camlimages", exports a lot of modules prefixed by
"ci_" but internally uses an "Image" module which MD5 sum is present in
all "ci_" modules.

An "image" module is shipped also by labltk which obviously, being a
different piece of software, has a different MD5 sum and can't be linked
along with camlimages.

A naming schema should be enforced not only for the toplevel library
modules, but for all modules being part of it.

Cheers.

-- 
Stefano Zacchiroli  --  Master in Computer Science @ Uni. Bologna, Italy
zack@{cs.unibo.it,debian.org,bononia.it}  -  http://www.bononia.it/zack/
"  I know you believe you understood what you think I said, but I am not
sure you realize that what you heard is not what I meant!  " -- G.Romney

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