Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: christo@nextsolution.co.jp (Frank Christoph)
To: caml-list@pauillac.inria.fr
Subject: Re: Managing module names
Date: Thu, 24 Jul 1997 14:21:46 +0900	[thread overview]
Message-ID: <199707240521.OAA00374@sparc3.co.jp> (raw)

> >>>>> "monniaux" == David Monniaux <monniaux@csl.sri.com> writes:
>     monniaux> Would it be possible to make up some scheme that would to
>     monniaux> things like: /graphics/blackwhite/main ->
>     monniaux> Graphics.Blackwhite.Main ?
> 
>     monniaux> Or, better: would it be interesting according to other users?
> 
> Absolutely! I think that such an arrangement would be even more useful
> than what exists presently.

In my experience, nested modules are not very useful in (O)CAML because you
cannot have a recursive definition cross a module boundary, and I find that
I quite often have mutual dependencies between sets of definitions whose
namespaces I would nevertheless like to separate.

I suspect that the reason package nesting in Java works so well is partly
due to the fact that recursion, etc. is hardly ever used.

On the other hand, SML seems to use module nesting quite freely, though,
and as far as I know it has the same restrictions on module dependencies...

-- FC





             reply	other threads:[~1997-07-24  7:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-07-24  5:21 Frank Christoph [this message]
1997-07-25 13:56 ` Fabrice Le Fessant
1997-07-25 16:39   ` ocamlc compiled in native code Fabrice Le Fessant
  -- strict thread matches above, loose matches on Subject: below --
1997-07-22 14:19 Managing module names Paul Stodghill
1997-07-22 23:45 ` David Monniaux
1997-07-23 12:29   ` Paul Stodghill
1997-07-24 14:36   ` Judicael Courant

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=199707240521.OAA00374@sparc3.co.jp \
    --to=christo@nextsolution.co.jp \
    --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