On Fri, Mar 06, 2009 at 12:15:18PM +1100, Timothy S. Nelson wrote:
On Thu, 5 Mar 2009, Patrick R. Michaud wrote:
Also, I personally would prefer to not see explicit typing
on the invocants to most methods.
Agreed. I wonder what I was thinking :).
Although, interestingly, if the method
HaloO,
Larry Wall wrote:
Although, interestingly, if the method is exported as a multi it
should automatically add in the current role or class as a constraint
on the (former) invocant so that multi dispatch will not overgeneralize.
I would expect
class Foo
{
method bar {...}
Em Sex, 2009-03-06 às 18:51 +0100, TSa escreveu:
I know that the use of 'is also' is called monkey patching but I can't
understand why this is regarded as a bad thing. Having a class assembled
from multiple modules is a rather normal affair.
You're describing Roles here, which is something you
On Thu, 5 Mar 2009, Patrick R. Michaud wrote:
Log:
- Moved defined and undefined from Scalar.pod to Any.pod,
as per signature
...
+=item defined
+
+ our Bool multi defined ( Any $thing )
+ our Bool multi defined ( Any $thing, ::role )
+ our Bool multi method defined ( Any
