• No replies
15 Posts

Pinned topic Reusable statecharts

‏2013-06-06T13:21:08Z | statechart

I had an issue with reusable statecharts (C++ model).

class0{}  <<-- has statechart with state A

class1: class0 {}  <-- has statechart with class A, but "overrides inheritance"

Now, I have a list<class0*> that contains both obejctes of class0 and objects of class1. I iterate over the list and for each ask whether it IS_IN(A). This kind of traversal fails when it gets to object of class1.

I was wondering whether it makes sense to add a warning when Rahpsody encounters such a case as: (1) it seems unnatural to override data members and (2) statecharts and states are internal Rhp implementation.

What do you think?