Making the right choices about the EventMechanism and the StateCharts interface to that mechanism is key to having a StateChartTool? that is easy to use and has broad applicability. On Win32 I think the choice is obvious: use COM events, and use TypeLibrary? input at edit/compile time to generate the event stub handlers. On other platforms - what do we do? It seems to be somewhat case-by-case. For example, under KDE / Qt we could look at signals and slots (though I'm not sure how to dig out that information without parsing header files). But is there some similar EventMechanism available for other C++ environments? How about Java? And if we are to genuinely MultipleLanguageSupport?, is there any way that we can also have a shared EventMechanism? I kind of doubt it.
The approach taken with SPL (StateProgrammingLanguage) was to build an EventMechanism based on StructuredStrings?. But that approach is less desirable if there is already a 'native' EventMechanism available.
-- DaleBrayden - 23 Jul 2002
Books RSS
