Now I’m confused - although there’s nothing new about that .
Are you sure that you are printing out the state variable, and not something from within the WIP DEBUG system? I’ve found that the values output by WIP DEBUG DO NOT match up with the error numbers in the API guide…
I’ve been observing such a behaviour through a number of WIP plugin versions.
Return value sometimes is unpredictable and not in enum range.
I presume this happens due to call wip_getState() for closed/not valid socket handle.
If this is the case, I do not understand why special enum value for such state was not implemented
Actually you should have not been mentioned ADL errors because wip_getState() function declared to return one of predefined values - enum wip_cstate_t
Instead of implementing deterministic behaviour of WIP functions sometimes there are notes in WIP development guide that being called for closed/invalid handles function might behave in unpredictable way