From: clemc at ccc.com (Clem Cole)
Subject: [COFF] [TUHS] v7 K&R C
Date: Mon, 18 May 2020 12:30:33 -0400 [thread overview]
Message-ID: <CAC20D2Nxwxuuo=Z9YhzSrDonHd7KGdc-rSGpkSzgGbXi=75sNg@mail.gmail.com> (raw)
In-Reply-To: <CAEoi9W6jwA1_MGD11Sc837YMgDfGJWzAQFCyrbrx72a1PJ3ViA@mail.gmail.com>
On Mon, May 18, 2020 at 12:12 PM Dan Cross <crossd at gmail.com> wrote:
> 6x6-bit data would certainly hold BAUDOT data, and I thought the
> Univac/CDC machines supported a 6-bit character set?
>
BAUDOT is 5 bits. CDC used a 6-bit Display code - which there were a
number of different versions. It was a PITA when you programmed it. The
original Pascal compiler was a mess because of this.
> Does this live on in the Unisys 1100-series machines? I see some
> reference to FIELDATA online.
>
https://www.fourmilab.ch/documents/univac/fieldata.html
Yes, it was officially a 7-bit code, but the first 1/2 of the code was
non-printable. So the printable set was 6 bits.
> they're called 'char' because that was just the way things had always
> been.
>
Right
Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200518/e1f4943a/attachment.htm>
next prev parent reply other threads:[~2020-05-18 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200515213138.8E0F72D2D71E@macaroni.inf.ed.ac.uk>
[not found] ` <alpine.DEB.2.21.2005151752250.19733@sd-119843.dedibox.fr>
[not found] ` <077a01d62b08$e696bee0$b3c43ca0$@ronnatalie.com>
[not found] ` <20200515233427.31Vab%steffen@sdaoden.eu>
[not found] ` <5DB09C5A-F5DA-4375-AAA5-0711FC6FB1D9@ronnatalie.com>
[not found] ` <20200516232607.nLiIx%steffen@sdaoden.eu>
[not found] ` <CABH=_VSqRFD6aHiRRdpQc7fzLaAcBXR-OMRJW3LqnqAih-W8EQ@mail.gmail.com>
2020-05-18 16:11 ` crossd
2020-05-18 16:30 ` clemc [this message]
2020-05-18 21:18 ` ron
2020-05-19 4:00 ` [COFF] UNIVAC and other character sets (was: v7 K&R C) grog
[not found] <CAKzdPgyYUCPDn3KjRgx6Aw_=AD8O2Mdk0WkmPZCH9oN+XkPebg@mail.gmail.com>
[not found] ` <20200511005745.GL17035@mcvoy.com>
[not found] ` <m1jYCHm-0036tPC@more.local>
[not found] ` <CABH=_VRucqOpJvZVRqhz6Bv-kVe6P-7Hk3SFDuO0XyKZ_=oCBg@mail.gmail.com>
[not found] ` <CAC20D2NTRE4cK5jewe-Yuo1UVnH6pY2u-wSt8NiG-5hBkzvvzQ@mail.gmail.com>
[not found] ` <CABH=_VT9dU7kuJSa+iN6zdF7RMpS-hE92DsyeSuMkTmrYGL_9g@mail.gmail.com>
[not found] ` <357EFE54-BD94-4C10-8C43-C6735BF7D317@via.net>
[not found] ` <20200511202555.GU17035@mcvoy.com>
[not found] ` <CABH=_VS8XO8BQA=fMCGTf8u-ubXLKT1tzUJ5ntTXWkjeGk1sSA@mail.gmail.com>
[not found] ` <alpine.BSF.2.21.9999.2005140930270.18677@aneurin.horsfall.org>
[not found] ` <20200514173206.GJ20771@mcvoy.com>
2020-05-14 17:37 ` [COFF] [TUHS] v7 K&R C athornton
2020-05-14 17:38 ` lm
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='CAC20D2Nxwxuuo=Z9YhzSrDonHd7KGdc-rSGpkSzgGbXi=75sNg@mail.gmail.com' \
--to=coff@minnie.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).