From: Richard Jones <rich@annexia.org>
To: caml-list@inria.fr
Subject: [Caml-list] Why not 'include' in an .mli file?
Date: Wed, 14 Apr 2004 17:41:48 +0100 [thread overview]
Message-ID: <20040414164148.GA18109@redhat.com> (raw)
I have a library which for various reasons is split into two modules,
called them Analysis_p and Analysis.
I want end-user programs to be able to 'open Analysis', and get all
the symbols from both modules. This is simple enough using the
'include' directive:
analysis.ml: include Analysis_p
(* plus a few extra functions *)
However when I added an analysis.mli file, I found that I could not
automatically 'include' symbols from Analysis_p. The following
doesn't work:
analysis.mli: include Analysis_p
(* plus a few extra prototypes *)
ocamlc -w s -g -I +pcre -I +postgres -I +dbi -c analysis.mli
File "analysis.mli", line 1, characters 8-24:
Unbound module type Analysis_p
Instead it seems, as far as I can see, that I have to list out all the
prototypes again in analysis.mli. Is this so? If so, it's a pain for
me, and means that prototypes for one function exist in two different
places (also I don't control Analysis_p directly, so it requires extra
coordination).
Rich.
--
Richard Jones. http://www.annexia.org/ http://www.j-london.com/
Merjis Ltd. http://www.merjis.com/ - improving website return on investment
MAKE+ is a sane replacement for GNU autoconf/automake. One script compiles,
RPMs, pkgs etc. Linux, BSD, Solaris. http://www.annexia.org/freeware/makeplus/
-------------------
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 reply other threads:[~2004-04-14 16:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-14 16:41 Richard Jones [this message]
2004-04-14 16:52 ` Markus Mottl
2004-04-15 19:43 ` Christopher Quinn
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=20040414164148.GA18109@redhat.com \
--to=rich@annexia.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).