Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: Berke Durak <berke.durak@exalead.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Using dynlink (native code and byte code) for the build system
Date: Thu, 31 Jan 2008 14:58:37 +0000	[thread overview]
Message-ID: <200801311458.38051.jon@ffconsultancy.com> (raw)
In-Reply-To: <47A1E250.8020608@exalead.com>

On Thursday 31 January 2008 14:59:28 Berke Durak wrote:
> Jon Harrop a écrit :
> > On Thursday 31 January 2008 14:49:44 Alain Frisch wrote:
> >> Berke Durak wrote:
> >>> Thank to Alain Frisch's natdynlink, it is now possible to dynamically
> >>> load native code plugins.
> >>
> >> Only on some platforms! Please don't make the availability of exotic
> >> features mandatory for the build system to work.
> >
> > FWIW, I think natdynlink should be a core feature of OCaml going forwards
> > because it is useful in so many circumstances
>
> I agree.  However such a build system will also work with bytecode, albeit
> at lower performance, on platforms not supporting natdynlink.  A build
> system is also not computationally too intensive, so it should be OK.

Good point. AMD64 gives far better performance than all other platforms anyway 
(AFAIK) so people should be using that if they want good performance anyway.

>  > not least the performant top-level.
>
> Natdynlink in the toplevel??

Alain wrote "ocamlnat", an OCaml top-level that uses compilation to native 
code (with dynamic linking) to provide performance competitive with other 
languages like Lisp and F#. I found this extremely useful for the few months 
that I used it, although it was a little buggy.

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/products/?e


  reply	other threads:[~2008-01-31 15:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 10:02 Berke Durak
2008-01-31 14:49 ` [Caml-list] " Alain Frisch
2008-01-31 14:48   ` Jon Harrop
2008-01-31 14:59     ` Berke Durak
2008-01-31 14:58       ` Jon Harrop [this message]
2008-01-31 16:46     ` Alain Frisch
2008-02-01 16:21       ` Jon Harrop

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=200801311458.38051.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --cc=berke.durak@exalead.com \
    --cc=caml-list@inria.fr \
    /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