caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Vitaly Lugovsky <vsl@ontil.ihep.su>
To: Charles Martin <martin@chasm.org>
Cc: caml-list@inria.fr
Subject: Re: Module hierarchies
Date: Sun, 7 Jan 2001 23:37:08 +0300 (MSK)	[thread overview]
Message-ID: <Pine.LNX.4.10.10101072332540.25900-100000@ontil.ihep.su> (raw)
In-Reply-To: <5.0.0.25.0.20010106112842.00a3eeb0@chasm.org>

On Sat, 6 Jan 2001, Charles Martin wrote:

> I am wondering how a large OCaml project might be structured, specifically
> in terms of directories and files. 

[...]

> I think this would be helpful for structuring large projects.  It would
> also make it easier to incorporate third-party utilities, since we could
> then adopt Java-style naming conventions: the distribution modules would
> all be wrapped inside Ocaml, and everything else would use the inverted
> domain name convention:

 There is an easy solution: 
1) allow dots in module names
2) write a compilation script, which converts directory structure to a
number of files with dots. 

[I really hate javish directory hierarchy for classfiles - it's good for
sources, not for binaries]

 And, btw, findlib is also a good tool for a big project structuring.

--

   V.S.Lugovsky aka Mauhuur (http://ontil.ihep.su/~vsl) (UIN=45482254)




  parent reply	other threads:[~2001-01-07 20:23 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-06 19:32 Charles Martin
2001-01-07 10:10 ` Mattias Waldau
2001-01-07 16:07 ` Michael Hicks
2001-01-09  8:03   ` John Max Skaller
2001-01-07 20:37 ` Vitaly Lugovsky [this message]
2001-01-08 10:24 ` Xavier Leroy
2001-01-08 14:01   ` Judicael Courant
2001-01-09 16:46 Dave Berry
2001-01-10  9:40 ` Markus Mottl
2001-01-09 17:34 Daniel Ortmann
2001-01-09 18:06 Dave Berry
2001-01-10 20:12 ` Gerd Stolpmann
2001-01-11 12:53 Dave Berry

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=Pine.LNX.4.10.10101072332540.25900-100000@ontil.ihep.su \
    --to=vsl@ontil.ihep.su \
    --cc=caml-list@inria.fr \
    --cc=martin@chasm.org \
    /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).