Best Practise/Subjective: Implement a finite state automaton in OOP

Posted by poeschlorn on Stack Overflow See other posts from Stack Overflow or by poeschlorn
Published on 2010-06-16T12:38:56Z Indexed on 2010/06/16 12:42 UTC
Read the original article Hit count: 747

Hi guys,

I am thinking about implementing a programm with finite state automaton in an OOP language like Java or C++.

What would you think is the best way to implement this with a manageable amount of available states, regarding to good software design?

Is it good to implement for each state an own class? If yes, how to do the bridge between two states?

Thanks for any comment!

© Stack Overflow or respective owner

Related posts about subjective

Related posts about oop