On Nov 30, 2008, at 12:25 PM, Charles Yeomans wrote:
I don't see why this would be a good idea. Currently, one can add
get/set method pairs to an interface. This provides one with a way
to add things with the property look-and-feel to an interface.
Computed properties provide a way to add more or less the same thing
to a class, and prevent them from being overridden. Also, when
writing this feature request, don't forget to take return-type
covariance into account.
Charles Yeomans
....playing off-the-cuff semi-demi devil's advocate...
Say you've implemented an Observer Pattern. What if you (for some
reason) wanted to track all instances of observers with a shared
property? Granted you could scour the application at run-time for
each "Observable" and have it give up the names of all the items
observing it, but it would be much nicer if you could have a single
property that gets incremented when you "Register" a new Observer.
I could likely think of a couple more instances where it would be
useful, but that's the first thing that came to mind in the 30 seconds
I read over this thread.
Best,
Michael
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|