caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: John Max Skaller <skaller@ozemail.com.au>
To: Michael Hicks <mwh@dsl.cis.upenn.edu>
Cc: Charles Martin <martin@chasm.org>, caml-list@inria.fr
Subject: Re: Module hierarchies
Date: Tue, 09 Jan 2001 19:03:40 +1100	[thread overview]
Message-ID: <3A5AC5DC.213F3D51@ozemail.com.au> (raw)
In-Reply-To: <MABBJDLGAJOFDJKIGNELGEBOCAAA.mwh@dsl.cis.upenn.edu>

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

	My solution is simple enough: I use a literate programming 
tool (interscript, see my sig below) to _generate_ all the Ocaml files 
in a scratch directory.

	So the structure of the program is defined in terms of the
LP source files, which need to be related to the generated files.
(It usually is though :-)

	The only problem I have with this is that ocamllex/yacc
do not respect #line directives.

-- 
John (Max) Skaller, mailto:skaller@maxtal.com.au
10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850
checkout Vyper http://Vyper.sourceforge.net
download Interscript http://Interscript.sourceforge.net



  reply	other threads:[~2001-01-09  9:04 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 [this message]
2001-01-07 20:37 ` Vitaly Lugovsky
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=3A5AC5DC.213F3D51@ozemail.com.au \
    --to=skaller@ozemail.com.au \
    --cc=caml-list@inria.fr \
    --cc=martin@chasm.org \
    --cc=mwh@dsl.cis.upenn.edu \
    /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).