Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Cc: Jean-Marc EBER <jeanmarc.eber@lexifi.com>
Subject: Re: [Caml-list] [OSR] Caml Community Code
Date: Mon, 4 Feb 2008 17:35:00 +0000	[thread overview]
Message-ID: <200802041735.00819.jon@ffconsultancy.com> (raw)
In-Reply-To: <47A72295.9080907@lexifi.com>

On Monday 04 February 2008 14:35:01 Jean-Marc EBER wrote:
> Hi all,
>
> Without entering into a dialog on this list, LexiFi, whose name has been
> cited in this mail, wants to make the following clarification(s):

Thank you for clarifying.

> ...
> c. General purpose cleanups, small enhancements etc.: we inform Inria about
> them: Inria may or may not incorporate these patches.

This is exactly the work that I think we should be sharing and all benefitting 
from. I think everyone has reached an understanding on how beneficial this 
could be even if we disagree about how to achieve that goal.

> > . OCaml's top-level runs interpreted bytecode and, consequently, is many
> > times slower than the interactive sessions of "competing" language
> > implementations like SBCL (Lisp) and F#. Alain Frisch has already
> > implemented a native-code top-level for OCaml called "ocamlnat" in his
> > "natdynlink" fork of OCaml. I found this extremely useful and would like
> > it to be easier for other people to benefit from this work.
>
> Jon, please, be careful with your public statements here.
> The "natdynlink" branch (repeat after me, branch, _not_ fork) has been
> implemented by Alain Frisch when he was at Inria, with full knowledge of
> Xavier Leroy. The idea was that if this _branch_ worked, it was supposed to
> become mainstream; this is so true that it has been merged into... cvs HEAD
> !

Excellent! I was under the impression that ocamlnat was deleted in the merge 
but it appears to compile from the current CVS... :-)

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


  reply	other threads:[~2008-02-04 17:39 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-31 14:28 Jonathan Bryant
2008-01-31 16:25 ` [Caml-list] " blue storm
2008-01-31 20:53   ` Stefano Zacchiroli
2008-01-31 21:38     ` Jon Harrop
2008-02-01  8:13       ` Stefano Zacchiroli
2008-02-01  9:14         ` Jon Harrop
2008-02-01 13:56           ` Christopher L Conway
2008-02-01 15:50             ` Sylvain Le Gall
2008-02-01 18:07             ` [Caml-list] " Jon Harrop
2008-02-01 19:00               ` Jonathan Bryant
2008-02-01 19:49                 ` Vincent Hanquez
2008-02-01 20:41               ` Christopher L Conway
2008-02-04 14:35               ` Jean-Marc EBER
2008-02-04 17:35                 ` Jon Harrop [this message]
2008-01-31 17:47 ` Ashish Agarwal
2008-01-31 18:12   ` Jonathan Bryant
2008-02-01 17:26 ` David Allsopp
2008-02-01 18:27   ` Jonathan Bryant
2008-02-01 18:25     ` Jon Harrop
2008-02-03 12:21       ` David Teller
2008-01-31 15:57 Jonathan Bryant
2008-01-31 16:08 ` [Caml-list] " Romain Beauxis
2008-01-31 16:23   ` Jonathan Bryant

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=200802041735.00819.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=jeanmarc.eber@lexifi.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