On 14-07-2012 07:00, Nick Sabalausky wrote:
On Fri, 13 Jul 2012 16:49:03 -0700
"H. S. Teoh"<hst...@quickfur.ath.cx> wrote:
On Sat, Jul 14, 2012 at 01:31:02AM +0200, Paul D. Anderson wrote:
I took a quick look at the Ceylon language (http://ceylon-lang.org/)
[...]
They also have couple of operators, '===' and '<=>' meaning
'identical' and 'compare', respectively.
Yikes! As soon as I saw '===', I went "no way, no how". That's one of
the most egregious flaws of languages like JavaScript. And they have
'is' on top of that?! Double yikes! What _must_ their type system look
like?!
Indeed. '===' operators are generally, if not always, indicative of a
thoroughly broken '=='.
The way Ceylon did it is definitely insane. But, I don't think having
=== *or* is, in addition to ==, is inherently bad. === would just be the
reference comparison operator, while == would always be for whatever
equality a class/interface has defined.
--
Alex Rønne Petersen
a...@lycus.org
http://lycus.org
