Author: wayland
Date: 2009-03-06 06:25:49 +0100 (Fri, 06 Mar 2009)
New Revision: 25722
Modified:
docs/Perl6/Spec/S32-setting-library/Callable.pod
Log:
Assuming .^methods returns an array of Method objects, I'mve documented things
appropriately. Now we just have to decide what the attribute de
I've done some more fiddling based on Carl Masak's updated list.
* I see the sub version of defined declared in S29. Is the method
version (used in S02:519) also in S29? I can't see it, but I might be
missing something about how method signatures work.
I've moved it to S32
OK; let me get a quick clarification here. How does:
say "Hello, World!";
differ from:
"Hello, World!".say;
or:
say $*OUT: "Hello, World!";
in terms of dispatching? And more generally, would there be a
reasonable way to write a single routine (i.e., implementation) that
could be
Author: wayland
Date: 2009-03-06 02:49:52 +0100 (Fri, 06 Mar 2009)
New Revision: 25719
Added:
docs/Perl6/Spec/S32-setting-library/Basics.pod
Removed:
docs/Perl6/Spec/S32-setting-library/Any.pod
docs/Perl6/Spec/S32-setting-library/Scalar.pod
Log:
Made Basics contain Object, Any, Pattern, a
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 ( A
Darren Duncan wrote:
So, is there some way, or is it reasonable for there to be, to declare a
method in Perl 6 such that say it is declared with say an Array of R or
Set of R etc parameter and that parameter is marked somehow, maybe with
a trait, to say it automatically gains the invocant as on
Darren Duncan wrote:
> Here's a question:
>
> Say I had an N-adic routine where in OO terms the invocant is one of the N
> terms, and which of those is the invocant doesn't matter, and what we really
> want to have is the invocant automatically being a member of the input list.
How about allowing
Larry Wall wrote:
So what's the difference between a function and a method then?
Nothing on the implementation end. The only difference is in the
call end; we have different calling notations that invoke different
dispatchers. Each of those dispatchers resolves the membership
and ordering of i
Author: lwall
Date: 2009-03-05 20:39:22 +0100 (Thu, 05 Mar 2009)
New Revision: 25715
Modified:
docs/Perl6/Spec/S02-bits.pod
docs/Perl6/Spec/S03-operators.pod
Log:
By principle of least damage, minimalize autopromotion of lists in item context
to Capture rather than to Array. (Let bindin
Author: lwall
Date: 2009-03-05 20:11:49 +0100 (Thu, 05 Mar 2009)
New Revision: 25712
Modified:
docs/Perl6/Spec/S12-objects.pod
Log:
more method declaration clarification, ruoso++
Modified: docs/Perl6/Spec/S12-objects.pod
===
---
Author: lwall
Date: 2009-03-05 20:00:13 +0100 (Thu, 05 Mar 2009)
New Revision: 25711
Modified:
docs/Perl6/Spec/S12-objects.pod
Log:
fix declaration syntax of private methods
Modified: docs/Perl6/Spec/S12-objects.pod
===
--- docs/
On Thu, Mar 05, 2009 at 12:58:21PM -0300, Daniel Ruoso wrote:
: Em Qua, 2009-03-04 às 20:21 +0100, pugs-comm...@feather.perl6.nl
: escreveu:
: > Simplify meaning of Capture and Match in item context to preserve sanity
: > (an object in item context is always just itself, never a subpart)
:
:
On behalf of AthenaLab, Im extremely happy to announce the
winners of AthenaLabs $1,000 prize for a Perl 6 based wiki.
The winners are Carl Mäsak, Johan Viklund, and Ilya Belikin.
They are members of the November project, which is a wiki
written in Rakudo Perl 6.
Carl Mäsak and Johan Viklund sta
Daniel Ruoso wrote:
> Daniel Ruoso escreveu:
>> What really got me confused is that I don't see what problem this change
>> solves, since it doesn't seem that a signature that expects an invocant
>> (i.e.: cares about invocant) will accept a call without an invocant, so
>> "method foo($b,$c) is exp
Em Qui, 2009-03-05 às 12:58 -0300, Daniel Ruoso escreveu:
> What really got me confused is that I don't see what problem this change
> solves, since it doesn't seem that a signature that expects an invocant
> (i.e.: cares about invocant) will accept a call without an invocant, so
> "method foo($b,$
Em Qua, 2009-03-04 às 20:21 +0100, pugs-comm...@feather.perl6.nl
escreveu:
> Simplify meaning of Capture and Match in item context to preserve sanity
> (an object in item context is always just itself, never a subpart)
sub foo { return 1 }
my $a = foo();
That is currently expressed as tak
> 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 $self)
> + our Bool multi method defined
17 matches
Mail list logo
