Jonathan Scott Duff wrote:
>> sub cond(Bool $c, $a, $b) is rw {
>> if $c return $a else return $b;
>> }
>>
>> Will this fail because $a and $b are not rw? If so, will it fail at run-
>> or compile-time? What about this:
>>
> That looks like it should be a compile-time failure to me.
>
De
I don't have any real answers, but I'll weigh in with my opinion
anyway :-)
On Tue, Jun 20, 2006 at 10:59:01AM +0100, Daniel Hulme wrote:
> I've just thought of an interesting interaction with lvalue functions
> and call by foo. What if I want to write, say, an lvalue ?? !! function
> thus
>
> s
On Mon, Jun 19, 2006 at 08:51:24AM -0600, Eric wrote:
: Just my two cents, but whenever i see "when True {...}" I expect $_
: to be true, so that i can do when True and when False. And I if see
: when followed by a comparison i expect the when to be true when the
: comparison is true. To me its
Author: larry
Date: Tue Jun 20 11:38:41 2006
New Revision: 9716
Modified:
doc/trunk/design/syn/S12.pod
Log:
s/property/attribute/ from cognominal++
Modified: doc/trunk/design/syn/S12.pod
==
--- doc/trunk/design/syn/S
Author: larry
Date: Tue Jun 20 11:37:51 2006
New Revision: 9715
Modified:
doc/trunk/design/syn/S03.pod
doc/trunk/design/syn/S04.pod
Log:
Smart match moved to S03.
Smart match clarifications.
Modified: doc/trunk/design/syn/S03.pod
===
I've just thought of an interesting interaction with lvalue functions
and call by foo. What if I want to write, say, an lvalue ?? !! function
thus
sub cond(Bool $c, $a, $b) is rw {
if $c return $a else return $b;
}
Will this fail because $a and $b are not rw? If so, will it fail at run-
or comp
