From: Alain Frisch <alain@frisch.fr>
To: Philippe Veber <philippe.veber@gmail.com>
Cc: Gabriel Scherer <gabriel.scherer@gmail.com>,
Leo P White <lpw25@cam.ac.uk>, caml <caml-list@inria.fr>
Subject: Re: [Caml-list] [ANN] ocamlopen 1.0.2
Date: Thu, 12 Apr 2012 16:29:16 +0200 [thread overview]
Message-ID: <4F86E6BC.7070706@frisch.fr> (raw)
In-Reply-To: <CAOOOohRd5jGiVJkwhWcsji3cRw=vG_GDt9yg1daZPbdggxaZeQ@mail.gmail.com>
On 04/12/2012 04:16 PM, Philippe Veber wrote:
> Isn't this a good use case for polymorphic variants too ?
I don't see how to use polymorphic variants here. The message bus
itself need to provide functions like:
val dispatch: message -> unit
val register_listener: (message -> unit) -> unit
How do you define the message type without having access to all possible
message constructors?
-- Alain
next prev parent reply other threads:[~2012-04-12 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 21:13 Leo P White
2012-04-12 12:56 ` Gabriel Scherer
2012-04-12 14:03 ` Alain Frisch
2012-04-12 14:16 ` Philippe Veber
2012-04-12 14:29 ` Alain Frisch [this message]
2012-04-17 10:02 ` Philippe Veber
2012-04-12 17:07 ` Leo P White
2012-04-12 17:21 ` Alain Frisch
2012-04-12 20:31 ` Leo P White
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=4F86E6BC.7070706@frisch.fr \
--to=alain@frisch.fr \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=lpw25@cam.ac.uk \
--cc=philippe.veber@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).