From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id RAA08902; Fri, 18 Jul 2003 17:46:42 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id RAA11010 for ; Fri, 18 Jul 2003 17:46:40 +0200 (MET DST) X-SPAM-Warning: Sending machine is listed in blackholes.five-ten-sg.com Received: from vsmtp1.tin.it (vsmtp1.tin.it [212.216.176.221]) by concorde.inria.fr (8.11.1/8.11.1) with ESMTP id h6IFkdf03428 for ; Fri, 18 Jul 2003 17:46:39 +0200 (MET DST) Received: from dalamar.takhisis.org (80.180.77.215) by vsmtp1.tin.it (7.0.019) id 3F17CBF90001D95B for caml-list@inria.fr; Fri, 18 Jul 2003 17:46:39 +0200 Received: from fistandantilus.takhisis.org (fistandantilus.takhisis.org [192.168.1.113]) by dalamar.takhisis.org (Postfix) with ESMTP id 8AF12B77D for ; Fri, 18 Jul 2003 17:46:38 +0200 (CEST) Received: by fistandantilus.takhisis.org (Postfix, from userid 3148) id 195F52740A9; Fri, 18 Jul 2003 17:46:38 +0200 (CEST) Date: Fri, 18 Jul 2003 17:46:38 +0200 From: Stefano Zacchiroli To: caml-list@inria.fr Subject: Re: [Caml-list] CTAN/CPAN for Caml (COCAN ...?) Message-ID: <20030718154638.GH9003@fistandantilus.takhisis.org> Mail-Followup-To: caml-list@inria.fr References: <20030715180953.GA8821@redhat.com> <3F17AC55.7050908@ozemail.com.au> <20030718084252.GA1284@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030718084252.GA1284@redhat.com> User-Agent: Mutt/1.5.4i X-Loop: caml-list@inria.fr X-Spam: no; 0.00; bononia:01 caml-list:01 cpan:01 camlimages:01 ocamllib:01 ocamlc:01 schema:01 enforced:01 labltk:01 linked:01 caml:01 toplevel:01 interfaces:01 compile:02 modules:02 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk 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