On Friday, 24 January 2014 at 19:20:26 UTC, Justin Whear wrote:
Now that I think of it, you also need to find a scheme for
indicating
which events you want to listen for. Which means either a
simple pairing
type (socket, event mask) or a getopt-style interface.
I have suggested a few
∅MQD is a D library that wraps the low-level C API of the ∅MQ
messaging framework. It is a rather thin wrapper that maps
closely to the C API, while making it safer, easier and more
pleasant to use. The API is designed to feel familiar to
existing ∅MQ users, yet natural to D users.
For
On Fri, 24 Jan 2014 17:45:44 +, Lars T. Kyllingstad wrote:
∅MQD is a D library that wraps the low-level C API of the ∅MQ messaging
framework. It is a rather thin wrapper that maps closely to the C API,
while making it safer, easier and more pleasant to use. The API is
designed to feel
On Friday, 24 January 2014 at 18:59:54 UTC, Justin Whear wrote:
Nicely done. It looks like you haven't wrapped the poll
functionality at
all, something that I use in most of my 0MQ programs.
Thanks! I'm glad that you mention zmq_poll(); I've been
wondering how to deal with that. It's
On Fri, 24 Jan 2014 19:11:56 +, Lars T. Kyllingstad wrote:
On Friday, 24 January 2014 at 18:59:54 UTC, Justin Whear wrote:
Nicely done. It looks like you haven't wrapped the poll functionality
at all, something that I use in most of my 0MQ programs.
Thanks! I'm glad that you mention
