On Thu, Jul 14, 2005 at 12:14:57PM -0600, John Williams wrote:
: Actually I took his question to be:
:
: If I explicitly name my invocant in the method signature, does that give
: the compiler enough assurance that I'm not going to use .method to mean
: $?SELF.method, and it will allow me to safel
On Wed, 13 Jul 2005, Juerd wrote:
> Dave Whipp skribis 2005-07-13 8:44 (-0700):
> > > Within a method or submethod, C<.method> only works when C<$_ =:=
> > > $?SELF>.
> > >C<.method> is perfectly legal on *any* topic anywhere that $?SELF
> > >doesn't exist.
> > Just to be clear, this includes an
Dave Whipp skribis 2005-07-13 8:44 (-0700):
> > Within a method or submethod, C<.method> only works when C<$_ =:=
> > $?SELF>.
> >C<.method> is perfectly legal on *any* topic anywhere that $?SELF
> >doesn't exist.
> Just to be clear, this includes any method/submethod with an explicitly
> named
Damian Conway wrote:
Important qualification:
Within a method or submethod, C<.method> only works when C<$_ =:=
> $?SELF>.
C<.method> is perfectly legal on *any* topic anywhere that $?SELF
doesn't exist.
Just to be clear, this includes any method/submethod with an explicitly
named invo
Matt Fowles summarized:
Method Call on Invocant
Now " ./method "is gone, and " .method " only works when " $_ =:= $?SELF ".
Important qualification:
Within a method or submethod, C<.method> only works when C<$_ =:= $?SELF>.
C<.method> is perfectly lega
Perl 6 Summary for 2005-07-05 through 2005-07-12
All~
Welcome to another summary from the frog house. A house so green it can
be seen from outerspace (according to google earth).
Perl 6 Compiler
Building Pugs Workaround
Sam Vilain posted a useful work around to the error
