At 12:53 PM -0700 10/5/02, Michael Lazzaro wrote:
>Dan Sugalski wrote:
>>
>> There won't be any direct access to attributes outside class methods
>> of the class that defines the attributes, unless Larry changes his
>> mind in a big way. (And, honestly, probably not even then) Instead
>> it'll all be accessed via lvalue methods. If an attribute is exposed
>> there's just an lvalue method created, if it's not exposed there
>> isn't.
>
>Ack! Hold on, there: I'm being told that Damian thinks lvalues are
>probably out, and that Larry thinks that pseudo-attributes will be made
>accessed through the use of lvalues. Please confirm, which is it? I
>don't particularly care, I just want to write an example down in
>best-guess form.
Object attributes aren't until A12. It's possible things will change,
and as such it's a bit early to worry about things. Still, access to
attributes outside the owning class' methods *will* be via methods
only (but only if the attribute is made public), and from within the
class will be done directly. They might be readonly, or you might
have set_ methods to set rather than lvalue methods, but either way,
there's a method involved from outside the class.
>Now, second question: if slots are in, that means that there is
>fundamentally no difference between a method and attribute. (This is a
>Very, Very Good Thing.) Will there be a _syntactic_ difference? e.g.
Who says slots are in? You can have attributes and methods with the
same name, but they don't have to be related. Heck, a class' parent
classes can all also share the same method and attribute name, as can
all their parent classes.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
