Author: audreyt
Date: Sat Sep 30 20:16:38 2006
New Revision: 12533
Modified:
doc/trunk/design/syn/S02.pod
doc/trunk/design/syn/S09.pod
Log:
* S02: Re-introduce comprehension, this time not context-specific,
under the list() syntactic expression:
# list() comprehension that evalu
Author: audreyt
Date: Sat Sep 30 20:13:47 2006
New Revision: 12531
Modified:
doc/trunk/design/syn/S09.pod
Log:
* S09: any() no longer has anything to do with comprehension.
Modified: doc/trunk/design/syn/S09.pod
==
--
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
