The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Bell Labs CSTRs
Date: Thu, 29 Jun 2023 10:14:30 -0500	[thread overview]
Message-ID: <eb714b9c-2ce6-33b6-5999-28890a114e00@gmail.com> (raw)
In-Reply-To: <CAC20D2OsxRwG7GDs6aH-qO2WQLDZyh__n8YL15pLXM7XJX=4xQ@mail.gmail.com>

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

On a related note, I just read cstr 99 - Bell's computing research 
history and one of Doug's early articles was mentioned:

M. D. McIlroy, "Macro Instruction Extension of Compiler Languages," 
Communications of the
ACM 3 (April 1960), pp. 214-220.

It's discussing the general extensibility that macros provide and I was 
interested to obtain a copy to read at leisure. I found it over on ACM's 
digital library:

https://dl.acm.org/doi/pdf/10.1145/367177.367223

But, the copy's not that great on my deteriorating eyesight. Does 
anybody have a cleaner copy?

Lately, I've been vastly improving my vi/vim skills and part of that 
process is shifting from an ad-hoc process to a move, act, repeat 
mentality (thank you Drew Neil for that revelation) and macros are 
consonant with this line of thinking :).

Will


On 6/29/23 09:40, Clem Cole wrote:
> +1 👍
> ᐧ
>
> On Thu, Jun 29, 2023 at 3:37 AM Noel Hunt <noel.hunt@gmail.com> wrote:
>
>     Many thanks.
>
>     On Thu, 29 Jun 2023 at 17:14, <arnold@skeeve.com> wrote:
>     >
>     > Available at https://www.skeeve.com/bell-labs-cstrs.tar.gz
>     >
>     > Warren and Brantley and anyone else, feel free to retrieve.
>     >
>     > I have two sets - both are in the tarball so there are undoubtedly
>     > duplications.  If someone else can curate them into single canonical
>     > set that'd be helpful, I just don't have the time right now.
>     >
>     > Enjoy,
>     >
>     > Arnold
>

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

  parent reply	other threads:[~2023-06-29 15:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29  7:14 [TUHS] " arnold
2023-06-29  7:36 ` [TUHS] " Noel Hunt
2023-06-29 14:40   ` Clem Cole
2023-06-29 15:04     ` Will Senn
2023-07-01 17:28       ` Dan Cross
2023-07-01 18:03         ` segaloco via TUHS
2023-07-01 18:42           ` Dan Cross
2023-06-29 15:14     ` Will Senn [this message]
2023-08-26 17:02 Nelson H. F. Beebe
2023-08-27  3:13 ` Jonathan Gray

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=eb714b9c-2ce6-33b6-5999-28890a114e00@gmail.com \
    --to=will.senn@gmail.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).