While I highly doubt this is a GNUstep bug(I think the bug lies in the actual objective-c library), I have noticed that if you do a
[object respondsToSelector: 0] it will seg fault. Doing a backtrace, I see that its failing in __objc_responds_to(). Perhaps __objc_responds_to was specifically designed to not take 0 as an argument, in which case the bug lies with GNUstep where it should check to make sure its not zero, or the bug could simply be in the objective-c library. Regardless, the behavior should be returning NO, not seg faulting. -- Andy Ruder (Beregorn on #gnustep on irc.openprojects.net) __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com _______________________________________________ Bug-gnustep mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-gnustep
