Re: Parser generator

glen herrmannsfeldt <gah@ugcs.caltech.edu>
Sun, 8 Jan 2012 21:58:47 +0000 (UTC)

          From comp.compilers
Related articles
Re: Parser generator drb@msu.edu (2012-01-08)
Re: Parser generator gah@ugcs.caltech.edu (glen herrmannsfeldt) (2012-01-08)
Re: Parser generator slkpg3@gmail.com (SLK Systems) (2012-01-08)
Re: Parser generator gah@ugcs.caltech.edu (glen herrmannsfeldt) (2012-01-11)
Re: Parser generator arnold@skeeve.com (2012-01-11)
Re: PL/I, was Parser generator drb@ihatespam.msu.edu (2012-01-11)
Re: PL/I, was Parser generator robert@prino.org (Robert AH Prins) (2012-01-11)
Re: Parser generator slkpg3@gmail.com (SLK Systems) (2012-01-11)
[7 later articles]
| List of all articles for this month |
From: glen herrmannsfeldt <gah@ugcs.caltech.edu>
Newsgroups: comp.compilers
Date: Sun, 8 Jan 2012 21:58:47 +0000 (UTC)
Organization: Aioe.org NNTP Server
References: 12-01-009
Keywords: parse, PL/I
Posted-Date: 11 Jan 2012 00:42:16 EST

Dennis Boone <drb@msu.edu> wrote:


> I'm looking for a parser generator that generates output in PL/I.
> That is, in the same way that there are variants of yacc that generate


(snip)


> [In the 35 years I've been in this biz, I've never seen one. It wouldn't
> be hard in principle to translate the parser skeleton in bison or yacc to
> generate PL/I, but it'd still be a chunk of work. -John]


One reason that I learned C was that none of the computers I was using
at the time had PL/I compilers. PL/I was much more fun to write than
Fortran 66 or even Fortran 77.


Most C statements should translate fairly easy into PL/I, such that
you could almost do it statement by statement.


Not having actually looked at the code recently, it might be that it
could be done using an automated system of some kind, possibly even
written with flex and yacc (or bison).


-- glen

Post a followup to this message

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