Area and Radius properties would be some sort of number objectsWell, they are. I mentioned that you could tie them, if you want to be able to manipulate them more like native numbers. But it's just about as easy to get the value, manipulate it, and put it back. This is exactly the same thing you'd do with parent-level getters and setters.
I don't see any better organization here at all. In fact, it seems quite a bit messier to meIn my view, having getFoo, setFoo, doSpecialThingWithFoo, etc. is analogous to having $var1, $var2, $var3 instead of @var. Having like things grouped together under one heading is the improved organization I'm talking about.
I would be interested to see what you consider to be a maintenance nightmare about the interface. If your beef is with the implementation, well, that's always subject to refactoring.
In reply to Re^2: The Accessor Heresy
by Roy Johnson
in thread The Accessor Heresy
by Roy Johnson
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |