Talk:Bitwise IO: Difference between revisions

:4. Ooch, no, in mathematics numbers have neither bits nor digits. For that matter, in [http://en.wikipedia.org/wiki/Zermelo%E2%80%93Fraenkel_set_theory Zermelo–Fraenkel set theory] numbers are first introduced as sets {} (empty set is 0), {{}} (set with 0 inside is 1), {{{}}} (set with 1 inside is 2). No any bits in sight. Nor it means that numbers have first and last brackets! Digit, bit, LSB, MSB, exponent, bracket etc are entities of representations. There are countless ways to representation numbers. Representations themselves are not numbers. Representation R is in a mapping from some set S to N (the set of numbers): R:S->N. When S is the set of English words, then "two" is a representation of the number {{{}}}. When S is the set of binary numerals then 10₂ is a representation of the same number {{{}}}. Division between "physical" and what? is below my radar, because you could not define "physical" anyway. About files. A byte-oriented file has bytes, these bytes contain themselves. They don't contain bits, characters, images or Shakespear's plays in PDF format. They just do not. It is a ''media layer'' in [http://en.wikipedia.org/wiki/OSI_layer#Layer_2:_Data_Link_Layer OSI] terms. The content (meaning), e.g. bits, characters etc, lies above it in the application that deals with the file. Your '''application''' knows the meaning of bytes, as defined by the task, i.e. to keep sequences of bits in a '''certain''' way. Merry Christmas! --[[User:Dmitry-kazakov|Dmitry-kazakov]] 08:59, 22 December 2008 (UTC)