caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Richard Jones <rich@annexia.org>
To: Jean-Baptiste Rouquier <jean-baptiste.rouquier@ens-lyon.org>
Cc: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] module / directory tree  OR  #include for camp4
Date: Tue, 27 Apr 2004 19:11:39 +0100	[thread overview]
Message-ID: <20040427181139.GA4496@redhat.com> (raw)
In-Reply-To: <408D0A43.50802@ens-lyon.org>

On Mon, Apr 26, 2004 at 03:10:27PM +0200, Jean-Baptiste Rouquier wrote:
> So my question is: Is there a canonical way to have submodules with the 
> same name (in different modules) in separate files, allowing to generate 
> documentation and use ocamlopt ? It would be even better if the 
> directory tree would be reflected in the module tree.

A pretty hideous solution would be to use a Makefile to concatenate
source files together, eg:

plot.ml: part1.frag part2.frag part3.frag
	cat $^ > $@

Then edit the individual fragments ...

Rich.

-- 
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
Perl4Caml lets you use any Perl library in your type-safe Objective
CAML programs. http://www.merjis.com/developers/perl4caml/

-------------------
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-04-27 18:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-26 13:10 Jean-Baptiste Rouquier
2004-04-27 18:11 ` Richard Jones [this message]
2004-04-27 19:13   ` David Brown
2004-04-27 21:53   ` Jean-Baptiste Rouquier
2004-04-30  0:13 ` Sylvain LE GALL

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=20040427181139.GA4496@redhat.com \
    --to=rich@annexia.org \
    --cc=caml-list@inria.fr \
    --cc=jean-baptiste.rouquier@ens-lyon.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).