Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] [TUHS] History of m6?
Date: Wed, 13 Nov 2019 09:17:09 -0500	[thread overview]
Message-ID: <CAC20D2OU6f8nbaD95pzoW=atX27LJfvWFZhmjVsjrtag5zYjnQ@mail.gmail.com> (raw)
In-Reply-To: <08b6c7ce02adabe45f54621c3cbe9863@firemail.de>

Moving to a COFF

On Wed, Nov 13, 2019 at 4:16 AM Thomas Paulsen <thomas.paulsen at firemail.de>
wrote:

> 'T'was before my time, but the legend has it that the original BLISS-10 bootstrap
> compiler was a set of TECO macros that Chuck Geschke (Adobe's
> founder) wrote.'
> Really? TECO = Tape Editor and Corrector

TECO started as that for PDP-1 or maybe TX-1 (at MIT I believe).  But over
time, TECO became the primary text editor on the PDP-10's for many, many
people in the ARPA community.   I learned it as my second, PDP-10 text
editor (I learned a line editor, who's name I forget, that was similar to
the IBM's editor when I got my first PDP-10 account, but quickly moved to
TECO).   FWIW: The original EMACS was a set of TECO macros.  The historical
truth is that besides being the primary text editor, it was so rich in
function that TECO became for the PDP-10 what Jon Bentley describes as a
'little language' and was used for all sorts of small hacks.

The later Unix world created other tools, be it sed, later awk, and the
like.  But for the PDP-10 world, TECO very much that low level engine that
a lot of people used.

When BLISS was written, CMU did not have UNIX (and thus nor any of the UNIX
tools - as I had a small hand in making UNIX happen @ CMU in the early
1970s).  But when I arrived, the two PDP-10's (CMU-A and CMU-B) reigned
supreme as primary CS (and EE) systems, along with the CMU hacked version
of IBM's TSS running on the 360 for everyone else (and where I got my first
real programming job), plus CMU's own TSS/8 on couple of PDP-8s that were
scattered about.

FWIW: Chuck used the PDP-10's for his work as a grad student.  He also is
famous for being the first PhD to produce his thesis on a 'laser printer',
the CMU XGP (it was not a laser as today, it was modified FAX machine made
by Xerox).   The fun story is that CMU's administration would not accept
his thesis originally because the library wanted the 'originals' to put in
the archives.   It took 6-9 months for his thesis advisor (Bill Wulf) to
convince the library, that they had the originals.

Anyway, the use of TECO in such a manner was very much the way things were
done in those days, so the legend is very much possible.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20191113/9cfeab51/attachment.html>


       reply	other threads:[~2019-11-13 14:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201911112110.xABLAQfW004396@skeeve.com>
     [not found] ` <d155d03e5177486fb1702add77ed540bebc3515a@webmail.yaccman.com>
     [not found]   ` <CAC20D2PjXNN-LTvpfTRvAzoCo-wMbf9tLuNTzs63_7VEGJUD0w@mail.gmail.com>
     [not found]     ` <08b6c7ce02adabe45f54621c3cbe9863@firemail.de>
2019-11-13 14:17       ` clemc [this message]
2019-11-13 15:06         ` lars
2019-11-13 15:32           ` clemc
2019-11-13 22:31           ` [COFF] TECO (was: History of m6?) grog
2019-11-14  5:47             ` [COFF] TECO lars
2019-11-14 14:40               ` clemc
2019-11-15  0:01                 ` imp
2019-11-14 15:00             ` [COFF] TECO (was: History of m6?) clemc
     [not found]       ` <7w8sokklwp.fsf@junk.nocrew.org>
     [not found]         ` <f68fbf8dad43ac5e8314c094c1ece06f@firemail.de>
2019-11-14 10:53           ` [COFF] [TUHS] History of m6? lars
2019-11-14 16:35             ` paul.winalski

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='CAC20D2OU6f8nbaD95pzoW=atX27LJfvWFZhmjVsjrtag5zYjnQ@mail.gmail.com' \
    --to=coff@minnie.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).