[zeromq-dev] Types for options in [gs]etsockopt()

[Martin Sustrik]

On 10/04/2010 04:55 PM, gonzalo diethelm wrote:

>> Since it's an API change it would have to be done for 3.0 unless
>> there's consensus from binding maintainers that this counts as a
>> 'minor change' in which case it could go into 2.1 now.
>>
>> I'd see this going in 2.2.0.  It will cause warnings in a bunch
>> of existing code though it'll be easy to find and fix those.

The problem is that the change would be completely transparent. So the 
applications would just start crashing without reporting problems 
beforehand at the compile time.

> Ok, so one thing would be to decide exactly when to apply this "great
> rewrite of [gs]etsockopt changes".
>
> Another thing is to decide what to do with the current version. I guess
> I should modify the Java binding so that it will have several different
> cases, depending on the actual size for each given option... I don't
> really see any other way, given the ABI restrictions. Right?

Right.

Martin