caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Nathaniel Gray <n8gray@gmail.com>
To: skaller <skaller@users.sourceforge.net>
Cc: Ker Lutyn <ker527mail@yahoo.com>, caml-list@inria.fr
Subject: Re: [Caml-list] PIC
Date: Tue, 3 Jan 2006 20:54:45 -0800	[thread overview]
Message-ID: <aee06c9e0601032054l6fb41a82vb8641b0cca363fc3@mail.gmail.com> (raw)
In-Reply-To: <1136342332.17213.96.camel@rosella>

On 1/3/06, skaller <skaller@users.sourceforge.net> wrote:
> On Tue, 2006-01-03 at 15:27 -0800, Nathaniel Gray wrote:
>
> > Who wants to write an app without plugins these days?
>
> Who is willing to write applications that are unsound?
>
> Once Ocaml generates -fPIC it can be linked with a C wrapper
> to make a shared library, and your mainline (or another
> wrapped library) can embed a function that loads such
> libraries with dlopen() and retrieves a record of functions,
> then casts it to the expected type ..
> voila, you have native code plugins.

This could solve part of the problem, namely alleviating the need for
recompiling the app for each plugin the user adds.  However, given the
OCaml team's indifference towards binary compatibility, trying to keep
everybody on the same version of the compiler would be too restrictive
to be practical.

-n8

--
>>>-- Nathaniel Gray -- Caltech Computer Science ------>
>>>-- Mojave Project -- http://mojave.cs.caltech.edu -->


      reply	other threads:[~2006-01-04  4:54 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
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 [this message]

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=aee06c9e0601032054l6fb41a82vb8641b0cca363fc3@mail.gmail.com \
    --to=n8gray@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=ker527mail@yahoo.com \
    --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).