On Oct 6, 2010, at 6:51 AM, Wolfgang Sourdeau wrote: >> 2010-10-06 10:41:55.165 sogod[4534] WARNING(-[NSNull(misc) length]): called >> NSNull -length (returns 0) !!! >> 2010-10-06 10:41:55.165 sogod[4534] WARNING(-[NSNull(misc) length]): called >> NSNull -length (returns 0) !!! >> 2010-10-06 10:41:55.165 sogod[4534] WARNING(-[NSNull(misc) length]): > > As explained many times already, this can be safely ignored. We cannot do > much about it as this is generated by GNUstep.
Thats incorrect, this is generated by a category in SOPE. It points out an issue with NSNull not being properly used in higher layers (essentially NSNull should only live in generic collections, if its retrieved via KVC, it should be replaced with nil. Hence in regular code you would never send arbitrary messages to NSNull). You can get rid of that by removing the respective methods in SOPE/NSObject+misc. (but that doesn't solve the core issue, which should be fixed instead ...) hh -- [email protected] https://inverse.ca/sogo/lists
