From: Michal Moskal <malekith@pld-linux.org>
To: "Jeffrey J. Cook" <jjcook@uiuc.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] code duplication when abstracting using explicit signatures
Date: Sat, 22 Mar 2003 13:07:10 +0100 [thread overview]
Message-ID: <20030322120710.GA16956@roke.freak> (raw)
In-Reply-To: <20030320233234.GA17684@crhc.uiuc.edu>
On Thu, Mar 20, 2003 at 05:32:34PM -0600, Jeffrey J. Cook wrote:
> I'm trying to avoid code duplication, but have a very simple case where it
> seems inescapable utilitizing only the functionality of the ocaml tools. In
> example.mli, I declare several large types, in which I want the full contents
> of the types to be visible to other modules. How do I avoid duplicating those
> full definitions in example.ml? I've tried using "include Example" at the
> beginning of example.ml, which ocamlopt has no argument with, but ocamlc gives:
>
> Error while linking example.cmo: Reference to undefined global `Example'
>
>
> I can't simply skip the .mli, as there are functions in example.ml that
> I don't want exported; not to meantion the clean-ness of seperation .mli's
> provide. Any suggestions?
Use example_types.mli and example.ml/mli. AFAIR you can only put types
in example_types, not even exceptions.
--
: Michal Moskal ::::: malekith/at/pld-linux.org : GCS {C,UL}++++$ a? !tv
: PLD Linux ::::::: Wroclaw University, CS Dept : {E-,w}-- {b++,e}>+++ h
-------------------
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:[~2003-03-22 12:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-20 23:32 Jeffrey J. Cook
2003-03-22 12:07 ` Michal Moskal [this message]
2003-03-23 0:52 ` brogoff
2003-03-23 9:58 ` Christian Lindig
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=20030322120710.GA16956@roke.freak \
--to=malekith@pld-linux.org \
--cc=caml-list@inria.fr \
--cc=jjcook@uiuc.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).