From: Lars Brinkhoff <lars@nocrew.org>
To: "Steve Johnson" <scj@yaccman.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] Archaic yacc C grammar
Date: Mon, 29 Oct 2018 07:31:24 +0000 [thread overview]
Message-ID: <7wftwpi4z7.fsf@junk.nocrew.org> (raw)
In-Reply-To: <1dbc3d888e7be7a2c93e497eac14bcd9f43c72fc@webmail.yaccman.com> (Steve Johnson's message of "Sun, 28 Oct 2018 20:00:42 -0700")
Steve Johnson wrote:
> Looking at the reserved words, there is one, ENTRY, that I've never
> heard of (although FORTRAN had an ENTRY statement), and there is
> STRUCT but no UNION. Also, he uses val= instead of $$=. There don't
> seem to be any nontrivial assignment ops (neither += or =+).
This is for Snyder's C compiler. There is something called =op which
is guess is for =+ etc.
> I'm guessing either Al wrote it from scratch or based it on some other
> similar program.
Looks like you're right. I found this in another file, so it would seem
he wrote it back at MIT:
"The original YACC was designed and implemented on a PDP-11/45 and a
Honeywell 6000 by S. C. Johnson at Bell Laboratories. The version
described in this paper was implemented on the PDP-10 by Alan Snyder.
next prev parent reply other threads:[~2018-10-29 8:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-28 21:34 Lars Brinkhoff
2018-10-29 3:00 ` Steve Johnson
2018-10-29 7:31 ` Lars Brinkhoff [this message]
2018-10-29 17:52 ` Steve Johnson
2018-10-29 18:37 ` Warner Losh
2018-10-30 8:16 ` Lars Brinkhoff
2018-11-03 21:50 ` Steve Johnson
2018-10-29 19:02 ` David
2018-10-30 22:01 ` Steve Johnson
2018-10-31 0:58 ` Larry McVoy
2018-10-31 13:49 ` Clem Cole
2018-11-03 22:14 ` Steve Johnson
2018-10-31 6:09 ` Lars Brinkhoff
2018-10-31 15:39 Noel Chiappa
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=7wftwpi4z7.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=scj@yaccman.com \
--cc=tuhs@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).