Jonathan Scott Duff wrote:
I hope you're way off the mark. Automatic coercion was one of the
annoyances I remember from C++. Debugging becomes more difficult when
you have to not only chase down things that are a Foo, but anything
you've compiled that might know how to turn itself into a Foo.
O
From: Jonathan Scott Duff <[EMAIL PROTECTED]>
Date: Sat, 30 Sep 2006 17:23:54 -0500
On Sat, Sep 30, 2006 at 11:48:04AM -0700, Joshua Choi wrote:
> How does automatic coercion work?
[ deletia ]
> 1. C automatically coerces its C arguments into C
> parameters because C.
Wouldn
On Sat, Sep 30, 2006 at 11:48:04AM -0700, Joshua Choi wrote:
> How does automatic coercion work?
[ deletia ]
> 1. C automatically coerces its C arguments into C
> parameters because C.
> 2. C then automatically coerces its C arguments into
> C parameters because C.
>
> ...Or am I completely off t
My understanding is that "does" will prevent coercion. In particular,
it is erroneous to say that 'Str does Num' or that 'Num does Str'.
If you say 'Foo does Bar', what this means is that anything Bar can
do, Foo can do, too. As such, any routine that asks for a Bar can
just as easily be given
Kudos to all(@Larry)!
How does automatic coercion work? Like, when a routine wants a
parameter of a certain type, and is called with an argument of a
different type that C
(For instance, is it something a little like this?
multi sum ( Num $addend1, Num $addend2 --> Num ) { ... }
multi say ( S
