From: Paul McJones <paul@mcjones.org>
To: Greg 'groggy' Lehey <grog@lemis.com>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Tandem NSK implementation language (was: Happy birthday, John Backus!)
Date: Tue, 4 Dec 2018 20:48:24 -0800 [thread overview]
Message-ID: <385DF3A2-447D-4CD4-AC5C-9F541070C28B@mcjones.org> (raw)
In-Reply-To: <mailman.1.1543975201.8252.tuhs@minnie.tuhs.org>
> On Dec 4, 2018, Greg 'groggy' Lehey <grog@lemis.com> wrote:
>
> The original Tandem OS (called Guardian at the time) was written in Tandem's TAL (Transaction Application Language, amongst other productions), a vague evolution of HP's SPL that looked more like Algol, starting in about 1974. That is also the earliest I know of an operating system being implemented entirely in a high level language.
Most likely the earliest operating system written in a high-level language was the one for the Burroughs B5000 (early 1960s), written in a dialect of Algol 60. Others: Multics, written in PL/1 (starting in mid 1960s), the operating system for the Berkeley Computer Corporation’s BCC-500, written in BCC SPL (system programming language) (late 1960s), OS6 by Stoy and Strachey, written in BCPL (early 1970s), Xerox Alto OS, written in BCPL (about 1974).
next parent reply other threads:[~2018-12-05 5:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1.1543975201.8252.tuhs@minnie.tuhs.org>
2018-12-05 4:48 ` Paul McJones [this message]
2018-12-05 8:16 ` Dr Iain Maoileoin
2018-12-05 14:29 ` Clem Cole
2018-12-04 14:43 [TUHS] Happy birthday, John Backus! Noel Chiappa
2018-12-04 14:53 ` Clem Cole
2018-12-04 16:24 ` Tim Rylance
2018-12-04 16:53 ` Clem Cole
2018-12-04 17:46 ` Paul Winalski
2018-12-04 20:59 ` Paul Winalski
2018-12-04 22:49 ` [TUHS] Tandem NSK implementation language (was: Happy birthday, John Backus!) Greg 'groggy' Lehey
2018-12-05 0:08 ` 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=385DF3A2-447D-4CD4-AC5C-9F541070C28B@mcjones.org \
--to=paul@mcjones.org \
--cc=grog@lemis.com \
--cc=tuhs@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).