From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10f6aa,76b1fcc14e8dced X-Google-Attributes: gid10f6aa,public X-Google-Thread: 114917,76b1fcc14e8dced X-Google-Attributes: gid114917,public X-Google-Thread: 1014db,8b6c45fbebd7d3b7 X-Google-Attributes: gid1014db,public X-Google-Thread: 109fba,76b1fcc14e8dced X-Google-Attributes: gid109fba,public X-Google-Thread: 103376,c9c309a1859318a1 X-Google-Attributes: gid103376,public From: dewar@merv.cs.nyu.edu (Robert Dewar) Subject: Re: HELP ! need to insert value in array !! Date: 1997/07/09 Message-ID: #1/1 X-Deja-AN: 255839220 References: <33A9C27C.22F7@post4.tele.dk> <5oci49$97g@crl.crl.com> <1997Jul7.091353.28784@indyvax.iupui.edu> Organization: New York University Newsgroups: comp.lang.c,comp.lang.c++,comp.os.msdos.programmer,comp.lang.asm.x86,comp.lang.ada Date: 1997-07-09T00:00:00+00:00 List-Id: iMark said << Nope. Byte operations on the PDP10 architecture all go through a "byte pointer" object that can deal with any contiguous collection of 1 to 36 bits that doesn't cross a 36-bit word boundary. It's the OS that had a predisposition for five 7-bit ASCII bytes per word, in string operations. Serial I/O hardware had to deal with other realities, but most of it was slotted into PDP11 frontend processors so it sat behind translation software anyway. Interfacing 36-bit hardware with 16-bit hardware made for some interesting programming (and interesting hardware!), to say the least.>> So let's get back to the original thread here, what I said turns out to be exactly right. The normal format for strings on this machine was 5x7 with one bit lweft over, and there was hardware support for this format. (I did not say it was the only format supported, just that there was hardware support for this format and that it was naturally supported in the hardware) Now back to the original point, given that --- how would you map ANSI C, given the claims that have been made (actually I can't find real justification for these claims in the ANSI standeard, and neither can Ritchie)