|Re: Parser generator firstname.lastname@example.org (2012-01-08)|
|Re: Parser generator email@example.com (glen herrmannsfeldt) (2012-01-08)|
|Re: Parser generator firstname.lastname@example.org (SLK Systems) (2012-01-08)|
|Re: Parser generator email@example.com (glen herrmannsfeldt) (2012-01-11)|
|Re: Parser generator firstname.lastname@example.org (2012-01-11)|
|Re: PL/I, was Parser generator email@example.com (2012-01-11)|
|Re: PL/I, was Parser generator firstname.lastname@example.org (Robert AH Prins) (2012-01-11)|
|Re: Parser generator email@example.com (SLK Systems) (2012-01-11)|
|[7 later articles]|
|From:||glen herrmannsfeldt <firstname.lastname@example.org>|
|Date:||Sun, 8 Jan 2012 21:58:47 +0000 (UTC)|
|Organization:||Aioe.org NNTP Server|
|Posted-Date:||11 Jan 2012 00:42:16 EST|
Dennis Boone <email@example.com> 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
> [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).
Return to the
Search the comp.compilers archives again.