Re: [PATCH] accept null selector for respondsTo...

[David Ayers]

Richard Frith-Macdonald wrote:

> 2. Support both behaviors, with the tolerant behavior the default and the
> exception raising behavior turned on by the existing GSMacOSXCompatible
> user default.

This would be my personal preference, as this would relieve other 
GNUstep Apps/Libraries/Frameworks/... of dealing with the "most recent 
API change" that Apple comes up with.  It might (or actually most likely 
will) lead to other GNUstep Apps/Libraries/Frameworks/... to break on 
most recent OS X releases more often, but I believe it is best to 
resolve these issues when the need arises (i.e. users actually ask for 
it) rather than when the core libraries happen to support the new OS X 
behavior.  If an App/Library/Framework/... is stable enough, that all it 
needs to do, is to track OS X, then this project maintainers just set 
the default and can go through thier tests and fix what ever they need 
to.  But I think that we shouldn't force *all* projects to update to the 
newest OS X API just to work with the current version of the core libraries.

Cheers,
Dave