in reply to Why get() and set() accessor methods are evil
An object should have methods reflecting its external behavior. "Set your X value to 24" is rarely a nice reusable, maintainable external behavior.
People writing these kinds of objects generally haven't quite gotten in to "object thinking", and instead treat the object as a "smart record". Methods should instead be derived by understanding how the class might be used (including subclassing).
I think the Perl6 object approach where all variables are private to the class (and not even directly available to the subclasses) will make for some interesting designs, especially when thinking about reuse.
-- Randal L. Schwartz, Perl hacker
Be sure to read my standard disclaimer if this is a reply.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Why get() and set() accessor methods are evil
by Abigail-II (Bishop) on Nov 25, 2003 at 17:12 UTC | |
Re: •Re: Why get() and set() accessor methods are evil
by Elian (Parson) on Nov 25, 2003 at 21:46 UTC | |
by Juerd (Abbot) on Nov 26, 2003 at 22:44 UTC | |
by sth (Priest) on Nov 26, 2003 at 19:00 UTC | |
by Ovid (Cardinal) on Nov 26, 2003 at 19:16 UTC | |
by sth (Priest) on Nov 27, 2003 at 00:26 UTC | |
by Elian (Parson) on Nov 26, 2003 at 19:12 UTC |
In Section
Meditations