Version française
Home     About     Download     Resources     Contact us    
Browse thread
[Caml-list] Toplevel & library conflicts
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Matt Gushee <mgushee@h...>
Subject: [Caml-list] Toplevel & library conflicts
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