The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Halbert <halbert@halwitz.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Does anybody know the etymology of the term "word" as in collection of bits?
Date: Thu, 8 Sep 2022 13:28:13 -0400	[thread overview]
Message-ID: <61096d8f-ce80-2ba5-ffdf-8ad5f802ab02@halwitz.org> (raw)
In-Reply-To: <202209081651.288Gp6ag355864@darkstar.fourwinds.com>

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

On 9/8/22 12:51, Jon Steinhart wrote:
> One of those questions for which there is no search engine incantation.
>
> Jon

The famous 1946 paper, "Preliminary discussion of the logical design of 
an electronic computing device",  by Arthur Burks,  Herman H. Goldstine, 
John von Neumann, contains this sentence. I have this paper in Computer 
Structures: Readings and Examples, by Bell and Newell, but it's also 
online in many forms

**

    *

    4. The memory organ

    * 4.1. Ideally one would desire an indefinitely large memory
    capacity such that any particular aggregate of 40 binary digits, or
    /word /(cf. 2.3), would be immediately available-i.e. in a time
    which is somewhat or considerably shorter than the operation time of
    a fast electronic multiplier.

I also looked in the Oxford English Dictionary for etymology. It has:

    *d.* /Computing/. A consecutive string of bits (now typically 16,
    32, or 64, but formerly fewer) that can be transferred and stored as
    a unit./machine word/: see /machine word/ n. at machine n. Compounds
    2 <https://www-oed-com.ezproxy.bpl.org/view/Entry/111850#eid38480019>.

    1946 H. H. Goldstine & J. Von Neumann in J. von Neumann /Coll. Wks./
    (1963) V. 28   In ‘writing’ a word into the memory, it is similarly
    not only the time effectively consumed in ‘writing’ which matters,
    but also the time needed to ‘find’ the specified location in the memory.

    [plus newer citations]

Dan H



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

  parent reply	other threads:[~2022-09-08 17:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-08 16:51 [TUHS] " Jon Steinhart
2022-09-08 16:56 ` [TUHS] " Andrew Hume
2022-09-08 17:28 ` Dan Halbert [this message]
2022-09-09  0:00   ` Greg 'groggy' Lehey
2022-09-09 15:49     ` Paul Winalski
2022-09-09 18:44       ` Bakul Shah
2022-09-08 18:20 Noel Chiappa
2022-09-08 19:28 ` Jim Capp
2022-09-08 21:16 Noel Chiappa
2022-09-08 21:24 ` Dan Halbert
2022-09-09  1:33 Douglas McIlroy
2022-09-09  2:12 ` Larry McVoy
2022-09-13 14:23   ` John Foust via TUHS
2022-09-09  2:45 ` George Michaelson
2022-09-16  5:55 ` Marc Donner
2022-09-09 17:26 Douglas McIlroy
2022-09-09 18:46 Norman Wilson
2022-09-10  1:35 ` Paul Winalski
2022-09-09 19:39 Nelson H. F. Beebe
2022-09-09 20:27 ` Bakul Shah
2022-09-09 21:12   ` Henry Bent
2022-09-09 21:44   ` Dave Horsfall
2022-09-11 13:30 Douglas McIlroy
2022-09-11 15:08 ` John Cowan
2022-09-11 15:30 ` Bakul Shah
2022-09-11 15:45   ` Paul Winalski
2022-09-11 16:20     ` Steve Nickolas

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=61096d8f-ce80-2ba5-ffdf-8ad5f802ab02@halwitz.org \
    --to=halbert@halwitz.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).