OK, I've made a pull request for this: https://github.com/zeromq/libzmq/pull/1096.
I think this will be a nice improvement. There may be other cases where we can assert instead of returning EINVAL. The change also makes me think we could add a probe API to allow applications and bindings to probe how libzmq was built. On Tue, Jun 17, 2014 at 3:40 PM, Pieter Hintjens <[email protected]> wrote: > On Tue, Jun 17, 2014 at 2:01 PM, Thomas Rodgers <[email protected]> wrote: > >> By debug/checked build, I meant build-time option. > > Indeed. I'm making a --with-militant option for libzmq's configure. > >> I'll admit though it is a somewhat academic argument on my part. For aziomq >> (https://github.com/aziomq/aziomq4-x) I've gone the route of making options >> type safe, so the asserts would act as a back stop on me screwing up the >> type parameters when I declared my option types. > > Same in CZMQ. In fact the one case where a random error on > zmq_setsockopt was hitting (a painful and costly bug in Zyre) was when > I bypassed CZMQ and went to the libzmq API directly. > > -Pieter _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
