The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rich Morin <rdm@cfcl.com>
To: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] The most surprising Unix programs
Date: Fri, 20 Mar 2020 11:43:05 -0700	[thread overview]
Message-ID: <FE7F5013-ABB8-40EB-B8FB-01C974DCCACA@cfcl.com> (raw)
In-Reply-To: <202003201640.02KGerlG470796@darkstar.fourwinds.com>

Back in the 70's, I bought an HP-67 for some ridiculous amount of money.  I only wrote one significant program on it, but I think folks here might find the idea interesting.  My X-Ray astronomy project at NRL (HEAO A1) was using a CDC 3800 for data analysis.  The machine had 48-bit words and used octal to display binary values.  I decided to write a program to convert the binary representation of a floating point number into the numeric value.

For starters, it had to accept a pair of 24-bit values, expressed in (mock) octal.  That is, when I entered 12345, it was actually 12345(8), not 12345(10).  So, the program had to turn these values back into real integers.  It then pulled out the exponent and mantissa, did the appropriate calculations, and displayed the floating-point value.  It worked, but it wasn't all that fast.  As I recall, it took about 30 seconds...

-r


  parent reply	other threads:[~2020-03-20 18:43 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-13 23:31 Doug McIlroy
2020-03-14  0:40 ` Dave Horsfall
2020-03-14 11:30 ` Harald Arnesen
2020-03-14 12:24   ` Clem Cole
2020-03-15 22:01     ` Rob Pike
2020-03-15 22:14       ` Larry McVoy
2020-03-15 23:34         ` Warner Losh
2020-03-16  2:45           ` Anthony Martin
2020-03-15 22:30       ` Clem Cole
2020-03-15 23:20       ` Dave Horsfall
2020-03-16  0:56         ` Rob Pike
2020-03-20 23:20           ` Dave Horsfall
2020-03-20 23:35             ` Toby Thain
2020-03-21  0:34             ` Rob Pike
2020-03-17 13:03 ` ca6c
2020-03-17 13:30   ` Andy Kosela
2020-03-17 14:53     ` Cág
2020-03-17 14:57       ` Larry McVoy
2020-03-17 14:59         ` Arrigo Triulzi
2020-03-17 15:40   ` Steve Nickolas
2020-03-17 22:28   ` Dave Horsfall
2020-03-18  0:17     ` Jon Steinhart
2020-03-18  3:28       ` Dave Horsfall
2020-03-18  8:40     ` arnold
2020-03-19 12:26     ` Mike Markowski
2020-03-19 21:31       ` Dave Horsfall
2020-03-20 11:48         ` paul
2020-03-20 15:40           ` Grant Taylor via TUHS
2020-03-20 16:40             ` Jon Steinhart
2020-03-20 17:23               ` Grant Taylor via TUHS
2020-03-20 18:43               ` Rich Morin [this message]
2020-03-19 20:01   ` Tomasz Rola
2020-03-19 20:57 Nelson H. F. Beebe
2020-03-19 21:18 ` Tomasz Rola
2020-03-20  7:14 ` arnold
2020-03-20  7:49   ` Thomas Paulsen
2020-03-20  8:18     ` arnold
2020-03-20 14:03 Noel Chiappa
2020-03-20 14:08 ` Richard Salz
2020-03-20 14:52   ` Larry McVoy
2020-03-20 14:58     ` Dagobert Michelsen
2020-03-20 15:05       ` Richard Salz
2020-03-20 22:09       ` Mike Markowski
2020-03-20 15:03     ` Gregg Levine
2020-03-20 15:05       ` Chet Ramey
2020-03-20 22:06     ` Dave Horsfall
2020-03-21  4:59     ` Wesley Parish
2020-03-20 21:57   ` Dave Horsfall
2020-03-22 18:05     ` Tony Finch
2020-03-20 15:07 ` Nemo
2020-03-20 19:03   ` Adam Thornton
2020-03-20 16:07 ` Grant Taylor via TUHS
2020-09-13 15:44   ` Juergen Nickelsen
2020-03-21  1:12 Noel Chiappa

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=FE7F5013-ABB8-40EB-B8FB-01C974DCCACA@cfcl.com \
    --to=rdm@cfcl.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).