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

[Pete French]

> > 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 

Doesnt this mean that you end up with some apps needing this enabled to run,
and others needing this disabled ? Thats incredibly frustrating for users
I would have thought.

> 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.

Agreed, but theres no harm in a small amount of ifdef's in life either on the
part of developers. Id prefer to know there was only one API on each system,
even if they happen to be different between the two, rather than having to
code either enforcing the behaviour or programming for both eventualities.

-bat.