Luke Palmer:
# The first thing I noticed was the == / eq distinction. This
# has been invaluable for scripting, but since Perl 6 is
# desiring to be more of a formal language, I'm wondering
# whether the distinction is profitable. In generic programming
# (my specialty :), it is very useful to have a standard sort
# of equality[*] that all participating objects define.
Your desired "standard sort of equality" is provided by smartmatch.
$a ~~ $b
# The solution that springs to mind is to conform to other
# languages' thought and make == polymorphically compare
# equality. Thanks to context-forcing, the string/numeric
# distinction is still there, at the expense of a little extra
# verbosity:
#
# +$a == +$b; # Numeric compare
# ~$a == ~$b; # String compare
# $a == $b; # Generic compare
Conciseness and precision are lost. What's gained?
# Then we could also use eq for real identity, if we wanted to.
Which is the more common operation, string equality or identity check?
Thought so.
--Brent Dax <[EMAIL PROTECTED]>
@roles=map {"Parrot $_"} qw(embedding regexen Configure)
>How do you "test" this 'God' to "prove" it is who it says it is?
"If you're God, you know exactly what it would take to convince me. Do
that."
--Marc Fleury on alt.atheism
