Abhijit A. Mahabal wrote:
*{"Foo::name1"} = -> $a { $a->{name1} };
If I read A12 correctly, this could be written as:
&Foo::$name1 := -> $a {$a.name1};
Could be; that sounds somewhat right, but could you point out where in A12
because a search for := revelaed nothing relevant to me.
Sorry, t
On Sun, 25 Apr 2004, Dave Whipp wrote:
>
> "Abhijit A. Mahabal" <[EMAIL PROTECTED]> wrote:
> > Symbol tables and typeglobs and such belong to A10... and the * has been
> > stolen... so I'll just speculate in pseudocode.
> > Blocks-are-subroutines makes life easier, and in pseudocode that can be
>
Dov Wasserman wrote:
> It's a valid question in general, but since you're designing this
> functionality from the ground up (and not retro-fitting it in to
> existing code), wouldn't the better approach be to create a non-GUI
> HList class, and a GUI subclass that adds the indicator methods? Or
>
"Abhijit A. Mahabal" <[EMAIL PROTECTED]> wrote:
> Symbol tables and typeglobs and such belong to A10... and the * has been
> stolen... so I'll just speculate in pseudocode.
> Blocks-are-subroutines makes life easier, and in pseudocode that can be
> just:
> *{"Foo::name1"} = -> $a { $a->{name1} }
On Sat, 24 Apr 2004, John Siracusa wrote:
> Based on the "default accessors and encapsulation" thread, it seems like a
> Perl 6 equivalent of Class::MethodMaker will be still be useful in our (or
> at least "my") Brave New World. I've been pondering the best way to create
> such a beast in Perl
A LONG time ago, after an Apocalypse far, far away, I tried to define
many built-in operators in Perl 6 to see if I "got it". After A12 I
think I get it enough to try at least the math ops again.
Everything in this file about modules and emitting IMCC is total
arm-waving, and there's no exporting
On Fri, 2004-04-23 at 20:51, Larry Wall wrote:
> On Sat, Apr 24, 2004 at 09:52:12AM +1000, Damian Conway wrote:
> : My proposal for that issue is just:
> :
> : module Bar;
> :
> : use Foo «foo»;
> :
> : sub foo is export {...}
>
> That's on the right track, but has some difficulties
On Fri, 2004-04-23 at 21:44, Jonathan Lang wrote:
> OK: I'm planning on creating a widget which must not make use of any of
> the indicator functionality of the HList; I don't just want to not use the
> functionality - I want to have its use forbidden (letting the optimizer go
> ahead and toss out
It's a valid question in general, but since you're designing this
functionality from the ground up (and not retro-fitting it in to existing
code), wouldn't the better approach be to create a non-GUI HList class, and
a GUI subclass that adds the indicator methods? Or even better, less tightly
couple
Based on the "default accessors and encapsulation" thread, it seems like a
Perl 6 equivalent of Class::MethodMaker will be still be useful in our (or
at least "my") Brave New World. I've been pondering the best way to create
such a beast in Perl 6.
The most common two Perl 5 techniques are:
1. U
10 matches
Mail list logo
