From: <pcm...@us...> - 2009-01-24 03:20:55
|
Revision: 1139 http://javapathfinder.svn.sourceforge.net/javapathfinder/?rev=1139&view=rev Author: pcmehlitz Date: 2009-01-24 03:20:51 +0000 (Sat, 24 Jan 2009) Log Message: ----------- * changed the way State.isActive() is set/reset, which is now done from setNextState(), AND ALSO IS HIERARCHICAL (i.e. we can now easily determine if a parent state is active) BUT: it only tells you if the state is still active in this step, or we already know it's going to be active in the next step. It doesn't separate the two cases * added a StateMachine.isInActiveStates(s), to answer at least if the provided state is still going to be processed in this step. * reworked the state entry processing, to hierarchically update 'isActive' and execute entry actions accordingly !! this isn't a real solution yet - UML just deals very badly with concurrency, and the 'active state' concept isn't very suitable to model it. Modified Paths: -------------- trunk/extensions/statechart/env/jpf/gov/nasa/jpf/sc/State.java trunk/extensions/statechart/env/jpf/gov/nasa/jpf/sc/StateMachine.java trunk/extensions/statechart/env/jvm/gov/nasa/jpf/jvm/NativeStateMachine.java trunk/src/gov/nasa/jpf/jvm/MJIEnv.java This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |