Version 2.215 (Mar 21, 2004) of object.c assumes that identity implies equality. I won't rehash the discussion about custom objects and NaN. I do think the decision should be reasonably consistent. The current CVS version shortcuts for == and !=, but not for the other operators. Normally, x == y implies x <= y x >= y not x < y not x > y (in addition to) not x != y I think any object that intentionally violates these rules is likely to also violate the (is implies ==) assumption. -jJ
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4