Message, Method, Event. It seems sometimes that despite them having known meanings, they're all are used confusedly and interchangeably. Add to that the fact that some languages have a separate message queue which has nothing to do with the messages sent between objects, and confusion!!
What I find interesting in the Active* objects is that there's a tendency not to subclass methods. Instead, people will assign container class methods to event properties. I suspect it's because some languages don't allow you to subclass methods in an object definition, and people are used to coding against that. Those patterns then stick around even when people are subclassing as it's easier to learn one interfacing pattern that works with both classes and objects than it is to learn two. That probably doesn't make sense to anyone but me actually. Anyway - even if I'm making no sense at all, that's what I think. > -- You received this message because you are subscribed to the Google Groups "NWRUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nwrug-members. For more options, visit https://groups.google.com/groups/opt_out.
