Groups | Search | Server Info | Login | Register


Groups > sci.electronics.design > #735116

Re: ANY(ONE can code

From Don Y <blockedofcourse@foo.invalid>
Newsgroups sci.electronics.design
Subject Re: ANY(ONE can code
Date 2025-08-22 02:18 -0700
Organization A noiseless patient Spider
Message-ID <1089cl4$1eod8$2@dont-email.me> (permalink)
References <107aa7p$1uov7$1@dont-email.me> <107cmnu$2hrjf$1@dont-email.me> <107dfoq$2qgg8$1@dont-email.me> <0ki6akht4lpcbkn23vjjuofdnu3c2q1en0@4ax.com> <1089be3$dsns$4@solani.org>

Show all headers | View raw


On 8/22/2025 1:57 AM, Gerhard Hoffmann wrote:
> You learn that when you write your 1st grammar parser
> using YACC or bison.   :-)

But, we call them DFA/NFA -- something hardware people never
get exposed to.  So, they don't think in terms of grammars
but, rather, just collections of states and events.  It
makes documenting what the automaton is intended to do
considerably harder.  Especially for anything beyond a
trivial machine (consider the state explosion problem that
you can "bury/hide" in a grammar)

[You can also get flex -- though not lex -- to build some
crude DFAs.  And, any regex compiler.  A *lot* closer to
self-documenting than anything you can build in hardware!]

Back to sci.electronics.design | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

ANY(ONE can code Don Y <blockedofcourse@foo.invalid> - 2025-08-10 07:27 -0700
  Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-11 02:09 +1000
  Re: ANY(ONE can code BillGill <tonisdad215@gmail.com> - 2025-08-11 07:12 -0500
    Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-11 07:22 -0700
    Re: ANY(ONE can code Don Y <blockedofcourse@foo.invalid> - 2025-08-11 07:27 -0700
      Re: ANYONE can code Don Y <blockedofcourse@foo.invalid> - 2025-08-11 07:46 -0700
      Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-11 08:50 -0700
        Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-12 03:32 +1000
          Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-11 16:19 -0700
            Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-12 16:19 +1000
              Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-12 07:37 -0700
                Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-13 15:28 +1000
                Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-17 02:17 +1000
                Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-16 13:40 -0700
                Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-17 14:35 +1000
                Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-17 08:31 -0700
                Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-18 02:47 +1000
                Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-17 10:23 -0700
                Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-18 21:08 +1000
                Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-18 07:10 -0700
                Re: ANY(ONE can code Joe Gwinn <joegwinn@comcast.net> - 2025-08-18 10:57 -0400
                Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-18 08:44 -0700
                Re: ANY(ONE can code Gerhard Hoffmann <dk4xp@arcor.de> - 2025-08-22 09:54 +0200
                Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-22 07:39 -0700
                Re: ANY(ONE can code Gerhard Hoffmann <dk4xp@arcor.de> - 2025-08-22 17:21 +0200
                Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-22 08:47 -0700
                Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-19 17:12 +1000
                Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-19 04:09 -0700
                Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-20 00:53 +1000
                Re: ANY(ONE can code Gerhard Hoffmann <dk4xp@arcor.de> - 2025-08-22 10:45 +0200
                Re: ANY(ONE can code Don Y <blockedofcourse@foo.invalid> - 2025-08-22 02:14 -0700
                Re: ANY(ONE can code Phil Hobbs <pcdhSpamMeSenseless@electrooptical.net> - 2025-08-22 11:41 +0000
                Re: ANY(ONE can code Buzz McCool <buzz_mccool@yahoo.com> - 2025-08-22 09:44 -0700
                Re: ANY(ONE can code Gerhard Hoffmann <dk4xp@arcor.de> - 2025-08-22 09:37 +0200
    Re: ANY(ONE can code Don Y <blockedofcourse@foo.invalid> - 2025-08-11 12:19 -0700
      Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-18 08:47 -0700
        Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-19 17:19 +1000
          Re: ANY(ONE can code bitrex <user@example.net> - 2025-08-22 20:52 -0400
        Re: ANY(ONE can code Gerhard Hoffmann <dk4xp@arcor.de> - 2025-08-22 10:57 +0200
          Re: ANY(ONE can code Don Y <blockedofcourse@foo.invalid> - 2025-08-22 02:18 -0700
            Re: ANY(ONE can code Gerhard Hoffmann <dk4xp@arcor.de> - 2025-08-22 11:39 +0200
              Re: ANY(ONE can code Don Y <blockedofcourse@foo.invalid> - 2025-08-22 03:09 -0700
                Re: ANY(ONE can code Don Y <blockedofcourse@foo.invalid> - 2025-08-22 11:51 -0700
            Re: ANY(ONE can code john larkin <jl@glen--canyon.com> - 2025-08-22 07:54 -0700
              Re: ANY(ONE can code Bill Sloman <bill.sloman@ieee.org> - 2025-08-23 02:11 +1000

csiph-web