From: Jean-Baptiste Rouquier <jean-baptiste.rouquier@ens-lyon.org>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: Re: [Caml-list] module / directory tree OR #include for camp4
Date: Tue, 27 Apr 2004 23:53:42 +0200 [thread overview]
Message-ID: <408ED666.6030602@ens-lyon.org> (raw)
In-Reply-To: <20040427181139.GA4496@redhat.com>
>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 ...
>
>
Yes. But this would imply that line.ml (or part1.frag) is
module Line = struct
...
end
which is against the file <-> module correspondence (compiling line.ml
would produce a module Line.Line).
I think I will have a small file plot.ml like
module Line : sig #include "plot/line.mli" end = struct #include
"plot/line.ml" end
module Bar ...
with a small preprocessor providing an #include directive. So I will
keep the plot/* files compilable with -pack.
Hoping better module/file tree will be provided in future releases!
Thanks,
--
Jean-Baptiste Rouquier
http://perso.ens-lyon.fr/jean-baptiste.rouquier
-------------------
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
next prev parent reply other threads:[~2004-04-27 21:52 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
2004-04-27 19:13 ` David Brown
2004-04-27 21:53 ` Jean-Baptiste Rouquier [this message]
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=408ED666.6030602@ens-lyon.org \
--to=jean-baptiste.rouquier@ens-lyon.org \
--cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).