a.equals(b) works like a == b, i.e. doesn't throw NullErr. It's not too bad but a little bit inconsistent. a.compare(b) doesn't throw NullErr either.
calling super.equals and super.compare gives illegal Javascript. The workaround is to use === unless you are overriding more then once (which is unlikely to be justified anyway).
andyMon 18 Apr 2011
Promoted to ticket #1475 and assigned to andy
andyThu 2 Jun 2011
calling super.equals and super.compare gives illegal Javascript
This was a compiler bug - fixed in 1.0.59
SlimerDudeTue 18 Aug 2015
So err... this ticket is closed then?
andyTue 18 Aug 2015
Ticket resolved in 1.0.59
Sounds like it :)
I have not seen this anytime recently - but if someone can reproduce I'll reopen.
vkuzkokov Mon 4 Apr 2011
a.equals(b)works likea == b, i.e. doesn't throwNullErr. It's not too bad but a little bit inconsistent.a.compare(b)doesn't throwNullErreither.calling
super.equalsandsuper.comparegives illegal Javascript. The workaround is to use===unless you are overriding more then once (which is unlikely to be justified anyway).andy Mon 18 Apr 2011
Promoted to ticket #1475 and assigned to andy
andy Thu 2 Jun 2011
This was a compiler bug - fixed in 1.0.59
SlimerDude Tue 18 Aug 2015
So err... this ticket is closed then?
andy Tue 18 Aug 2015
Ticket resolved in 1.0.59
Sounds like it :)
I have not seen this anytime recently - but if someone can reproduce I'll reopen.