From: gwtmp01@...
Date: 2006-08-29T12:22:39+09:00
Subject: Re: A newbie question about case and ===


On Aug 28, 2006, at 9:02 PM, Eero Saynatkari wrote:
> case actually evaluates the other way.
>
>  Integer === a_fix_num   # true

I think the problem is that the visual representation (===)
of the operator i symmetric and this tends to imply that the
operator follows associative behavior ((a op b) the same as
(b op a)) but that isn't true for === in general.

If the operator token was asymmetric  I don't think it would
be so confusing.  Actually, I wonder why the match operator (=~)
couldn't be used instead.  I've looked into this a bit, but I
I suspect that there are very few cases where === and =~
could not be aliases for each other.

Gary Wright