From: orbifx <fox@orbitalfox.eu>
To: "Ali M." <tclwarrior@gmail.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Introspection of functions with Utop
Date: Fri, 24 Apr 2020 17:05:23 +0100 [thread overview]
Message-ID: <3ab1f224-dfce-9496-6570-c518cb367008@orbitalfox.eu> (raw)
In-Reply-To: <CA+ftKJ6jdvtDUJQj11bvDGHDiqd-58c2W6W_J29m6gcj+pZeoQ@mail.gmail.com>
On 21/04/2020 15:08, Ali M. wrote:
> I would suggest to also ask this question on the discourse forum
> https://discuss.ocaml.org/
> You might get better interaction
Thank you. I prefer the mailing list directly. I was given an answer on this by Alan in the XMPP room[1] for OCaml.
[1]: xmpp:ocaml@conference.orbitalfox.eu?join
next prev parent reply other threads:[~2020-04-24 16:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 11:40 orbifx
2020-04-21 14:08 ` Ali M.
2020-04-24 16:05 ` orbifx [this message]
2020-04-25 6:43 ` Malcolm Matalka
2020-04-25 13:12 ` Alan Schmitt
2020-04-25 13:37 ` Basile Starynkevitch
2020-04-27 16:11 ` Josh Berdine
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=3ab1f224-dfce-9496-6570-c518cb367008@orbitalfox.eu \
--to=fox@orbitalfox.eu \
--cc=caml-list@inria.fr \
--cc=tclwarrior@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).