You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This probably means that these problematic classes override handleUnknownMessage:withContext: and do not call super.
These classes include, but may not be limited to:
NuCell
NSNull
NSArray
I'll take a look at this myself, but I've created this ticket as a reminder, as I'll have to do a concise pass over the complete source to see what other classes might need to be fixed as well.
The text was updated successfully, but these errors were encountered:
However, the same ‘problem’ applies to NSDictionary, but I haven't been able to think of a way to make it work for that case. The problem is that sending an unknown symbol message which is also not a key in the dictionary currently returns nil, which is consistent with the valueForKey: behavior. I.e. This would be really confusing if this would suddenly return different values, or even raise an unknown handler exception.
Regarding NSNull, none of my naive attempts have allowed me to catch unknown messages.
This is because of the dummy NSObject handleUnknownMessage:withContext: method I defined in test_array.nu and test_list.nu. Will have to think about a better way to test it…
This probably means that these problematic classes override handleUnknownMessage:withContext: and do not call super.
These classes include, but may not be limited to:
I'll take a look at this myself, but I've created this ticket as a reminder, as I'll have to do a concise pass over the complete source to see what other classes might need to be fixed as well.
The text was updated successfully, but these errors were encountered: