At 5:10 PM -0500 3/9/06, John Balestrieri wrote:
I understand the principle, I was just questioning the implementation ("questioning" does not mean "challenging"). As I understand it, computed properties were added so that we did not have to have cumbersome methods to manage property getting/setting in the same editor space as our class methods.
No, I think they were added mainly (1) to make VB converts more comfortable, and (2) to support REALbasic 2005, where the framework itself is written (or at least wrapped) in REALbasic. The framework has always had computed properties (as have plugins, for that matter), but these nonetheless show values in the debugger; breaking that functionality just because the framework is now RB code was not acceptable.
It seems we are loosing functionality we had by doing the same thing with methods, and I'm not seeing the benefit of these computed properties being handled as properties rather methods.
There isn't much. If you prefer methods, use methods. Indeed, one could argue that you now get to choose between virtual (method) and non-virtual (computed property) for any simple accessor, and that this choice is a Good Thing.
Best, - Joe -- Joseph J. Strout [EMAIL PROTECTED] _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html>
