The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Phil Budne <phil@ultimate.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: origin of null-terminated strings
Date: Fri, 16 Dec 2022 19:26:50 -0500	[thread overview]
Message-ID: <202212170026.2BH0QoH7060198@ultimate.com> (raw)
In-Reply-To: <CAC20D2OBc71sa+7sUu_SsF3K4opF2wXaYGb_tn_1c4j7GPqUDA@mail.gmail.com>

> From: Bob Supnik
> Tim can comment on the PDP10.

MACRO10 (the DEC PDP-10 assembler) had the ASCIZ directive,

I don't see it in the May 1964 MACRO6 (PDP-6 assembler) document at:

http://bitsavers.trailing-edge.com/pdf/dec/pdp6/F-64MAS_MACRO6_Assembly_Program_May64.pdf

Nor the February 1965 version:
http://bitsavers.trailing-edge.com/pdf/dec/pdp6/DEC-6-0-TP-MAC-LM-FP-ACT01_MACRO-6_Assembly_Language_Feb65.pdf

But it does appear in the May 1965 MACRO-6 manual:

http://bitsavers.trailing-edge.com/pdf/dec/pdp6/DEC-6-0-TP-MAC-LM-FP_ACT02_MACRO-6_Assembly_Language_May65.pdf

Which has the fullly trifuricated character packings:

ASCII/ASCIZ:	7 bit bytes, with the low order bit left over
		(set at the start of lines in files to indicate a Line
		Sequence Number metadata for line number based editors)
SIXBIT		"6-bit ASCII" -- ASCII characters 040 thru 0137
		stored as 00 thru 077 in six six bit bytes
RADIX50		6 characters from a 40 (050) character character set
		(plus four flag bits) used to store symbol tables
		https://en.wikipedia.org/wiki/DEC_RADIX_50#36-bit_systems

And ASCIZ is used in listings of the PDP-6 "T.S. Executive" version
1.4 dated 8-18-65:

http://bitsavers.trailing-edge.com/pdf/dec/pdp6/tsExec1.4/COMCON.pdf

COMCON is "COMmand CONtrol" -- the top level command interpreter built
into the monitor (the file name was retained into the later days of
TOPS-10), and messages output to the user use ASCIZ directives.

And to tie the thread back (closer) to the list subject, the "sub
title" headers in the above assembler listing file are "T. HASTINGS
8-2-65" (who I believe is Tom Hastings), which also appears in many
other files, including the job scheduler:

http://bitsavers.trailing-edge.com/pdf/dec/pdp6/tsExec1.4/CLKCSS.pdf

*AND* T. Hastings also appears as an author of the CTSS scheduler:

https://softwarehistory.csse.rose-hulman.edu/index.php/ctss-scheduler/
(in the "Full Code" section):

          :R******TIME SHARING SCHEDULING ALGORITHM***********
          :R    T. Hastings and R. Daley
          :R    Minor Modifications by G. Schroeder when NEW
          :R    I/O Package Installed....Summer, 1965

  reply	other threads:[~2022-12-17  0:27 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 [this message]
2022-12-16 21:18         ` Luther Johnson
2022-12-16 21:20         ` Dan Halbert
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=202212170026.2BH0QoH7060198@ultimate.com \
    --to=phil@ultimate.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).