From: Eric Cooper <ecc@cmu.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Modules vs Modular programming
Date: Fri, 23 Feb 2007 15:41:45 -0500 [thread overview]
Message-ID: <20070223204145.GA4632@localhost> (raw)
In-Reply-To: <1172261771.5108.9.camel@oxylin.no-ip.org>
On Fri, Feb 23, 2007 at 09:16:11PM +0100, Julien Peeters wrote:
> I'am currently working on a academic project in OCaml. I have to do the
> choice of multiple files vs multiple ocaml modules per file.
>
> I would like to know your point of view about this choice I have to do.
> For instance, what did you choose if you've already done this choice and
> why?
I would use one module per file for all but trivial modules, to take
advantage of the OCaml compiler's support for that model (pairing of
.mli with .ml files), and better support by software development tools
like make and subversion, etc., which operate at file granularity.
An example of trivial modules where this doesn't apply would be those
built for the purposes of functor application -- they often have
components that just rename values defined elsewhere.
--
Eric Cooper e c c @ c m u . e d u
prev parent reply other threads:[~2007-02-23 20:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 20:16 Julien Peeters
2007-02-23 20:41 ` Eric Cooper [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070223204145.GA4632@localhost \
--to=ecc@cmu.edu \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).