Fixed Windows compilation errors and memory leak

Fixed Windows compilation errors introduced by https://github.com/zeromq/aziomq/pull/8
and memory leak discussed in https://github.com/zeromq/aziomq/pull/9#discussion-diff-20735727
Agreed. Before I substantially rewrote the aziomq, I provided a callback
based mechanism that passed zmq_event_t and a asio::const_buffer for each
event. I plan on re-adding this functionality once I finish up support for
actors (ala zactor from CZMQ, but as stackless coroutines) as a monitor
actor type. My plan was to put event_t into the public interface as part of
those changes.

On Mon, Nov 24, 2014 at 5:47 PM, Andrey Upadyshev <notifications@github.com>
wrote:

> In test/socket/main.cpp:
>
> >
> >      monitor_handler(boost::asio::io_service & ios, aziomq::socket& s)
> >          : socket_(s.monitor(ios, ZMQ_EVENT_ALL))
> >      { }
> >
> >      boost::asio::mutable_buffer buffer() {
> > -        return boost::asio::buffer(&event_, sizeof(event_t));
> > +        return boost::asio::buffer(&event_, sizeof(zmq_event_t));
>
> Looks like event_t should be placed in AzioMQ header because this struct
> will be needed for every user of monitor...
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/zeromq/aziomq/pull/12/files#r20832606>.
>