The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: arnold@skeeve.com
To: robpike@gmail.com, beebe@math.utah.edu
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] [tuhs] Dennis Ritchie's couch
Date: Tue, 25 May 2021 23:13:12 -0600	[thread overview]
Message-ID: <202105260513.14Q5DCBu016940@freefriends.org> (raw)
In-Reply-To: <CAKzdPgzJsQKMx5BB3sybzAd2HRUnd6L0K-akVepL+538_UOC2w@mail.gmail.com>

As a quite serious question, what do you use instead? Hand-written
recursive descent?  Some other form of machine generated parser?

Thanks,

Arnold

Rob Pike <robpike@gmail.com> wrote:

> And today, we understand parsing so well we don't need yacc.
>
> -rob
>
>
> On Wed, May 26, 2021 at 10:20 AM Nelson H. F. Beebe <beebe@math.utah.edu>
> wrote:
>
> > The last article of the latest issue of the Communications of the ACM
> > that appeared electronically earlier today is a brief interview with
> > this year's ACM Turing Award winners, Al Aho and Jeff Ullman.
> >
> > The article is
> >
> >         Last byte: Shaping the foundations of programming languages
> >         https://doi.org/10.1145/3460442
> >         Comm. ACM 64(6), 120, 119, June 2021.
> >
> > and it includes a picture of the two winners sitting on Dennis
> > Ritchie's couch.
> >
> > I liked this snippet from Jeff Ullman, praising fellow list member
> > Steve Johnson's landmark program, yacc:
> >
> > >> ...
> > >> At the time of the first Fortran compiler, it took several
> > >> person-years to write a parser.  By the time yacc came around,
> > >> you could do it in an afternoon.
> > >> ...
> >
> >
> > -------------------------------------------------------------------------------
> > - Nelson H. F. Beebe                    Tel: +1 801 581 5254
> >     -
> > - University of Utah                    FAX: +1 801 581 4148
> >     -
> > - Department of Mathematics, 110 LCB    Internet e-mail:
> > beebe@math.utah.edu  -
> > - 155 S 1400 E RM 233                       beebe@acm.org
> > beebe@computer.org -
> > - Salt Lake City, UT 84112-0090, USA    URL:
> > http://www.math.utah.edu/~beebe/ -
> >
> > -------------------------------------------------------------------------------
> >

  parent reply	other threads:[~2021-05-26  5:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-26  0:12 Nelson H. F. Beebe
2021-05-26  0:37 ` Rob Pike
2021-05-26  3:03   ` Larry McVoy
2021-05-26  4:02     ` Rob Pike
2021-05-26  6:20     ` Bakul Shah
2021-05-26  6:52       ` Rob Pike
2021-07-02  2:13         ` scj
2021-07-02  3:30           ` Rob Pike
2021-07-02  3:34             ` Rob Pike
2021-07-02  4:40               ` Rob Pike
2021-07-02  6:29                 ` George Michaelson
2021-07-02  7:00                   ` Bakul Shah
2021-07-02 17:17                     ` [TUHS] " Tony Finch
2021-07-04 23:40                       ` George Michaelson
2021-07-05  3:41                         ` Bakul Shah
2021-05-26  5:13   ` arnold [this message]
2021-05-26  4:10 ` [TUHS] [tuhs] " Avindra G

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=202105260513.14Q5DCBu016940@freefriends.org \
    --to=arnold@skeeve.com \
    --cc=beebe@math.utah.edu \
    --cc=robpike@gmail.com \
    --cc=tuhs@minnie.tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).