Names and primitives in SRFI 56 Hans Oesterholt-Dijkema (17 Sep 2004 21:53 UTC)
Re: Names and primitives in SRFI 56 Alex Shinn (18 Sep 2004 02:33 UTC)
Re: Names and primitives in SRFI 56 Hans Oesterholt-Dijkema (18 Sep 2004 09:53 UTC)
Re: Names and primitives in SRFI 56 bear (18 Sep 2004 19:46 UTC)
Re: Names and primitives in SRFI 56 Bradd W. Szonye (19 Sep 2004 18:08 UTC)
Re: Names and primitives in SRFI 56 bear (19 Sep 2004 19:28 UTC)
Re: Names and primitives in SRFI 56 Dave Mason (28 Sep 2004 11:36 UTC)
Re: Names and primitives in SRFI 56 Alex Shinn (28 Sep 2004 15:11 UTC)
Re: Names and primitives in SRFI 56 bear (18 Sep 2004 02:58 UTC)

Re: Names and primitives in SRFI 56 Bradd W. Szonye 19 Sep 2004 18:08 UTC

bear wrote:
> Character strings are not binary.  They are characters. Binary is data
> without interpretation.  Characters are an interpretation of binary
> data.  These are different ideas.

More generally, I/O models differ in at least three ways:

1. Interpretation of individual units (e.g., characters, bytes)
2. Handling of variable-length units (e.g., CR+LF, combining characters)
3. Structure of I/O (e.g., stream, record, binary objects)

Many languages simply follow the assumptions of the operating system for
which they were originally designed. For example, the original C
language assumed that bytes and characters were synonymous, that there
are no variable-length units, and that all I/O is stream-oriented. The
ANSI C standard expanded the model to handle variable-length units, but
it still assumes character/byte equivalence and stream sequencing. Newer
languages in the C family have adopted the ANSI C assumptions, as do
many higher-level languages that use C for the underlying
implementation. In contrast, languages like COBOL make radically
different assumptions. They assume record-oriented files to support the
operating systems they were designed for.
--
Bradd W. Szonye
http://www.szonye.com/bradd