What steps will reproduce the problem?
1. Compare a numeric value to a non-numeric value (e.g. 5 != nil)
What is the expected output? What do you see instead?
Expected output is <true>, while in the example, nil is implicitly coerced to a
numeric value (to
match the ATNumeric argument type expected by the equality and inequality tests
in the
ATNumeric interface). Subsequently, a selector not found exception is thrown
since nil does not
implement the necessary methods used in the double dispatch to compare numbers.
Please use labels and text to provide additional information.
A fix for this problem has been made in the reactive branch, rev. 1418
Original issue reported on code.google.com by smost...@gmail.com on 22 Nov 2008 at 8:45
Original issue reported on code.google.com by
smost...@gmail.com
on 22 Nov 2008 at 8:45