Bit bucket

From Wikipedia, the free encyclopedia
Revision as of 02:35, 23 December 2024 by imported>Necessarycoot72 (Updated image description)
(diff) ← Previous revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Template:Short description Script error: No such module "Distinguish". Template:Use dmy dates

File:Univac bit bucket.JPG
The chad receiver (or "bit bucket")[1] from a UNIVAC key punch

In computing jargon, the bit bucket (or byte bucket[2][3]) is where lost computerized data has gone, by any means; any data which does not end up where it is supposed to, being lost in transmission, a computer crash, or the like, is said to have gone to the bit bucket – that mysterious place on a computer where lost data goes, as in:

Template:Quote

Template:Quote

History

Originally, the bit bucket was the container on teletype machines or IBM key punch machines into which chad from the paper tape punch or card punch was deposited;[1] the formal name is "chad box" or (at IBM) "chip box". The term was then generalized into any place where useless bits go, a useful computing concept known as the null device. The term bit bucket is also used in discussions of bit shift operations.[4]

The bit bucket is related to the first in never out buffer and write-only memory, in a joke datasheet issued by Signetics in 1972.[5]

In a 1988 April Fool's article in Compute! magazine, Atari BASIC author Bill Wilkinson presented a POKE that implemented what he called a "WORN" (Write Once, Read Never) device, "a close relative of the WORM".[6]

In programming languages the term is used to denote a bitstream which does not consume any computer resources, such as CPU or memory, by discarding any data "written" to it. In .NET Framework-based languages, it is the System.IO.Stream.Null.[7]

See also

References

Template:Reflist

External links

Template:Sister project

  1. a b Cite error: Invalid <ref> tag; no text was provided for refs named Cutler_1964
  2. Cite error: Invalid <ref> tag; no text was provided for refs named Intel_1978_MSC86-OI
  3. Cite error: Invalid <ref> tag; no text was provided for refs named DRI_1983_CPM86-PG
  4. Cite error: Invalid <ref> tag; no text was provided for refs named OBrien_2010
  5. Cite error: Invalid <ref> tag; no text was provided for refs named Signetics_1972
  6. Cite error: Invalid <ref> tag; no text was provided for refs named Wilkinson_1988
  7. Cite error: Invalid <ref> tag; no text was provided for refs named Java2s