From: alex at bochannek.com (Alex Bochannek)
Subject: [COFF] [TUHS] AP-3 minicomputer
Date: Fri, 20 Dec 2019 09:14:24 -0800 [thread overview]
Message-ID: <m2v9qahqbz.fsf@bochannek.com> (raw)
In-Reply-To: <CAEoi9W7faOgFNxW-NtXtLjGys8ThGwbVKM7Kvqv+qG8PeEquZg@mail.gmail.com> (Dan Cross's message of "Fri, 20 Dec 2019 03:49:49 -0500")
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1841 bytes --]
Dan Cross <crossd at gmail.com> writes:
> On Wed, Dec 18, 2019 at 1:52 PM Paul McJones <paul at mcjones.org>
> wrote:
>
> Computer History Museum curator Dag Spicer passed along a
> question from former CHM curator Alex Bochannek that I thought
> someone on this list might be able to answer. The paper "The M4
> Macro Processor” by Kernighan and Ritchie says:
>
> > The M4 macro processor is an extension of a macro processor
> called M3 which was written by D. M. Ritchie for the AP-3
> minicomputer; M3 was in turn based on a macro processor
> implemented for [B. W. Kernighan and P. J. Plauger, Software
> Tools, Addison-Wesley, Inc., 1976].
>
> Alex and Dag would like to learn more about this AP-3
> minicomputer — can anyone help?
>
>
> [I recommend that follow-ups go to coff, which is Cc'ed here]
>
> I took a short stab at this, but can find little beyond references in
> the aforementioned M4 paper.
>
> I did, however, run across this: https://www.cia.gov/library/
> readingroom/document/cia-rdp78b04770a000100110018-1
>
> This appears to be a declassified letter written to the US Air Force
> at Bowling Green Air Force Base in regards to spare parts fo the AP-3
> computer; dated October 19, 1966. The list of parts seem reasonable
> for a minicomputer, and it further seems reasonable to believe that
> this may be related to the same type of computer referenced in the M4
> paper. However, details of the sending party have been redacted, and
> there is nothing pointing to the identity of the manufacturer.
Good find. The part numbers suggest Bendix.
> Sadly, that's all that seems available. I wonder if, perhaps, Doug
> McIlroy (Cc'ed directly to float this to the top of his stack) can
> shed more light on the topic?
>
> - Dan C.
>
>
>
--
Alex.
next prev parent reply other threads:[~2019-12-20 17:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0FCF3C9F0F6C2441BC6C13C6E49BAEF101DC35B21D@EX-MB1.hq.computerhistory.org>
[not found] ` <4C8A6FE1-3A6E-4F28-AABE-793AABD3F4C4@mcjones.org>
2019-12-20 8:49 ` crossd
2019-12-20 13:30 ` ats
2019-12-20 17:14 ` alex [this message]
2019-12-23 19:50 ` dspicer
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=m2v9qahqbz.fsf@bochannek.com \
--to=coff@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).