caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Vu Ngoc San <san.vu-ngoc@laposte.net>
To: Jonathan Roewen <jonathan.roewen@gmail.com>
Cc: Caml Mailing List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] mixing dynlink & toplevel...
Date: Mon, 28 Aug 2006 11:41:34 +0200	[thread overview]
Message-ID: <44F2BA4E.4000103@laposte.net> (raw)
In-Reply-To: <ad8cfe7e0608271830t65a3e2f7ke4e5195046b1f4a7@mail.gmail.com>

By the way, is there somewhere a doc for toplevellib ? It is not in the
"official" ocaml manual, and, googgleing a little bit, I could not find
anything.

Best
San

Jonathan Roewen a écrit :
> Well, I've solved my own problem. Mind you, I am known for doing
> things that are not expected/thought of...
> 
> Turns out it was a double initialisation problem as dynlink &
> toplevellib share some modules.
> 
> On 8/28/06, Jonathan Roewen <jonathan.roewen@gmail.com> wrote:
>> > Hi,
>> >
>> > I dunno if this is possible, but: if I use Dynlink, can I later load
>> > toplevellib.cma, and use it like normal? At the moment I get undefined
>> > reference to global 'Toploop'.
>> >
>> > Jonathan
>>
>> I've just made a small test case to demonstate:
>>
>> test.ml:
>> open Dynlink
>>
>> let () = try
>>  print_endline "init";
>>  Dynlink.init ();
>>  print_endline "allowing unsafe modules";
>>  Dynlink.allow_unsafe_modules true;
>>  print_endline "loading toplevellib.cma";
>>  Dynlink.loadfile "/usr/local/lib/ocaml/toplevellib.cma";
>>  print_endline "loading topstart.cmo";
>>  Dynlink.loadfile "/usr/local/lib/ocaml/topstart.cmo";
>>  (* now the ocaml toplevel should be running *)
>> with Dynlink.Error error -> print_endline (Dynlink.error_message error);;
>>
>> To compile: ocamlc -o test -linkall dynlink.cma test.ml
>>
>> Running:
>> colinux:~/test# ./test
>> init
>> allowing unsafe modules
>> loading toplevellib.cma
>> loading topstart.cmo (shouldn't return)
>>        Objective Caml version 3.09.2
>>
>> # let s = "hello world";;
>> Reference to undefined global `Toploop'
>> # exit 0;;
>> colinu:~/test#
>>
>> As you can see, it can run functions fine (e.g. calling
>> Pervasives.exit), but let bindings fail.
>>
>> I know that a module loaded via Dynlink.loadfile can call functions
>> defined by other modules loaded by Dynlink.loadfile before it (I
>> actually do this), so why can't the toplevel access these? It can only
>> access those of the original program from my testing.
>>
>> Jonathan
>>
> 
> _______________________________________________
> Caml-list mailing list. Subscription management:
> http://yquem.inria.fr/cgi-bin/mailman/listinfo/caml-list
> Archives: http://caml.inria.fr
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
> 



  reply	other threads:[~2006-08-28  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-26 23:47 Jonathan Roewen
2006-08-27 21:08 ` Jonathan Roewen
2006-08-28  1:30   ` Jonathan Roewen
2006-08-28  9:41     ` Vu Ngoc San [this message]
2006-08-28  9:49       ` Jonathan Roewen
2012-07-10 11:22     ` [Caml-list] " Hongbo Zhang
2012-07-10 11:32     ` [Caml-list] " Hongbo Zhang

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=44F2BA4E.4000103@laposte.net \
    --to=san.vu-ngoc@laposte.net \
    --cc=caml-list@yquem.inria.fr \
    --cc=jonathan.roewen@gmail.com \
    /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).