Dan Sugalski <[EMAIL PROTECTED]> wrote:
The rule is that a method in a class has access to the attributes for that class and nothing else.
Ah, that was the reason of my confusion. Could you adapt the docs accordingly:
Yep. I'll patch that up.
> ... We're not enforcing that rule at the lowlevel, but compilers should never emit code for a method that has any knowledge of attributes outside the class the method is compiled into.
How *should* is "should"? Will Parrot automatically provide attribute get/set functions (e.g. via some class .pragma)?
Nope. If a language wants to provide get/set methods for class attributes it needs to create those methods at compilation time.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
