From: Charles Anthony <charles.unix.pro@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] head/sed/tail (was The Unix shell: a 50-year view)
Date: Fri, 16 Jul 2021 17:34:17 -0700 [thread overview]
Message-ID: <CANV78LQsCrPDGW6-BQd1Q=ViDEbDdDBK9Frydso8tc6YE5r8Xg@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2McU80+T+OzTNTQcFZ+_siXr9S-5SXtMd_QPcskhX6v9w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
On Fri, Jul 16, 2021 at 7:20 AM Clem Cole <clemc@ccc.com> wrote:
>
>
> On Fri, Jul 16, 2021 at 4:05 AM Lars Brinkhoff <lars@nocrew.org> wrote:
>
>> Clem Cole wrote:
>> > The 'second' C compiler was a PDP-10 and Honeywell (36-bit) target
>> > Alan Synder did for his MIT Thesis. It was originally targeted to ITS
>> > for the PDP-10, but it ran on Tops-20 also. My >>memory<< is he used
>> > a 7-bit Character, ala SAIL, with 5 chars stored in a word with a bit
>> > leftover.
>>
>> On ITS it only ever stored characters as full 36-bit words! So sizeof
>> char == 1 == sizeof int. This is allowed per the C standard. (Maybe it
>> was updated somewhere else, I dunno.)
>>
>
> Ah - that makes sense. I never programmed the Honeywell in anything but
> Dartmouth BASIC (mostly) and any early FORTRAN (very little) and the whole
> idea of storage size was somewhat oblivious to me at the point as I was a
> youngster when I did that. Any idea did the Honeywell treat chars as
> 36-bit entities also? Steve, maybe you remember?
>
>
The Honeywell 6000 machines ran GCOS; the system standard was six six-bit
characters per word.
The Honeywell 6100 machines ran Multics; the system standard was four
nine-bit characters per word.
For Multics C, sizeof (*) != sizeof (int) and NULL != 0, so a lot of
"portable" C code wasn't.
-- Charles
[-- Attachment #2: Type: text/html, Size: 2291 bytes --]
next prev parent reply other threads:[~2021-07-17 0:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 19:01 Norman Wilson
2021-07-15 19:27 ` Clem Cole
2021-07-15 19:28 ` Clem Cole
2021-07-15 19:34 ` Warner Losh
2021-07-16 7:38 ` arnold
2021-07-16 16:09 ` Warner Losh
2021-07-16 8:05 ` Lars Brinkhoff
2021-07-16 14:19 ` Clem Cole
2021-07-17 0:34 ` Charles Anthony [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-07-18 20:07 Douglas McIlroy
[not found] <CAKH6PiW58PDPb5HRi12aKE+mT+O8AjETr9R51Db6U3KcEp_KkA@mail.gmail.com>
2021-07-16 14:17 ` Nelson H. F. Beebe
2021-07-16 16:13 ` Theodore Y. Ts'o
2021-07-16 12:09 Douglas McIlroy
2021-07-16 14:32 ` Bakul Shah
2021-07-15 22:26 Nelson H. F. Beebe
2021-07-15 23:18 ` Jim Davis
2021-07-16 0:02 ` John Floren
2021-07-16 1:02 ` Nelson H. F. Beebe
2021-07-16 8:27 ` Lars Brinkhoff
2021-07-16 15:28 ` John Floren
2021-07-16 0:02 ` Clem Cole
2021-07-16 0:25 ` Nelson H. F. Beebe
2021-07-16 8:50 ` Lars Brinkhoff
2021-07-15 22:00 Douglas McIlroy
2021-07-15 22:12 ` John Cowan
2021-07-15 21:26 Paul Ruizendaal
2021-07-15 16:54 Nelson H. F. Beebe
2021-07-15 15:44 Norman Wilson
2021-07-15 2:38 Douglas McIlroy
2021-07-15 4:19 ` arnold
2021-07-15 4:25 ` Adam Thornton
2021-07-15 7:20 ` Thomas Paulsen
2021-07-15 14:28 ` Theodore Y. Ts'o
2021-07-15 22:29 ` Bakul Shah
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='CANV78LQsCrPDGW6-BQd1Q=ViDEbDdDBK9Frydso8tc6YE5r8Xg@mail.gmail.com' \
--to=charles.unix.pro@gmail.com \
--cc=clemc@ccc.com \
--cc=tuhs@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).