From: Rob Pike <robpike@gmail.com>
To: Norman Wilson <norman@oclsc.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Origins and life of the pg pager
Date: Tue, 16 Jun 2020 07:36:42 +1000 [thread overview]
Message-ID: <CAKzdPgy07hwixLdUAqLyS9iZLxbn1h=YwntZt78uKeYvyOtEQw@mail.gmail.com> (raw)
In-Reply-To: <1592252735.3176.for-standards-violators@oclsc.org>
[-- Attachment #1: Type: text/plain, Size: 1390 bytes --]
I had forgotten about that tool, along with many others. "Comp" sounds
plausible but as I said, I forget. (Not a sign of age; my memory for
details is no match for Clem's; to me stage actors are superheroes).
I do remember the tool existing, though, and now see it as related to a
long list of similar things, including "go generate". I wonder if my
subconscious held on to it.
This history stuff is fun because of the reminder of a time when tools were
simple and you could create a whole new one in an afternoon.
-rob
On Tue, Jun 16, 2020 at 6:26 AM Norman Wilson <norman@oclsc.org> wrote:
> Rob Pike:
>
> Yeah, p is all we need. I think it originated with td at UofT. I might
> have
> brought it with me to Bell Labs, or recreated it. Probably the former.
>
> ====
>
> The former, I think. The source code in V10 is very similar
> to that you left behind at Caltech (where I first encountered
> p). Most differences have to do with using opendir and readdir
> rather than reading raw directories in the SPname code.
>
> A further clue is that, even in V10, p.c begins
>
> /*%cc p.c pad.o spname.o
> */
>
> The tool that looked for such lines to tell it how to compile
> things (I forget its name; was it comp?) doesn't seem to have
> survived in the archival backup I have from Caltech HEP, but
> I'm quite sure it came from U of T as well.
>
> Norman Wilson
> Toronto ON
>
[-- Attachment #2: Type: text/html, Size: 1864 bytes --]
next prev parent reply other threads:[~2020-06-15 21:37 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 20:25 Norman Wilson
2020-06-15 21:36 ` Rob Pike [this message]
2020-06-15 22:55 ` Henry Bent
-- strict thread matches above, loose matches on Subject: below --
2020-06-15 2:26 Doug McIlroy
2020-06-15 2:41 ` Bakul Shah
2020-06-15 2:55 ` Larry McVoy
2020-06-15 4:26 ` Rob Pike
2020-06-15 4:27 ` Bakul Shah
2020-06-15 4:38 ` George Michaelson
2020-06-15 7:40 ` Ed Carp
2020-06-15 8:17 ` Rob Pike
2020-06-15 7:12 ` Thomas Paulsen
2020-06-14 22:52 [TUHS] Fwd: " Warren Toomey
2020-06-14 23:37 ` Mary Ann Horton
2020-06-14 23:52 ` [TUHS] " David Barto
2020-06-15 0:06 ` George Michaelson
2020-06-15 0:31 ` Alan D. Salewski
2020-06-15 0:35 ` Alan D. Salewski
2020-06-15 1:38 ` Warner Losh
2020-06-15 1:47 ` Larry McVoy
2020-06-15 2:38 ` Alec Muffett
2020-06-15 2:46 ` Alec Muffett
2020-06-15 2:26 ` Charles H. Sauer
2020-06-15 14:03 ` Mary Ann Horton
2020-06-15 20:19 ` Greg A. Woods
2020-06-15 20:50 ` Mary Ann Horton
2020-06-15 5:41 ` [TUHS] Fwd: " Lars Brinkhoff
2020-06-15 13:56 ` Clem Cole
2020-06-15 14:15 ` Mary Ann Horton
2020-06-15 14:56 ` Clem Cole
2020-06-21 18:49 ` Michael Siegel
2020-06-22 0:35 ` Greg A. Woods
2020-06-22 16:24 ` Derek Fawcus
2020-06-22 21:33 ` Rob Pike
2020-06-22 21:59 ` [TUHS] " Bakul Shah
2020-06-22 22:43 ` Steffen Nurpmeso
2020-06-25 1:50 ` Theodore Y. Ts'o
2020-06-25 21:31 ` Steffen Nurpmeso
2020-07-05 1:34 ` Dave Horsfall
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='CAKzdPgy07hwixLdUAqLyS9iZLxbn1h=YwntZt78uKeYvyOtEQw@mail.gmail.com' \
--to=robpike@gmail.com \
--cc=norman@oclsc.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).