Thanks all for the detailed comments & discussion.
Trying to distill this down -- would anyone be philosophically opposed
to either of these feature requests?
* a way for Interfaces to play nicely with Computed Properties, e.g.
Given
Interface: method foo as double
it would be legal for a subclass to satisfy the interface by
implementing:
Subclass: computed property foo as double
* a way for a subclass (including window classes) to shadow a
superclass property with a method or computed property, and then
access that property:
computed property WindowSubclass.Visible() as boolean
get:
return super.visible // access Window.Visible, not
WindowSubclass.Visible()!
set:
super.visible = value
' do special subclass logic here
I'll submit to fogbugz if nobody has any objections?
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|