From: octachron <octa@polychoron.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCaml release 4.04.2
Date: Fri, 23 Jun 2017 21:53:51 +0200 [thread overview]
Message-ID: <e8869b67-0bad-0b7c-dcef-cf7513beac54@polychoron.fr> (raw)
In-Reply-To: <CAPFanBF-3X4XioSJcYEadsd4=e0MXuXt4zk3uV164GFVULmsWw@mail.gmail.com>
Unfortunately, the C runtime plugin feature is still woefully
undocumented currently. The recent documentation effort focused on
(ocaml) compiler plugins, of which the existence was very briefly
touched upon in previous version of the documentation but not really
documented. And the extended documentation for these compiler plugins
will indeed be only available in the 4.06 version of the manual (except
if we decide to backport these changes or make available an experimental
trunk version of the manual).
Le 23/06/2017 à 21:13, Gabriel Scherer a écrit :
> I agree, of course, that we should do a better job of documentation
> new features as they get merged and not after-the-fact. There was in
> fact documentation contributed after-the-fact by Florian Angeletti
> (with helpful reviews by Hezekiah M. Carty and Gabriel Radanne, that
> in generally has been doing excellent work in the past few years on
> improving the state of the manual and documentation.
>
> https://github.com/ocaml/ocaml/pull/1187
>
> (I think that this change to the documentation only exists in the the
> trunk version for now, so without explicit backporting it would only
> become available in the 4.06.0 manual).
>
next prev parent reply other threads:[~2017-06-23 19:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 15:18 Damien Doligez
2017-06-23 16:47 ` Alexey Egorov
2017-06-23 19:05 ` David Allsopp
2017-06-23 19:13 ` Gabriel Scherer
2017-06-23 19:53 ` octachron [this message]
2017-06-23 20:38 ` Hannes Mehnert
2017-06-23 21:18 ` Anil Madhavapeddy
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=e8869b67-0bad-0b7c-dcef-cf7513beac54@polychoron.fr \
--to=octa@polychoron.fr \
--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