From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Jeremie Dimino <jdimino@janestreet.com>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
caml-list <caml-list@inria.fr>,
Thomas Refis <thomas.refis@gmail.com>
Subject: Re: [Caml-list] ocamlnat
Date: Wed, 13 Jul 2016 14:22:37 +0200 [thread overview]
Message-ID: <1468412557.25014.111.camel@e130.lan.sumadev.de> (raw)
In-Reply-To: <CANhEzE4rp=9GvwtJ6_yexOw5FOitWHnXOY6fB4whV68Z8-3KRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3335 bytes --]
Thanks for the info. I'll also copy that code to my separate repository,
so that everybody can easily start experimenting with it. I keep you
posted on what we find.
Gerd
Am Mittwoch, den 13.07.2016, 10:50 +0100 schrieb Jeremie Dimino:
> ocamlnat indeed builds with 4.03 but is not built by default
>
> On Tue, Jul 12, 2016 at 11:28 PM, Gabriel Scherer
> <gabriel.scherer@gmail.com> wrote:
> Thomas Réfis and Jérémie Dimino have been working on ocamlnat
> in trunk recently, and ocamlnat builds on either the "trunk"
> branch or, I believe, the 4.03 release. You should talk to
> them.
>
>
> Let me take this an opportunity to advertise the "runtop"
> target in the compiler distribution's Makefile, which runs a
> toplevel from an (uninstalled) build of the compiler
> distribution:
>
>
> make runtop
>
> make natruntop
>
>
> I added them during the 4.03+dev release cycle, but didn't
> mention it in the Changelog (they're not user-facing features)
> so most people keep doing weird incantations of
> (./byterun/ocamlrun ./ocaml -I nostdlib ...) instead.
>
>
> On Tue, Jul 12, 2016 at 5:39 PM, Gerd Stolpmann
> <info@gerd-stolpmann.de> wrote:
> Hi,
>
> I've tried to reactivate the ocamlnat tool that comes
> with OCaml but
> isn't built (and even isn't buildable). This repo was
> tested against
> 4.02.3:
>
> https://gitlab.camlcity.org/gerd/ocamlnat
>
> Since recently I'm quite interested in this, and would
> like to make it
> fully working, including ocamlfind support. For my use
> case the
> disadvantages of the ocamlnat approach (i.e. that it
> requires toolchain
> support for dynlinking, and that the executable
> continuously grows) do
> not matter - I really want it for interactive work,
> and not for
> scripting.
>
> Gerd
> --
> ------------------------------------------------------------
> Gerd Stolpmann, Darmstadt, Germany
> gerd@gerd-stolpmann.de
> My OCaml site: http://www.camlcity.org
> Contact details:
> http://www.camlcity.org/contact.html
> Company homepage: http://www.gerd-stolpmann.de
> ------------------------------------------------------------
>
>
>
>
>
>
>
> --
> Jeremie
--
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany gerd@gerd-stolpmann.de
My OCaml site: http://www.camlcity.org
Contact details: http://www.camlcity.org/contact.html
Company homepage: http://www.gerd-stolpmann.de
------------------------------------------------------------
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2016-07-13 12:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 21:39 Gerd Stolpmann
2016-07-12 22:28 ` Gabriel Scherer
2016-07-13 9:50 ` Jeremie Dimino
2016-07-13 12:22 ` Gerd Stolpmann [this message]
2016-07-13 13:45 ` Fabrice Le Fessant
2016-07-14 19:26 ` Sébastien Hinderer
2016-07-15 14:47 ` Gerd Stolpmann
2016-07-18 8:14 ` Sébastien Hinderer
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=1468412557.25014.111.camel@e130.lan.sumadev.de \
--to=info@gerd-stolpmann.de \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=jdimino@janestreet.com \
--cc=thomas.refis@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