Luke Palmer wrote:
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.
Aha. What does [EMAIL PROTECTED] evaluate to? How do the elements of
@Larry communicate?
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.
If 'when' were the single exception then setting $_ = $?SELF (note: copy
not binding) there when in method code should be doable for the compiler.
BTW, what does $.foo outside of class scope mean?
It means:
BEGIN { die "Can't use \$.foo outside of class scope"; }
That contradicts $Larry's statement: "By the way, this probably goes along
with a policy of allowing $.foo, @.foo, and %.foo outside of the class as well.
These would not refer to the actual attribute, but would call $self.foo()
underneath (except in the class that actually defines the attribute)."
OK, he has got a 'probably' there. Would it be the one character saver
$.foo == $_.foo outside class scope, $.foo == $?SELF.foo in methods
of derived (or even unrelated?) classes and direct access to the instance
variable in the class scope that has the corresponding 'has $.foo' declaration?
Regards,
--
TSa (Thomas SandlaÃ)
