From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] DEC filenames (was: Command-line options)
Date: Sat, 26 Mar 2016 17:03:06 -0400 [thread overview]
Message-ID: <20160326210306.GC12921@mercury.ccil.org> (raw)
In-Reply-To: <56F6F150.8020906@update.uu.se>
Johnny Billquist scripsit:
> SIXBIT dominated here for a long time. We see it both in the PDP-8,
> but also the PDP-6 and its follow ons. RAD50 was the natural
> extension of SIXBIT on a machine that did not have a word size that
> was a multiple of 6.
Well, for identifiers, yes. But SIXBIT was quite general, especially
if you repurposed two of the characters to mean "end of string" and
"CR+LF". The "@" was a popular choice for the former, perhaps because
its encoding is 00; IIRC, "_" was popular for the latter.
--
John Cowan http://www.ccil.org/~cowan cowan at ccil.org
Long-short-short, long-short-short / Dactyls in dimeter,
Verse form with choriambs / (Masculine rhyme):
One sentence (two stanzas) / Hexasyllabically
Challenges poets who / Don't have the time. --robison who's at texas dot net
next prev parent reply other threads:[~2016-03-26 21:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.163.1459021419.15972.tuhs@minnie.tuhs.org>
2016-03-26 20:30 ` Johnny Billquist
2016-03-26 21:03 ` John Cowan [this message]
2016-03-26 21:29 ` [TUHS] DEC filenames Johnny Billquist
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=20160326210306.GC12921@mercury.ccil.org \
--to=cowan@mercury.ccil.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).