Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Matt Gushee <mgushee@havenrock.com>
To: caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Do you like files as modules?
Date: Wed, 6 Oct 2004 23:38:01 -0600	[thread overview]
Message-ID: <20041007053801.GA16450@swordfish> (raw)
In-Reply-To: <1097118765.20680.565.camel@pelican.wigram>

On Thu, Oct 07, 2004 at 01:12:46PM +1000, skaller wrote:
> 
> In both Ocaml and Python, the module name is also
> coupled to the filename.

This doesn't bother me, but it would be nice if the compilers had an
option allowing you to associate differently-named interface and
implementation files. Currently, if you have an interface 'foo.mli',
with several possible implementations, you have to resort to kludges
like creating subdirectories a/, b/, and c/, each with a different
version of 'foo.ml', one of which gets copied into the main directory at
build time. It should be possible to have foo_a.ml, foo_b.ml, and
foo_c.ml, and arbitrarily select one as the implementation of Foo.

-- 
Matt Gushee                 When a nation follows the Way,
Haven Rock Press            Horses bear manure through
Englewood, Colorado, USA        its fields;   
books@havenrock.com         When a nation ignores the Way,
                            Horses bear soldiers through
                                its streets.
                                
                            --Lao Tzu (Peter Merel, trans.)

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


  reply	other threads:[~2004-10-07  5:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-07  3:12 skaller
2004-10-07  5:38 ` Matt Gushee [this message]
2004-10-07 16:14   ` [Caml-list] " Stefan Monnier
2004-10-07 19:45 ` [Caml-list] " William Lovas

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=20041007053801.GA16450@swordfish \
    --to=mgushee@havenrock.com \
    --cc=caml-list@pauillac.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