On Mar 10, 2006, at 3:05 PM, Theodore H. Smith wrote:
From: Guyren Howe <[EMAIL PROTECTED]>
Date: Fri, 10 Mar 2006 08:22:42 -0600
On Mar 10, 2006, at 4:56 AM, Theodore H. Smith wrote:
So Lets say I have class "MySuper", and class "MySub". Both have
the "GetItem" event. If I call "GetItem", the event called really
depends on which class the code is in that is calling GetItem. So
it's as if we actually had the method:
function MySuper_GetItem() as item... and
function MySub_GetItem() as item
This would allow for distinguishing between which "event" is
called. All you'd need then is a bit of syntactic magic in the
parser to imply the "MySuper_" or the "MySub_" part when coming
across a call to "GetItem"!
And you'd have an event system that is built out of methods.
Except that maintaining it is a nightmare, and setting it up in the
first place is significantly extra work than letting RB do it for us.
No, you don't get what I mean.
I'm suggesting something that doesn't yet exist.
It would look just like events, smell like events, compile like events.
So from that persepective, nothing has changed, it's only an
implementation detail.
The only difference, is that you'd be able to call the events from the
outside, with soemthing like the form "MySuper_MethodName", because
those events really are just ordinary methods.
I filed a feature request for this sort of thing some time ago.
--------------
Charles Yeomans
_______________________________________________
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>
