I would be interested to see what you consider to be a maintenance nightmare about the interface.
There's nothing all that onerous about the interface but the interface isn't what gets maintained; the implementation is.
In one fell swoop—and with an extremely simplistic example no less—you've almost doubled your number of methods and tripled your number of classes. Your number of lines of code has probably grown in proportion to those numbers... somewhere between one and two hundred percent. With that comes more chance for errors and a bigger haystack to find them in. On top of that, you've given yourself the choice of keeping those classes and methods in separate files or living with multiple methods with the same name (get, set, new) all in one file. All at the expense of performance and for what purpose again?
-sauoq "My two cents aren't worth a dime.";
In reply to Re^3: The Accessor Heresy
by sauoq
in thread The Accessor Heresy
by Roy Johnson
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |