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 BAA06829; Mon, 8 Sep 2003 01:51:52 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id BAA18426 for ; Mon, 8 Sep 2003 01:51:51 +0200 (MET DST) Received: from kurims.kurims.kyoto-u.ac.jp (kurims.kurims.kyoto-u.ac.jp [130.54.16.1]) by nez-perce.inria.fr (8.11.1/8.11.1) with ESMTP id h87NpmT13456 for ; Mon, 8 Sep 2003 01:51:49 +0200 (MET DST) Received: from localhost (suiren.kurims.kyoto-u.ac.jp [130.54.16.25]) by kurims.kurims.kyoto-u.ac.jp (8.9.3p2/3.7W) with ESMTP id IAA13058; Mon, 8 Sep 2003 08:51:42 +0900 (JST) To: ecc@cmu.edu Cc: caml-list@inria.fr Subject: Re: [Caml-list] referencing the signature inferred from a .mli file? In-Reply-To: <20030907164121.GA15853@ecooper.com> References: <20030907164121.GA15853@ecooper.com> X-Mailer: Mew version 1.94.2 on Emacs 21.2 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20030908085155I.garrigue@kurims.kyoto-u.ac.jp> Date: Mon, 08 Sep 2003 08:51:55 +0900 From: Jacques Garrigue X-Dispatcher: imput version 20000228(IM140) X-Loop: caml-list@inria.fr X-Spam: no; 0.00; caml-list:01 inferred:01 mli:01 jacques:01 mli:01 textually:01 jacques:01 sig:01 garrigue:01 garrigue:01 module:03 module:03 suppose:03 referencing:03 functions:05 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk From: "Eric C. Cooper" > 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