From: "William H. Mitchell" <whm@msweng.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: SNOBOL and RATSNO
Date: Tue, 9 Aug 2022 09:45:53 -0700 [thread overview]
Message-ID: <444E7F34-EBFF-4BCD-9138-665BEB88B164@msweng.com> (raw)
In-Reply-To: <CAKzdPgzAOAt4pdw7-AE226zxoubNjJeAhYmAfKMOxWCO4H2d-Q@mail.gmail.com>
A cool thing you buy in those days was the full source code for SPITBOL, on microfiche. I bought a copy and a number of my friends did, too. It was really beautiful code.
> On Aug 8, 2022, at 11:11 PM, Rob Pike <robpike@gmail.com> wrote:
>
> We're probably well off topic now but...
>
> Many years ago I ran into Bob Dewar on a visit to Cambridge University and we got to talking. He said that the original implementation of SPITBOL, for the System/360, was in assembler (of course), and written by him and Belcher (?). The story he told was that they wrote it all down first, put it on punch cards, and sent it to the IBM machine. The next day they got back a listing with a bunch of errors. They iterated. By the fourth round—fifth day—they had a working SPITBOL.
>
> I still marvel at the productivity and precision of his generation of programmers.
>
> -rob
next prev parent reply other threads:[~2022-08-09 16:46 UTC|newest]
Thread overview: 52+ 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 [this message]
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
2022-07-29 15:37 ` Dave Plonka
2022-08-09 17:42 [TUHS] Re: SNOBOL and RATSNO Noel Chiappa
2022-08-09 18:49 ` Larry McVoy
2022-08-09 18:54 ` Tom Teixeira
2022-08-09 19:00 ` Larry McVoy
2022-08-09 19:21 ` Marshall Conover
2022-08-09 20:19 ` Warner Losh
2022-08-10 21:13 ` Bill Cheswick
2022-08-10 21:30 ` John Cowan
2022-08-11 16:08 ` Marc Donner
2022-08-09 22:18 Douglas McIlroy
2022-08-09 22:25 ` Larry McVoy
2022-08-10 15:05 ` arnold
2022-08-10 17:14 ` Larry McVoy
2022-08-10 17:37 ` arnold
2022-08-10 18:24 ` joe mcguckin
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=444E7F34-EBFF-4BCD-9138-665BEB88B164@msweng.com \
--to=whm@msweng.com \
--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).