Matt,

> I'm not even going to _suggest_ a setctxopt() that lets you decide on
> the fly :-)
>
>       setctxopt(ctx, ZMQ_SIGRET, sigvec[], unsigned num_sigs);  // not a
> pun on "cigarette"

The solution is not incorrect per se. It's the Microsoft way: "If 
feature X behaved this way in Win3.1 it should behave same way in all 
future version of Windows so that existing applications won't break. If 
there are two different mutually exclusive behaviours add an option to 
switch between them."

Which kind of works in short run, however, ultimately it leads to system 
with API and semantics as monstrous as those to be found on modern 
Windows systems.

Martin
_______________________________________________
zeromq-dev mailing list
[email protected]
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Reply via email to