From: Greg 'groggy' Lehey <grog@lemis.com>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] IBM 7030 byte size (was: v7 K&R C)
Date: Tue, 19 May 2020 13:24:09 +1000 [thread overview]
Message-ID: <20200519032409.GJ1670@eureka.lemis.com> (raw)
In-Reply-To: <202005181358.04IDwQ25114938@tahoe.cs.Dartmouth.EDU>
[-- Attachment #1: Type: text/plain, Size: 1426 bytes --]
On Monday, 18 May 2020 at 9:58:26 -0400, Doug McIlroy wrote:
>> [A]lthough these days "byte" is synonymous with "8 bits", historically it
>> meant "the number of bits needed to store a single character".
>
> It depends upon what you mean by "historically". Originally "byte"
> was coined to refer to 8 bit addressable units on the IBM 7030
> "Stretch" computer.
It seems that even then it was of variable size. From G.R. Trimble,
"STRETCH," Computer Usage Communique, 1963,
(http://archive.computerhistory.org/resources/text/Computer_Usage_Company/cuc.communique_vol2no3.1963.102651922.pdf):
the words can be composed of "bytes" with from one to eight bits in
a byte.
There's more at https://people.cs.clemson.edu/~mark/stretch.html.
> The term was perpetuated for the 360 family of computers. Only
> later did people begin to attribute the meaning to non-addressable
> 6- or 9-bit units on 36- and 18-bit machines.
>
> Viewed over history, the latter usage was transient and colloquial
Transient maybe, but UNIVAC used the term in its documentation of the
1100 series. The 1106/1108/1110 could access (but not directly
address) 6, 9 and 12 bit "bytes".
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
prev parent reply other threads:[~2020-05-19 3:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 13:58 [TUHS] v7 K&R C Doug McIlroy
2020-05-19 3:24 ` Greg 'groggy' Lehey [this message]
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=20200519032409.GJ1670@eureka.lemis.com \
--to=grog@lemis.com \
--cc=doug@cs.dartmouth.edu \
--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).