I think is some confusion arising form our differing ideas of "attribute".
An attribute is essentially a variable with possibly some runtime enforced restrictions so it should be accessible just like any other variable.That is needlessly restrictive, and the conclusion does not follow from the premise. Suppose you have a timer that is counting up/down. You may have, as an "attribute", the elapsed time/time remaining. Should that look like a variable?
You changed the premise (widened the meaning of "attribute") it's no surprise that the conclusion no longer follows.
A timer shouldn't look like a variable because it doesn't behave like a variable. Trying to put a variable-like interface on something that doesn't behave like a variable is just confusing and a bad idea and I never suggested that.
My definition was needfully restrictive - in order to reach my conclusion. If your idea of an attribute includes things that don't behave like variables then please run
on my previous comments.perl -pe 's/(attribute)/behaves-like-a-variable-$1/g
In reply to Re^11: Perl OO and accessors
by fergal
in thread Perl OO and accessors
by dragonchild
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |