From: "Charles H Sauer (he/him)" <sauer@technologists.com>
To: coff@tuhs.org
Subject: [COFF] Re: Of PL/I
Date: Tue, 2 Apr 2024 12:01:52 -0500 [thread overview]
Message-ID: <1d3f129c-eafe-4fb2-9ea2-d949f3813c88@technologists.com> (raw)
In-Reply-To: <CAC20D2NcpbggiT4fJCNTdQ8UzdU7bXsvG6+o8Hh+X32=Ut2uBA@mail.gmail.com>
On 4/2/2024 11:40 AM, Clem Cole wrote:
>
>
> On Tue, Apr 2, 2024 at 11:23 AM Dave Horsfall <dave@horsfall.org
> <mailto:dave@horsfall.org>> wrote:
>
> Has there ever been a full implementation of PL/I?
>
> Well all of the IBM, GE/Honeywell and DEC compilers were certified. Bob
> Freiburghouse (who was part of the Multics compiler if I understand this
> right), created a firm in Mass that built a number of commercial
> compilers for a number of folks, with PL/1 being their prime. In fact
> when DEC bought the PL/1 front-end from them (which was in PL/1 of
> course), Culter and team wrote the VAX back-end, they had to
> cross-compile in Cambridge (I think at MIT) and bring the assembler
> source back to ZKO in Nashua to assemble and test.
>
> It seems akin tosolving the halting problem...
>
> No more than Algol-68 and many modern languages.
>
>
> Yes, I've used PL/I in my CompSci days, and was told that IBM had
> trademarkedeverything from /I to /C :-)
>
> I think that is more like an urban legend and IBM's notorious marketing
> behavior since Gary Kidall (who was originally a compiler guy) created
> PL/M for the 8080 and sold it to Intel.
>
>
> -- Dave, who loved PL/360
>
> Yeah - it might have been Nicklaus Wirth's best language. I still have
> the Standford manuals, but I can not say I have seen a working compiler
> since the late 1970s :-)
I was ready to jump in, but since I didn't have a definitive answer, I
waited for someone (Clem) who would really know.
The vast majority of my undergraduate and graduate school work was in
CDC Fortran. When I joined IBM Yorktown in 1975, I brought that work
with me in thousands of punched cards. Initially, I continued my
simulation work in Fortran. As that work became more important, Fortran
was unacceptable. I wrote a Fortran to PL/I crude translator in SNOBOL,
had the PL/I version running in a couple of weeks, and didn't look back.
Being judicious in using just the good parts, PL/I seemed just fine.
Essentially all of my work at Yorktown was in PL/I.
The 801 people created PL.8, which was primarily a subset of the good
parts of PL/I, but with some changes that I'd have to research to remember.
Charlie
ᐧ
--
voice: +1.512.784.7526 e-mail: sauer@technologists.com
fax: +1.512.346.5240 Web: https://technologists.com/sauer/
Facebook/Google/LinkedIn/Twitter: CharlesHSauer
next prev parent reply other threads:[~2024-04-02 17:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 15:06 [COFF] " Dave Horsfall
2024-04-02 16:40 ` [COFF] " Clem Cole
2024-04-02 17:01 ` Charles H Sauer (he/him) [this message]
2024-04-03 16:18 ` Paul Winalski
2024-04-03 17:30 ` segaloco via COFF
2024-04-03 20:44 ` Paul Winalski
2024-04-04 3:37 ` Wesley Parish
2024-04-04 15:40 ` Paul Winalski
2024-04-04 22:53 ` Peter Pentchev
2024-04-07 23:10 ` Dave Horsfall
2024-04-07 23:25 ` Charles H Sauer (he/him)
2024-04-09 21:41 ` Stuff Received
2024-04-10 0:50 ` [COFF] SNOBOL, ICEBOL, SPITBOL, et al William H. Mitchell
2024-04-10 1:42 ` [COFF] " Dave Horsfall
2024-04-08 1:13 ` [COFF] Re: Of PL/I Paul Winalski
2024-04-02 19:25 ` Stuff Received
2024-04-02 20:31 ` William H. Mitchell
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=1d3f129c-eafe-4fb2-9ea2-d949f3813c88@technologists.com \
--to=sauer@technologists.com \
--cc=coff@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).