And as long as you're naming things, about the return value from setters?
It's in the plan, but I see that as an orthogonal decision for what to call the setter in the first place. The choice for what to name them also seemed a little more self-evident: "new_value", "old_value", "self". I hadn't thought of doing success/fail, as I'm also planning on having a user hook that can filter/validate in the setter and die with an error message to indicate failure.
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
| [reply] |
Whatever the documention reads, the last bet is probably the safest assumption. Don't trust anything more than you have to. :-) | [reply] |