Re: ALGOLW parser

gah4 <>
Wed, 27 Jul 2022 13:36:09 -0700 (PDT)

          From comp.compilers

Related articles
ALGOLW parser (gah4) (2022-07-26)
Re: ALGOLW parser (gah4) (2022-07-27)
Re: ALGOLW parser (gah4) (2022-07-27)
| List of all articles for this month |

From: gah4 <>
Newsgroups: comp.compilers
Date: Wed, 27 Jul 2022 13:36:09 -0700 (PDT)
Organization: Compilers Central
References: 22-07-048 22-07-050
Injection-Info:; posting-host=""; logging-data="7518"; mail-complaints-to=""
Keywords: parse, history, comment
Posted-Date: 27 Jul 2022 17:47:19 EDT
In-Reply-To: 22-07-050

On Wednesday, July 27, 2022 at 11:01:09 AM UTC-7, gah4 wrote:
> (I wrote)

> It seems that in addition to the listings, the source of the MTS
> ALGOLW compiler from some years later is available. The low
> level I/O routines and other OS specific parts will be different,
> but the internal compiler routines should be close.

And our moderator wrote:
> [Well, whaddaya know. The PL360 table generator that reads the BNF is
> just before the BNF, starting on page 81. -John]


Since I didn't know where to start, and especially as I want to compare to the
MTS source, I was going through looking for PROCEDURE statements
(and for CSECT in the assembly code). I wanted a rough idea about
how the modules went together, without too many details.

I did notice that the one on page 81 didn't start with PROCEDURE,
and thought that was strange, but it didn't occur to me that it was a
completely different program.

(Even though that is the obvious reason.)

So, what was usual for parser generators in 1969?

I also noted a linkage editor map for a PL/I (F) program named ALPHA,
though the program itself seems not to be there. I was, just a little,
suspecting that was the program to read it.

[My recollection is that there were a lot of programs that would read some
form of BNF and create parser tables, but yacc was the first one that let
you interspese the rules and the action code which made it a lot easier
to use. -John]

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.