The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Bakul Shah <bakul@iitbombay.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] v7 source code for sh
Date: Sun, 20 Feb 2022 05:44:46 +1100	[thread overview]
Message-ID: <CAKzdPgzn8V2zykc-NtVW=Kgz62vtRwmtQD7u_mGf6U=b6VXJtA@mail.gmail.com> (raw)
In-Reply-To: <8102A7AB-21F5-477D-8D37-5412103CD396@iitbombay.org>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

I undid all the macros for the v8 shell, with Steve's blessing, before
doing the key work on that shell. But no one outside cared about any of the
research Unixes after v7, sad though that is to admit, so his macros and
griping about them lingered on in the world.

I did the same to adb, which turned out to have a really good debugger
hidden under a few serious bugs of its own, which I fixed.

-rob


On Sun, Feb 20, 2022 at 4:46 AM Bakul Shah <bakul@iitbombay.org> wrote:

> On Feb 19, 2022, at 8:11 AM, Clem Cole <clemc@ccc.com> wrote:
>
> 
> On Sat, Feb 19, 2022 at 11:04 AM Steve Nickolas <usotsuki@buric.co> wrote:
>
>> Apparently Bourne was heavily into ALGOL,
>>
> That's sort of an understatement.  I believe that when he was at
> Cambridge, he was one of the people that helped to take the Algol-X
> proposal and turned it into the Algol-68 definition. I also believe he
> worked on their famous implementation of same.
>
>
> Some of you may be interested in this “A history of Algol68” paper:
> https://dl.acm.org/doi/pdf/10.1145/234286.1057810
> The author, Charles H Lindsey, still occasionally posts on comp.lang.misc
> about Algol68. Among other things Bourne was a coauthor of Algol68C,
> a portable implementation of Algol68.
>

[-- Attachment #2: Type: text/html, Size: 2324 bytes --]

  reply	other threads:[~2022-02-19 18:45 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-19 17:44 Bakul Shah
2022-02-19 18:44 ` Rob Pike [this message]
2022-02-19 19:29   ` Clem Cole
2022-02-19 22:39   ` John Cowan
2022-02-19 23:11     ` Sven Mascheck
2022-02-19 23:34       ` Rob Pike
2022-02-19 23:36       ` silas poulson
2022-02-20 20:54       ` Chet Ramey
2022-02-20 21:02         ` Larry McVoy
2022-02-20 21:19           ` Chet Ramey
2022-02-20 21:19         ` Lyndon Nerenberg (VE7TFX/VE6BBM)
2022-02-20 22:39           ` Chet Ramey
2022-02-21  1:01             ` Dan Cross
2022-02-22  4:54               ` Dan Stromberg
2022-02-22  5:39                 ` Rob Pike
2022-02-22  5:54                   ` George Michaelson
  -- strict thread matches above, loose matches on Subject: below --
2022-02-22  3:07 Brian Walden
2022-02-22 14:28 ` Chet Ramey
2022-02-22 14:47 ` Clem Cole
2022-02-21 17:58 Norman Wilson
2022-02-21 18:10 ` Rob Pike
2022-02-20  7:24 Rudi Blom
2022-02-19 15:43 Will Senn
2022-02-19 16:03 ` Steve Nickolas
2022-02-19 16:07   ` Clem Cole
2022-02-19 16:43   ` Steve Nickolas
2022-02-19 17:24   ` Ron Natalie
2022-02-19 16:04 ` Clem Cole
2022-02-19 16:06 ` Bakul Shah
2022-02-19 16:57   ` Will Senn

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='CAKzdPgzn8V2zykc-NtVW=Kgz62vtRwmtQD7u_mGf6U=b6VXJtA@mail.gmail.com' \
    --to=robpike@gmail.com \
    --cc=bakul@iitbombay.org \
    --cc=tuhs@minnie.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).