Re^8: Assignable Subroutines

I think demerphq isn't speaking so much about publicly-exposed mutators as accessing properties from within the class itself.

A good example of this would be a method in a base class. It needs to increment the value of the foo property. Should it

$self->{foo}++;?
No good - some child class may have restricted the foo property and you just went past the maximum value.
$self->foo( $self->foo + 1 );?
Now we're respecting the children. But ...

wouldn't it be nice to say $self->foo++;. You get the conciseness of the first option with the child-safety of the second. And, you don't even have to know how you're represented in memory. It. Just. Works.

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

Comment on Re^8: Assignable Subroutines Select or Download Code

Replies are listed 'Best First'.
Re^9: Assignable Subroutines by Anonymous Monk on Jan 26, 2005 at 04:07 UTC
you just went past the maximum value You get the conciseness of the first option with the child-safety of the second. Child-safety caps give me hand cramps.	[reply]