API Unification

[chloe-zen]

The differences between zmq2 and zmq3 could be effectively papered over by providing a superset of the APIs down at the ZMQ level. For example, sendmsg and recvmsg can easily be made to work on ZMQ::Socket using both underlying libraries.

Are you open to this kind of change?

Also, error reporting would be Much Nicer if either $! integration were more advanced or zmq_strerror was exposed via the base ZMQ. Or both.

[lestrrat]

Open to the idea, yes. I'd have to say I just don't know what would be the correct API names would be, because I don't trust for a second (at this moment, anyway) that send/recv or some other function name/semantics would change in libzmq4 or whatever future versions.

WRT to $!, don't know what you mean by "advanced". any pseudocode?

WRT to zmq_strerror, I guess functions like zmq_strerror/zmq_version can be exported the same way, but I guess this also falls on "what shall be the naming convention?" category. Proposals welcome.