Re: ? 1={}, is there really any other interpretation?
Everytime this subject comes up, I suggest the same thing, but no one ever
comments. First of all, the idea of changing the behavior of existing operators
is crazy -- you'll break too much code; it is too late for that (by 18 years).
[It would break virtually ALL of my code -- to me sequence ops *IS* Euphoria --
that's why I use it.] Second of all, the functionality the complainers want
already exists in the language -- they just don't like to type the correct
functions to use it.
So the answer is, of course, just to ADD NEW OPERATORS -- just add a colon (or
whatever) to each operator to make it a strict boolean operator:
:<
:=
:>
etc.
Problem solved. No code breaks, and you've got some nice shortcuts so you never
have to type compare(). What's the problem with that?
|
Not Categorized, Please Help
|
|