added a few warnings to figure out a bug
removed close/DESTROY because it seems to cause an infinite loop???
re-enabled close method
Merge branch 'master' of devbox.vpn.validad.net:ZMQx-Class
wip (RT63106_Building_deb_for_0mq_4)
more little things to move to ffi
ZMQx::Class for ZMQ::FFI module

Updated to use ZMQ::FFI, test t/10_zmq_class.t all tests success
 (RT63106_Building_deb_for_0mq_4)
remove helper api methods (RT63106_Building_deb_for_0mq_4)
clean up test comments
 (RT63106_Building_deb_for_0mq_4)
Call the correct ->socket
 (RT63106_Building_deb_for_0mq_4)
router req test (ffi)
Create a proper test case showing the UTF-8 / zmq issue

Perl / zmq4 / ffi is having issues (currently) having issues with unicode strings. This test exposes the issue and we can work on it's solution
 (RT63420_ZMQx_Class_Unicode_safe)
ZMQx::Class receive_string methods

The Python lib for zmq implements receive_string for obvious reasons. I like
the approach and have added the receive_string() to ZMQx::Class::Socket. It is
possible to use encodings other than 'utf8' but it will be slower.

beware!! we're using Encode::_utf8_on for 'upgrading' the strings. This is
evil (but fast).
 (RT63420_ZMQx_Class_Unicode_safe)
Merge branch 'RT63420_ZMQx_Class_Unicode_safe'
Update send() to reflect the (non-)return value from ZMQ::FFI::send().

ZMQ::LibZMQ3() is documented to return the number of bytes sent (which is the
return value from the underlying zmq_msg_send() C library call).
ZMQ::FFI::send() is not documented to return anything in particular, and will
throw an exception if the C library call returns -1 for error.

The code in ZMQx::Class was relying on the ZMQ::LibZMQ3 behaviour, and getting
caught out if ZMQ::FFI::send() happened to return a false value.

For now, ignore the return value of ZMQ::FFI::send() and send_multipart(), and
continue to honour our documented return value (the length of the message) by
using the value passed in.

It's unclear if this is the best long term fix.
Improve how ZMQx::Class::Socket::send() calculates the length that it returns.

It now always returns the total number of bytes sent, summing the lengths for
multipart messages.
Merge branch 'master' of devbox.vpn.validad.net:ZMQx-Class
Add a send_bytes method, for when you really need to send raw bytes.

Useful for sending multi-part messages with ZMQ routing information.
pyzmq has both byte and string send functions, and it turns out we need them
too.
Ensure that send() always passes strings as sequences of UTF-8 to ZMQ::FFI

ZMQ::FFI intentionally deals only in bytes, but isn't (yet) robust at enforcing
this. So we need to ensure that what we pass to it are scalars containing only
bytes, and manage the conversion from strings as Unicode ourselves.
Merge branch 'master' of devbox.vpn.validad.net:ZMQx-Class