From: David Fox <david.fox@linspire.com>
To: Xavier Leroy <Xavier.Leroy@inria.fr>
Cc: skaller <skaller@users.sourceforge.net>, caml-list@inria.fr
Subject: Re: [Caml-list] PIC
Date: Sat, 31 Dec 2005 13:31:27 -0800 [thread overview]
Message-ID: <43B6F8AF.6010807@linspire.com> (raw)
In-Reply-To: <43B1116C.5060407@inria.fr>
Xavier Leroy wrote:
>Dynamic loading of OCaml code from OCaml code raises many other
>issues. It is currently supported for bytecode only, and will not be
>available for native code in the forseeable future. I have already
>discussed this on this list earlier.
>
>
I can seem to locate this discussion - do you remember any keywords I
might search for?
next prev parent reply other threads:[~2005-12-31 21:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-25 2:07 PIC skaller
2005-12-27 10:03 ` [Caml-list] PIC Xavier Leroy
2005-12-27 12:23 ` skaller
2005-12-28 9:14 ` Sven Luther
2005-12-31 21:31 ` David Fox [this message]
2006-01-01 10:49 ` Ker Lutyn
2006-01-03 23:27 ` Nathaniel Gray
2006-01-04 2:38 ` skaller
2006-01-04 4:54 ` Nathaniel Gray
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=43B6F8AF.6010807@linspire.com \
--to=david.fox@linspire.com \
--cc=Xavier.Leroy@inria.fr \
--cc=caml-list@inria.fr \
--cc=skaller@users.sourceforge.net \
/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).