caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Xavier Leroy <Xavier.Leroy@inria.fr>
To: Tom <tom.primozic@gmail.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Dynamic loading of bytecode
Date: Thu, 17 Aug 2006 13:48:01 +0200	[thread overview]
Message-ID: <44E45771.3090805@inria.fr> (raw)
In-Reply-To: <c1490a380608140821q497970cfr6a8f091ec73b19ef@mail.gmail.com>

> How can you load the whole module hiearchy (many modules, dependent on
> one another) with a single command in toploop?

You cannot.  However, you could build a .cma archive via a Makefile:

    ocamlc -a -o mylib.cma a.cmo b.cmo

and issue the toplevel command #load "mylib.cma", which will load both
module implementations at once.

- Xavier Leroy


  parent reply	other threads:[~2006-08-17 11:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-14 15:21 Tom
2006-08-14 15:42 ` [Caml-list] " David MENTRE
2006-08-17 11:48 ` Xavier Leroy [this message]
2006-08-18  1:15 ` Pietro Abate

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=44E45771.3090805@inria.fr \
    --to=xavier.leroy@inria.fr \
    --cc=caml-list@yquem.inria.fr \
    --cc=tom.primozic@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).