Thrown exceptions when operations are not supported due to versions about jzmq HOT 4 CLOSED

No good reason really. The 0MQ Java binding has always been a very shallow wrapper, so whatever is returned from 0MQ we tend to do the same. You could also argue that exceptions might be too expensive for high-performance 0MQ code.

Anyway, if you feel strongly about this, I would suggest you bring it up on the 0MQ mailing list and see what others think.

from jzmq.

Hi gonzus,

I've made the question here

Patrick

from jzmq.

I guess the key here is to be consistent. There are a couple of options one can take in this case.

• Like what was suggested, throw an UnsupportedOperationSuggestion for features that aren't supported in the version of libzmq
• Maintain two builds of the latest stable releases; 2.2 and 3.2
• Return -1

Thoughts?

from jzmq.

Closing because this issue is 2 years old

from jzmq.