Re: Text on FSM

Newsgroups	comp.arch.embedded
Date	2023-03-10 07:20 -0800
References	<ba8e4635-0eb1-4a92-99a7-e6bf7ba67e14n@googlegroups.com> <tuer7v$1sg9m$1@dont-email.me> <rr5m0i5dh7buhchacl4tnplmtf4h39vrr5@4ax.com>
Message-ID	<99eae897-178b-4760-bc71-61ba49b76b44n@googlegroups.com> (permalink)
Subject	Re: Text on FSM
From	Rick C <gnuarm.deletethisbit@gmail.com>

Show all headers | View raw

On Friday, March 10, 2023 at 6:48:13 AM UTC-5, Robert Roland wrote:
> On Fri, 10 Mar 2023 09:54:23 +0100, pozz <pozz...@gmail.com> wrote: 
> 
> >There will be a time when the programmer would simply draw one or more 
> >state-machines and click a button to generate the full working code in 
> >whatever language.
> When I went to school, 30 or so years ago, we did have such a program. 
> I am not able to remember its name, though. 

The problem these have, like many graphic oriented approaches, is continuing support and version control of the source.  I've never worked with a state machine that was so complex it required anything other than a diagram drawn up in your favorite word processor drawing package.  Typically, FSM can be decomposed into multiple distinct FSM that are easier to understand, and typically relate to the problem better.  

A FSM with 10 states is easy to code.  A FSM with 100 states is probably several FSMs, mistakenly combined into one. 

-- 

Rick C.

+ Get 1,000 miles of free Supercharging
+ Tesla referral code - https://ts.la/richard11209

Thread

Text on FSM jmariano <jmariano65@gmail.com> - 2023-03-09 14:17 -0800
  Re: Text on FSM Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-09 16:52 -0800
  Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-09 19:11 -0700
    Re: Text on FSM Bill Davy <Bill@XchelSys.co.uk> - 2023-03-10 08:37 +0000
      Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-10 03:50 -0700
  Re: Text on FSM pozz <pozzugno@gmail.com> - 2023-03-10 09:54 +0100
    Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-10 04:17 -0700
    Re: Text on FSM Robert Roland <fake@ddress.no> - 2023-03-10 12:48 +0100
      Re: Text on FSM Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-10 07:20 -0800
        Re: Text on FSM pozz <pozzugno@gmail.com> - 2023-03-13 16:35 +0100
          Re: Text on FSM StateMachineCOM <statemachineguru@gmail.com> - 2023-03-13 08:55 -0700
            Re: Text on FSM pozz <pozzugno@gmail.com> - 2023-03-14 15:44 +0100
          Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-13 09:29 -0700
            Re: Text on FSM pozz <pozzugno@gmail.com> - 2023-03-14 15:54 +0100
              Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-14 08:39 -0700
              Re: Text on FSM Niklas Holsti <niklas.holsti@tidorum.invalid> - 2023-03-14 18:49 +0200
      Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-10 09:39 -0700
        Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-10 10:02 -0700
        Re: Text on FSM Ed Prochak <edprochak@gmail.com> - 2023-03-10 10:10 -0800
          Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-10 12:10 -0700
            Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-10 12:49 -0700
            Re: Text on FSM Ed Prochak <edprochak@gmail.com> - 2023-03-10 14:02 -0800
              Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-11 06:01 -0700
                Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-11 06:17 -0700
  Re: Text on FSM StateMachineCOM <statemachineguru@gmail.com> - 2023-03-10 07:54 -0800
  Re: Text on FSM jmariano <jmariano65@gmail.com> - 2023-03-10 09:51 -0800
    Re: Text on FSM Rick C <gnuarm.deletethisbit@gmail.com> - 2023-03-10 11:27 -0800
    Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-10 12:46 -0700
    Re: Text on FSM Ed Prochak <edprochak@gmail.com> - 2023-03-10 13:11 -0800
    Re: Text on FSM Gerhard Hoffmann <dk4xp@arcor.de> - 2023-03-13 21:20 +0100
      Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-13 15:41 -0700
        Re: Text on FSM George Neuner <gneuner2@comcast.net> - 2023-03-13 23:07 -0400
          Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-13 22:59 -0700
            Re: Text on FSM George Neuner <gneuner2@comcast.net> - 2023-03-14 21:29 -0400
              Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-14 19:40 -0700
                Re: Text on FSM George Neuner <gneuner2@comcast.net> - 2023-03-22 16:37 -0400
                Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-22 18:15 -0700
                Re: Text on FSM George Neuner <gneuner2@comcast.net> - 2023-03-26 00:45 -0400
                Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-26 03:35 -0700
                Re: Text on FSM George Neuner <gneuner2@comcast.net> - 2023-03-27 02:32 -0400
                Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-27 01:16 -0700
                Re: Text on FSM George Neuner <gneuner2@comcast.net> - 2023-03-28 15:25 -0400
                Re: Text on FSM Don Y <blockedofcourse@foo.invalid> - 2023-03-28 16:56 -0700
                Re: Text on FSM Clifford Heath <no.spam@please.net> - 2023-03-27 16:18 +1100
                Re: Text on FSM George Neuner <gneuner2@comcast.net> - 2023-03-28 11:17 -0400
                Re: Text on FSM Clifford Heath <no.spam@please.net> - 2023-03-29 09:00 +1100
                Re: Text on FSM George Neuner <gneuner2@comcast.net> - 2023-03-28 21:27 -0400
                Re: Text on FSM Clifford Heath <no.spam@please.net> - 2023-03-30 08:33 +1100
                Re: Text on FSM Richard Damon <Richard@Damon-Family.org> - 2023-03-28 21:31 -0400
  Re: Text on FSM George Neuner <gneuner2@comcast.net> - 2023-03-10 16:49 -0500

csiph-web