jaeheum / qzmq Goto Github PK

current interface of returning exception feels awkward.

For the 0MQ Guide as examples are going to be included therein.

For both API and users guide.

Either rewrite it or pair with free() as the owner of the pointer.

Just curious. Looks like zthread.fork is also gone. I can't find the rationale in the repo for removing them.

Consider the following trivial example:

\l qzmq.q

ctx:zctx.new[]
socket:zsocket.new[ctx; zmq`DEALER]
zsocket.bind[socket; `$"tcp://*:9001"]
zsocket.destroy[ctx; socket]
zctx.destroy[ctx]
\\

This works fine, and you will see the port number printed out to the q console which indicates that the port bound properly. Now notice if you add a semicolon after the bind line:

\l qzmq.q

ctx:zctx.new[]
socket:zsocket.new[ctx; zmq`DEALER]
zsocket.bind[socket; `$"tcp://*:9001"];
zsocket.destroy[ctx; socket]
zctx.destroy[ctx]
\\

Now the bind does not occur. I'm still pretty new to q, but as far as I can tell semicolons shouldn't affect the calls of functions.

BTW this is KDB+ 2.7 2011.03.23 if that helps at all.

need to finish translations of examples http://zguide.zeromq.org/page:all

Because symbols are interned strings, they don't GCed. Symbols are nice in that there can be no accidental mutation but come at a high cost of memory leak.

zmq_pollitem_t handling will be less than pretty -- which is why documentation needs to be written.

add devices support in libzmq api

https://raw.github.com/zeromq/czmq/master/NEWS

qzmq needs a more sensible build/integration mechanism to cover different platforms/versions of kdb+, ØMQ and CZMQ.

e.g. xt==-10h, yt==KC, yt==KG, etc. so that wrong types do not propagate downward to unsuspecting library.