From: John Cowan <cowan@ccil.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: SNOBOL and progeny [Was: Re: Re: Line Numbers Before SysIII nl? BSD num?]
Date: Fri, 29 Jul 2022 10:07:33 -0400 [thread overview]
Message-ID: <CAD2gp_SmXLU-MD51QSgBk2YpcoSfYHeZAFtjKCYOd6GCtXFi0g@mail.gmail.com> (raw)
In-Reply-To: <A3F3134D-6309-4818-8673-6861340BC8AA@technologists.com>
[-- Attachment #1: Type: text/plain, Size: 1401 bytes --]
On Fri, Jul 29, 2022 at 1:02 AM Charles H. Sauer <sauer@technologists.com>
wrote:
> A few experiences as SNOBOL/Icon enthusiast, not expert, ending with
> limited tie back to Unix:
> o Introduced to SNOBOL4 in introductory programming languages course
> summer 1971 U.T. Austin
> o ca 1976 used SNOBOL4 on VM/370 to build Fortran to PL/I translator "The
> elapsed time between beginning work on the translator and getting a running
> PL/I version of APLOMB was approximately two weeks, and this achievement
> was a great relief to those who anticipated a much, much larger effort."
> https://technologists.com/sauer/The_Evolution_of_the_Research_Queueing_Package.pdf
> o ca 1985 (with minimal effort) modified/built Icon to run on PC/IX, began
> emailing with Ralph Griswold
> o Discovered IBM colleague Viktors Berstis and his SNOBOL
> advocacy/expertise (http://berstis.com/)
> o ca 1986 "With help from an ISC colleague, I created a PL.8 to C
> translator using Icon, that was used to facilitate some of the rewriting.
> [of the RT/PC VRM]"
> https://notes.technologists.com/notes/2017/03/08/lets-start-at-the-very-beginning-801-romp-rtpc-aix-versions/
>
> Let us not forget Icon <https://www2.cs.arizona.edu/icon/>, Ralph
Griswold's own successor to Snobol. Well-structured, portable to Posix and
Windows, "Prolog from another point of view" (the Icon implementation is
very much like the WAM).
[-- Attachment #2: Type: text/html, Size: 3490 bytes --]
next prev parent reply other threads:[~2022-07-29 14:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-23 2:57 [TUHS] Line Numbers Before SysIII nl? BSD num? segaloco via TUHS
2022-07-23 5:56 ` [TUHS] " markus schnalke
2022-07-23 7:55 ` segaloco via TUHS
2022-07-23 11:01 ` Dan Cross
2022-07-23 11:20 ` John Cowan
2022-07-23 12:00 ` Dan Cross
2022-07-23 12:49 ` Norman Wilson
2022-07-23 13:20 ` Rob Pike
2022-07-23 13:36 ` Ralph Corderoy
2022-07-23 14:33 ` John Cowan
2022-07-24 19:45 ` Warner Losh
2022-07-24 20:33 ` segaloco via TUHS
2022-07-24 21:04 ` Warner Losh
2022-07-23 17:35 ` Clem Cole
2022-07-23 18:40 ` Phil Budne
2022-07-23 18:51 ` Nelson H. F. Beebe
2022-07-23 19:07 ` Douglas McIlroy
2022-07-24 19:02 ` Tomasz Rola
2022-07-28 0:30 ` Tomasz Rola
2022-07-28 1:03 ` Phil Budne
2022-07-28 4:13 ` [TUHS] SNOBOL and RATSNO William H. Mitchell
2022-07-29 4:28 ` [TUHS] " Dave Horsfall
2022-07-29 5:07 ` Tomasz Rola
2022-08-09 5:12 ` Jonathan Gevaryahu
2022-08-09 6:11 ` Rob Pike
2022-08-09 13:34 ` Clem Cole
2022-08-09 15:15 ` Andrew Hume
2022-08-09 18:26 ` Clem Cole
2022-08-09 18:52 ` Tom Teixeira
2022-08-09 21:25 ` Rob Pike
2022-08-09 15:39 ` Richard Salz
2022-08-09 13:56 ` Larry McVoy
2022-08-09 16:45 ` William H. Mitchell
2022-07-29 0:22 ` [TUHS] SNOBOL and progeny [Was: Re: Re: Line Numbers Before SysIII nl? BSD num?] Stuff Received
2022-07-29 5:01 ` [TUHS] " Charles H. Sauer
2022-07-29 14:07 ` John Cowan [this message]
2022-07-29 15:37 ` Dave Plonka
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=CAD2gp_SmXLU-MD51QSgBk2YpcoSfYHeZAFtjKCYOd6GCtXFi0g@mail.gmail.com \
--to=cowan@ccil.org \
--cc=tuhs@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).