The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@bitblocks.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] In Memoriam: Per Brinch Hansen
Date: Thu, 2 Aug 2018 08:44:01 -0700	[thread overview]
Message-ID: <170A1322-620F-46EE-8BA3-8BF295EC6E3A@bitblocks.com> (raw)
In-Reply-To: <20180802140734.GC24473@mcvoy.com>

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

I think it is this one: http://bitsavers.org/pdf/regnecentralen/RC_4000_Reference_Manual_Jun69.pdf

Along these lines, at least one of Fujitsu’s high end network switches was described using PowerPoint slides. At one point while working for them I felt a software simulator of the switch would really help with testing switch software. So I started developing one on my own. That is when I discovered these slides were not only very detailed but also very accurate and quite clear. They answered every question I had during the development. I have never seen such /engineering/ use of PowerPoint anywhere else.

> On Aug 2, 2018, at 7:07 AM, Larry McVoy <lm@mcvoy.com> wrote:
> 
> I suspect not, I suspect his first reference is the one you want.
> 
>> On Thu, Aug 02, 2018 at 09:10:54AM -0400, Ben Greenfield via TUHS wrote:
>> Is this a weblink to that manual?
>> 
>> I want to read something so well written:)
>> 
>> Ben
>> 
>> https://pdfs.semanticscholar.org/b77f/02dedb784a52229c5376277173c5ef6da5c1.pdf
>> 
>>> On Aug 2, 2018, at 8:44 AM, Doug McIlroy <doug@cs.dartmouth.edu> wrote:
>>> 
>>> A tangential connection to early Unix experience:
>>> 
>>> My collection of early computer manuals includes Brinch Hansen's manual
>>> for the RC 4000, which stands out for its precise description of the
>>> CPU logic--in Algol 60! It's the only manual I have seen that offers a
>>> good-to-the-last-bit formal description of the hardware.
>>> 
>>> DEC presented something of the sort for the PDP-11, but punted where
>>> the woods got thick. When I wanted to know how they computed the last
>>> bit of floating-point results, I got no satisfaction. Amidst a thorough
>>> description of addressing came this formulation of the actual computation:
>>> "form floating point result".
>>> 
>>> Doug
> 
> -- 
> ---
> Larry McVoy                     lm at mcvoy.com             http://www.mcvoy.com/lm 

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

  reply	other threads:[~2018-08-02 15:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-02 12:44 Doug McIlroy
2018-08-02 13:10 ` Ben Greenfield via TUHS
2018-08-02 14:07   ` Larry McVoy
2018-08-02 15:44     ` Bakul Shah [this message]
2018-08-05 23:18 ` Perry E. Metzger
  -- strict thread matches above, loose matches on Subject: below --
2018-07-31  0:40 Dave Horsfall
2018-07-31  1:10 ` Toby Thain
2018-07-31  7:25   ` Wesley Parish

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=170A1322-620F-46EE-8BA3-8BF295EC6E3A@bitblocks.com \
    --to=bakul@bitblocks.com \
    --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).