|
|
|
|
|||||||
| Forums | Portal | Register | Forum Rules | FAQ | Contribute | Members List | Arcade | Search | Today's Posts | Mark Forums Read |
| High Level Programming Post questions about C, C++, Java, SQL, and other programming languages here. |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| mach 0.9.3 (Default branch) | iBot | Software Releases - RSS News | 0 | 05-22-2008 05:50 PM |
| child process state | smreddy | UNIX for Dummies Questions & Answers | 8 | 12-23-2007 09:51 PM |
| The State of Unix (Addict 3D) | iBot | UNIX and Linux RSS News | 0 | 06-18-2007 07:40 PM |
| Process State | ianlow | UNIX for Dummies Questions & Answers | 1 | 09-06-2006 07:11 AM |
 |
|
|
Submit Tools | LinkBack | Thread Tools | Display Modes |
|
#1
10-20-2005
|
|||
|
|||
|
state machine...
hi,
I am looking for some info on how can we implement state machines. Conceptually it appears to be good but while implementing it causes lot of confusion.. I have some doubts regarding this concept. (my explanation may look wired, as I am also not clear on this front) The commonly adopted strategy to implement state machine is to have array of function pointers to handle a state. When ever appropriate input is recv the array is activated or used to trigger the functions. (I don't have solid example, sorry for making it difficult to understand) Can somebody add some info on this... Regards, Parasa Kiran Last edited by parasa; 10-20-2005 at 02:50 AM. 
|
| Forum Sponsor | ||
|
|
|
#2
10-20-2005
|
||||
|
||||
|
Quote:
Rules -> (10) Don't post your email address and ask for an email reply. The forums are for the benefit of all, so all Q&A should take place in the forums. Last edited by vino; 10-20-2005 at 03:01 AM.
|
Linear Mode
