The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Dan Halbert <halbert@halwitz.org>
To: tuhs@tuhs.org
Subject: [TUHS] Re: origin of null-terminated strings
Date: Fri, 16 Dec 2022 16:20:59 -0500	[thread overview]
Message-ID: <bd4689fc-3823-5ad9-ed0c-9c5ecf6e5454@halwitz.org> (raw)
In-Reply-To: <CANCZdfpXG2Wdzhwd5uqhetHM4xX6kNk41V3ULBkoEEuzYf7esw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1370 bytes --]

On 12/16/22 16:02, Warner Losh wrote:
> On Fri, Dec 16, 2022, 1:12 PM Dave Horsfall <dave@horsfall.org> wrote:
>
>     On Fri, 16 Dec 2022, Dr Iain Maoileoin wrote:
>
>     > I remember running into a .asciz directive n the 70s
>     “somewhere”. It was
>     > an assembler directive in one of the RT11 systems??? or perhaps
>     the unix
>     > bootstrap and/or “.s” files - when I get some time I will go
>     read some
>     > old code/manuals.
>
>     MACRO-11 on RSX-11D seems to ring a bell...
>
>
> I first encountered it on RSTS/E 6C in the MACRO-11 it had... But the 
> v6 macro assembler from DEC via Harvard that eventually wound up in 
> 2BSD is older and dates to 1977 or so.
>
> Warner

The PDP-10 manual I spoke of is from 1971, and there were older 
editions. For the PDP-7, this manual from 1965, 
http://www.bitsavers.org/pdf/dec/pdp7/PDP-7_AsmMan.pdf, printed pages 
38-40, does not mention "ASCIZ" specifically, but talks about assembler 
directives "TELETYPE" and "ANALEX" that add a "termination code" of 00 
octal, for characters.

DEC also used SIXBIT, a truncated ASCII code that had printing 
characters but no control characters, so no newline, etc. In that 
scheme, 00 octal was SPACE. Table here: 
https://en.wikipedia.org/wiki/Six-bit_character_code#Examples_of_six-bit_ASCII_variants.

Dan H

[-- Attachment #2: Type: text/html, Size: 2677 bytes --]

  parent reply	other threads:[~2022-12-16 21:21 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-16  3:02 [TUHS] " Douglas McIlroy
2022-12-16  3:14 ` [TUHS] " Ken Thompson
2022-12-16  9:13   ` Dr Iain Maoileoin
2022-12-16 13:42     ` Dan Halbert
2022-12-16 16:10       ` Dan Cross
2022-12-16 16:22         ` Tom Lyon
2022-12-16 16:29         ` Jon Steinhart
2022-12-16 20:12     ` Dave Horsfall
2022-12-16 21:02       ` Warner Losh
2022-12-16 21:13         ` Clem Cole
2022-12-16 21:49           ` Clem Cole
2022-12-17  0:26             ` Phil Budne
2022-12-16 21:18         ` Luther Johnson
2022-12-16 21:20         ` Dan Halbert [this message]
2022-12-16  3:17 ` Steve Nickolas
2022-12-16 17:24 ` John P. Linderman
     [not found] ` <6009124d-750d-365e-a424-ec7bb25922b9@gmail.com>
2022-12-16 22:30   ` [TUHS] Terms for string, and similar character constructs (was: origin of null-terminated strings) Alejandro Colomar
2022-12-16 22:51     ` [TUHS] " Dave Horsfall
2022-12-16 22:26 [TUHS] Re: origin of null-terminated strings Douglas McIlroy
2022-12-17  2:03 ` James Frew
2022-12-17  3:42 ` steve jenkin
2022-12-17 17:11 ` Clem Cole
2022-12-17 18:15   ` Tom Lyon
2022-12-17 18:43     ` Clem Cole
2022-12-17 18:46       ` Clem Cole
2022-12-17 19:26     ` Tom Perrine
2022-12-19  4:26     ` Adam Thornton
2022-12-16 23:11 Noel Chiappa

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=bd4689fc-3823-5ad9-ed0c-9c5ecf6e5454@halwitz.org \
    --to=halbert@halwitz.org \
    --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).