Am 14.07.2012 07:13, schrieb H. S. Teoh:
On Sat, Jul 14, 2012 at 01:00:18AM -0400, 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 '=='.
What boggles my mind is the fact that they have '===' *and* 'is'. I
don't think I want to know what's the difference between them.
One of these days, I should invent a language that sports the ====
operator. Along with the associated<====> operator and the ^_^
operator.
Easily doable in any language where operators are plain function names,
like ML-family, Lisp, Smalltalk, ...
