Subject:
|
Re: FSMs, coding techniques and other goodies
|
Newsgroups:
|
lugnet.robotics.rcx
|
Date:
|
Tue, 14 Dec 1999 01:06:44 GMT
|
Viewed:
|
1288 times
|
| |
|
|
Vlad,
why don't you write a graphical FSM generator?
Textbook FSMs are quite powerful, but in practice, states and
transitions are usually augmented with enter/hold/leave actions. This
provides plenty of configuration potential. Also, there's a whole body
of theory available to turn non-deterministic ones into deterministic
ones, minimize them etc.
You could write back ends to create code for NQC, legOS, pbForth and
even Spirit.ocx remote control from one and the same FSM description.
Never solve the problem. Solve the class of problems.
Markus.
--
"Nieder mit den Zitaten!" -Markus L. Noga <markus@noga.de>
|
|
Message has 1 Reply:
 | | Re: FSMs, coding techniques and other goodies
|
| (...) I was thinking about that. The problem is that I lack the time... for the next couple of months, anyway... The idea of using a higher level language comes from the guess that it would be faster to develop than a graphical tool. Plus that it (...) (25 years ago, 14-Dec-99, to lugnet.robotics.rcx)
|
Message is in Reply To:
| | FSMs, coding techniques and other goodies
|
| Hi all! I know that multitasking is reducing the need for using FSMs, but in my case the tasks ended being smaller FSMs after all, and because some parts were overlapping - why not use a single large FSM? [maybe it is my own fault that FSMs appear (...) (25 years ago, 13-Dec-99, to lugnet.robotics.rcx)
|
5 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
