On Wednesday, August 28, 2002, at 10:21 AM, David Ayers wrote:
> Hello Richard, > > checking up on some of the added/changed implemtations in NSObject, I > noticed that GNUstep would behave differently than OPENSTEP 4.2 would > in some cases. I don't have an OS X to verify how it is implemented > there though. If OS42 and OS X differ in these implemetations, then it > would be nice to have #define guards OS 4.2 compatibility. The release notes for MacOS-X 10.2 say that they are now raising an exception wherever a null selector is passed ... except for NSStringFromSelector() I don't have a copy of the latest version of the OS, so I can't tell if the release notes are telling the truth, but it seems reasonable. As for the issue of compatibility with OPENSTEP4.2 ... I'm not sure that this is a particularly good idea - this is one of those cases where the change seems to me to be quite likely to expose bugs in the application source code, allowing you to fix them (ie the change seems to me to be a good thing). If/where, on the other hand, the OpenStep spec or documentation etc specifically states that you can use a null selector, I'd want to retain that capability (and simply have a debug warning logged). _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
