From: Matt Gushee <mgushee@havenrock.com>
To: caml-list@pauillac.inria.fr
Subject: [Caml-list] Toplevel & library conflicts
Date: Sun, 15 Jun 2003 13:09:00 -0600 [thread overview]
Message-ID: <20030615190900.GA23999@swordfish> (raw)
Hello, everyone--
I have an issue with name conflicts in libraries. I am working on an
application that uses both Mlgraph and Camlimages; in general, it will
render drawings in PostScript and then convert them to PNG. But both
Mlgraph and Camlimages have modules named Geometry, so if I simply try
to load both libraries in the toplevel, I get an error message saying
that
File /opt/ocaml-3.06/lib/ocaml/mlgraph.cma is not up-to-date with \
respect to interface Geometry
Now, I understand that if I am compiling a program, I can create
separate compilation units that isolate the functions calling on the two
different libraries; in fact I successfully compiled a small test
program that way a couple of days ago. But that's not what I want to do
at the moment. Right now I am trying to build up a set of modules
gradually and test them interactively.
Can anyone suggest a good way to handle the name conflict when using the
toplevel?
Thanks in advance.
--
Matt Gushee When a nation follows the Way,
Englewood, Colorado, USA Horses bear manure through
mgushee@havenrock.com its fields;
http://www.havenrock.com/ When a nation ignores the Way,
Horses bear soldiers through
its streets.
--Lao Tzu (Peter Merel, trans.)
-------------------
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:[~2003-06-15 19:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-15 19:09 Matt Gushee [this message]
2003-06-15 19:28 ` Never mind (was Re: [Caml-list] Toplevel & library conflicts) Matt Gushee
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=20030615190900.GA23999@swordfish \
--to=mgushee@havenrock.com \
--cc=caml-list@pauillac.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).