From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Kenneth Adam Miller <kennethadammiller@gmail.com>
Cc: caml users <caml-list@inria.fr>
Subject: Re: [Caml-list] Utop Difficulties with C callbacks
Date: Fri, 20 Mar 2015 16:02:59 +0100 [thread overview]
Message-ID: <4895487FAC0C45A6AEDB397422528A2C@erratique.ch> (raw)
In-Reply-To: <CAK7rcp9N_UqLT5XGrTDmUbDt=s77DJ1x2g5x02BJ=EOT0UsLZA@mail.gmail.com>
Le vendredi, 20 mars 2015 à 15:51, Kenneth Adam Miller a écrit :
> Sorry Daniel, I should have done even more homework.
No problem, this was not a criticism. It's just that sometimes being insulated from the details by our build systems, meta-build systems and other ocamlfinds we forget about the underlying basic utilities and the fact that those are quite well documented.
Best,
Daniel
prev parent reply other threads:[~2015-03-20 15:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 18:19 Kenneth Adam Miller
2015-03-19 19:01 ` Jeremie Dimino
2015-03-19 19:33 ` Kenneth Adam Miller
2015-03-19 21:36 ` Kenneth Adam Miller
2015-03-20 9:43 ` Jeremie Dimino
2015-03-20 9:57 ` Daniel Bünzli
2015-03-20 14:51 ` Kenneth Adam Miller
2015-03-20 15:02 ` Daniel Bünzli [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=4895487FAC0C45A6AEDB397422528A2C@erratique.ch \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=kennethadammiller@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;
as well as URLs for NNTP newsgroup(s).