software design - Implement a finite state automaton in OOP -


I think of implementing a program with a finite state automaton in an OOP language such as Java or C ++ I am here.

Regarding good software design, do you think the best way to implement it with a handleable amount of available states?

Is it good to apply your class to each state? If so, how to bridge between two states?

Thanks for any comments!

Is it just for your programming muscle to flex or actual project etc? In both cases it depends on the state machine for you: - It is to manage tasks in some kind of workflow - this application is to determine the flow state - this is for business rule engine etc.

< P> In case of a project, I would recommend that, depending on your targeted usage, you search for libraries in that domain. For example, there are many other libraries for Java workflow / business flow, as well as many tons of rules in the engine (Drools comes under the scope of bat, though it is a complex beehor)


Comments

Popular posts from this blog

windows - Heroku throws SQLITE3 Read only exception -

lex - Building a lexical Analyzer in Java -

python - rename keys in a dictionary -