John Carter wrote:
"State Machines" are the embedded development flavour of the month?
year? (god forbid) decade? but are nothing more than multi-threaded
tangle of computed goto's with a roll your own scheduler in drag. :-))
(Oh dear... I have probably offended about half my colleagues. :-))
So I better add some fine print... "but can be useful in strict
latency requirement systems having insufficient RAM to create a stack
for each thread / State Machine."
Can't let that one go uncommented:
State machine != Multi-threading
State machine != Scheduler
Independent concepts. One can be used without the other.
Your colleague,
Douglas.
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
