c++ - Finite State Machine : Bad design? -


What is normally considered as poor design in OOP?

I have heard that much more, when I had to work to use an old, uncertified piece of C ++, I agree.

FSM should never be considered bad. They are very useful by now, but people who are not accustomed to them will often be burdened with them.

There are several ways to implement one with OOP. Some are inferior to others. Your low-level people will use the switch statement, jump the table or even "goto."

If you are looking for a cleaner way to do this, then I would recommend, which is designed to implement UML, state diagram in C ++ uses this modern template technology, so that Things could be made more readable. It also performs very well.


Comments

Popular posts from this blog

sql - dynamically varied number of conditions in the 'where' statement using LINQ -

asp.net mvc - Dynamically Generated Ajax.BeginForm -

Debug on symbian -