Thomas Sandlaà writes:
> Larry Wall wrote:
> >On Mon, May 02, 2005 at 05:42:47PM -0700, Larry Wall wrote:
> >: We're still discussing it on @Larry, but I think we can make that work.
>
> Sorry if I don't know, but where or what is @Larry?
Ahh, you came in too late. I don't remember who coined it, but @Larry
is the array of Larrys, that is, the design team.
> I guess some IRC?
No #Larry {yet, >:-}.
> >Well, now I think &.foo() won't work, since &.foo should be reserved
> >for a sub ref attribute to be consistent. But I think all we have
> >to do is find some other character to use for self calls instead of '&'.
> >There are a number of candidates, and I can convince myself that there
> >are good arguments for most of them, so now I just have to pick the one
> >with the weakest arguments against it. :-)
>
> I'm not carping about the syntax but about the in my eyes unfortunate
> binding of the topic variable to one of the invocants.
I agree with you there. $Larry has said that he wants `when` to work
at the top level in methods, which is the main reasoning for the topic
binding. Indeed, that might cause people to use .method to mean "call
on self", and then get shot in the foot when they reorganize things, but
I think it would be easy enough just to teach them not to. If they do,
then they're the ones with the gun.
> BTW, what does $.foo outside of class scope mean?
It means:
BEGIN { die "Can't use \$.foo outside of class scope"; }
:-)
Luke
