Lines Matching refs:attribute

71 variables, you can make your class attribute accessor methods either ignorant
168 values to the specific, named class attribute.
511 without any attribute methods whatsoever.  The most commonly used module
535     # accessor method for "name" attribute
542     # read-only accessor method for "birthday" attribute
549     # accessor method for "stars" attribute
578 Hold on, that doesn't look like anything special.  Those attribute
586 In the three attribute methods, C<%$self> is really accessing the %Cosmos
663 implement I<translucent attributes>.  A translucent attribute is one
665 attribute, in which case C<< $object->attribute() >> returns that value.
666 But if no value has been set, then C<< $object->attribute() >> returns
673 an object and store the attribute value directly on the class, then the
681 had a translucent data attribute called "color".  First you set the color
695 meta-object's value for that attribute, and these objects do not have
698 Changing the attribute on one object has no effect on other objects
721 Now let's change the color attribute on the entire class:
753 If you have an object with an actual attribute value, and you want to
754 make that object's attribute value translucent again, what do you do?
756 C<undef> as its argument, that attribute returns to translucency.
788     # translucent accessor for "color" attribute
809     # accessor for "PopCount" class attribute
829 object attribute is coming from the meta-object.  The &has_attribute
834     # detect whether an object attribute is translucent
841     # test for presence of attribute in class
886 suggest nominal privacy on attribute variables or hash keys, because these
1248     # translucent accessor for "color" attribute
1268     # class attribute accessor for "PopCount" attribute
1279     # detect whether an object attribute is translucent
1287     # test for presence of attribute in class