This seems to be adding a special case. (I.e. only if _both_ are
non-numeric will it switch to a cmp operation.)
I currently fail to switch to 'eq' many times when I should, but the
failure mode is obvious. Her the failure mode will be really strange.
(And how does one tell if the string is numeric or not?
eg. "35abc" == "n37c"
)
Would modifying the waya number is converted to string be more
satisfactory? I generally look at the 'cmp' amily as doing a lexical
ordering. While the '<=>' as doing a numerical ordering.
So I'm not sure that your generic insertion is generic enough. One still
has to decide on the ordering.
Enlighten me O' prolific one.
<chaim>
>>>>> "PRL" == Perl6 RFC Librarian <[EMAIL PROTECTED]> writes:
PRL> =head1 ABSTRACT
PRL> This RFC proposes that numeric comparison operators default to stringwise
PRL> comparison when both arguments are non-numeric strings.
PRL> =head1 DESCRIPTION
PRL> Currently the expression:
PRL> "cat" == "dog"
PRL> returns true.
PRL> It is proposed that if I<neither> argument of a numeric comparison
PRL> operator can be converted to a number, rather than both being converted
PRL> to zero, the two operands should be compared using the equivalent
PRL> stringwise comparison operator.
--
Chaim Frenkel Nonlinear Knowledge, Inc.
[EMAIL PROTECTED] +1-718-236-0183
