in reply to Re^3: Are lvalue methods (as properties) a good idea?
in thread Are lvalue methods (as properties) a good idea?
Sure it's overhead. But you only need to write the tieing class once globally, and you only need to write one validating closure per kind of validation. With that work out of the way, you can define the constraints for all your attributes declaratively.
As far as I'm concerned it's a big win in terms of syntax and maintenance.
Makeshifts last the longest.
|
|---|