From: "Charles H Sauer (he/him)" <sauer@technologists.com>
To: coff@tuhs.org
Subject: [COFF] Re: Of PL/I
Date: Sun, 7 Apr 2024 18:25:29 -0500 [thread overview]
Message-ID: <a40818d5-245a-4291-9dc4-affb9b4a953b@technologists.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2404080905220.31370@aneurin.horsfall.org>
On 4/7/2024 6:10 PM, Dave Horsfall wrote:
> On Tue, 2 Apr 2024, Charles H Sauer (he/him) wrote:
>
> [...]
>
>> I wrote a Fortran to PL/I crude translator in SNOBOL [...]
>
> Gadzooks... For our "write a simple compiler" assignment I threatened to
> use SNOBOL, but my lecturer (Ken Robinson) threatened to fail me :-)
>
> -- Dave
SNOBOL fascinated me as soon as I learned in first languages survey
course (also covered LISP, ALGOL, others) in 1971.
In the mid 1980s, when we (IBM AIX people) wanted to move our PL.8 code
to C, I created a PL.8 to C translator in Griswold's Icon successor to
SNOBOL, then an ISC colleague took it over and enhanced it so that I
could focus on my other responsibilities. I'm told the enhanced version
was used quite a bit, but I don't really know.
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-07 23:25 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)
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) [this message]
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=a40818d5-245a-4291-9dc4-affb9b4a953b@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).