Re: Parser generator

arnold@skeeve.com (Aharon Robbins)
Wed, 11 Jan 2012 20:06:55 +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)
Re: programming in PL/I compilers@is-not-my.name (2012-01-12)
Re: programming in PL/I robert@prino.org (Robert AH Prins) (2012-01-14)
Re: programming in PL/I derek@_NOSPAM_knosof.co.uk (Derek M. Jones) (2012-01-14)
[2 later articles]
| List of all articles for this month |
From: arnold@skeeve.com (Aharon Robbins)
Newsgroups: comp.compilers
Date: Wed, 11 Jan 2012 20:06:55 +0000 (UTC)
Organization: A noiseless patient Spider
References: 12-01-009 12-01-010
Keywords: parse, PL/I, comment
Posted-Date: 11 Jan 2012 16:10:36 EST

glen herrmannsfeldt <gah@ugcs.caltech.edu> wrote:
>Dennis Boone <drb@msu.edu> wrote:
>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.


Are there PL/I compilers available for modern platforms? E.g. Windows,
Linux 32 and 64 bit Intel, sparc, power pc, etc.... (I see there was
a start at one for GCC.)


Is there a reason to prefer PL/I over C++ or Java?


Just wondering.


Thanks,


Arnold
--
Aharon (Arnold) Robbins arnold AT skeeve DOT com
P.O. Box 354 Home Phone: +972 8 979-0381
Nof Ayalon Cell Phone: +972 50 729-7545
D.N. Shimshon 99785 ISRAEL
[Yes, there's PL/I for a surprising array of computers. If you're doing a
lot of formatted I/O it's a considerable improvement over its
successors. -John]

Post a followup to this message

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