[Xapian-discuss] Deprecation policy question

[Richard Boulton]

Olly Betts wrote:
> It's also worth noting that you can easily disable all Xapian
> deprecation warnings like the bindings do:
> 
> #define XAPIAN_DEPRECATED(D) D
> 
> That's not a documented feature, but we could document it, or perhaps
> better provide a "XAPIAN_NO_DEPRECATED_WARNINGS" macro the user can
> define which does this internally (in case we find we need to change
> how that macro works).  I think ideally we want the policy which API
> users find most useful, but if different people want different things,
> then this is one solution.

This suggests to me that we should follow my "option 1", and if people 
complain about the warnings, we can document and implement a 
"XAPIAN_NO_DEPRECATED_WARNINGS" macro.

If we really wanted to sit on the fence, we could also implement a 
"XAPIAN_NO_RECENT_DEPRECATED_WARNINGS" macro, which turns off warnings 
for features which have been deprecated in the current release series. 
But that's almost certainly more work than it's worth (especially 
considering that no-one has replied yet in favour of my option 3).

For the record, I'm currently thinking that option 1 is the way forward, 
but feel free to shout within the next day or so if you think 
differently (or the same).

-- 
Richard