Re: binary i/o files
- From: Terence <tbwright@xxxxxxxxx>
- Date: Thu, 19 Feb 2009 03:30:42 -0800 (PST)
Ron Shepard wrote:
In article
<fed58698-e244-4f9e-80d3-364449fc1733@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
Terence <tbwright@xxxxxxxxx> wrote:
So I have suggested on how to write the full ascii 256-character set
to unformatted sequential, unbridged BINARY stream files.
I just checked wikipedia, and ascii still has only 128 characters in it.
http://en.wikipedia.org/wiki/ASCII
I've been expecting it to be extended up to 256 for some time now, but
it hasn't happened yet.
$.02 -Ron Shepard
Say that to any programmer who writes in a language other that simple
english (and to be pedantic, English english still has the extremely
rare æ (AE) and accented vowels like é and ö).
Said programmer will reply "¿Oh? You mean AMERICAN ascii?".
All others also have to use the "other half" of the table at least;
some need special tables (like Polish and Cyrillic and Turkamen; and
many languages need double character tables. "And some write it
backwards which is absolutely frightening".
The meaning of words change; dictionaries are always in the past.
Even so, some few of the lower 31 positions of the ascii table are now
pretty useless; their job was to provide a signalling system for
external device the ascii frames might be passing through in
electrical or electronic form. Some like TAB still cause us pain.
I'm reminded of those little illuminated arms that popped up on the
sides of automobiles, to replace the usual whip signal (Yes, I helped
deliver milk on horseback).
.
- Follow-Ups:
- Re: binary i/o files
- From: Craig Powers
- Re: binary i/o files
- From: Glen Herrmannsfeldt
- Re: binary i/o files
- References:
- binary i/o files
- From: nikhilvasudeo
- Re: binary i/o files
- From: Terence
- Re: binary i/o files
- From: Richard Maine
- Re: binary i/o files
- From: Terence
- Re: binary i/o files
- From: Terence
- Re: binary i/o files
- From: Ron Shepard
- binary i/o files
- Prev by Date: Re: Fortran Standard question: COMMON, SAVE and EQUIVALENCE
- Next by Date: Re: Fortran Standard question: COMMON, SAVE and EQUIVALENCE
- Previous by thread: Re: binary i/o files
- Next by thread: Re: binary i/o files
- Index(es):
Relevant Pages
|