From: Clem Cole <clemc@ccc.com>
To: tuhs@tkr.bondplaza.com
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Happy birthday, John Backus!
Date: Tue, 4 Dec 2018 11:53:29 -0500 [thread overview]
Message-ID: <CAC20D2PsA=_Yf-hZRM6wCJL7H3Y9o6cSE02s5oPz_VHfqRYxRA@mail.gmail.com> (raw)
In-Reply-To: <2DBF1622-0489-4F39-88A5-BCE130732041@tkr.bondplaza.com>
[-- Attachment #1: Type: text/plain, Size: 1033 bytes --]
On Tue, Dec 4, 2018 at 11:34 AM Tim Rylance <tuhs@tkr.bondplaza.com> wrote:
> The Fortran H compiler was mostly written in Fortran: 27,415 lines of
> Fortran and 16,721 lines of assembler according to slide 12 of [1].
>
Thanks for the pointer. As Doug points out, Burrough's ESPOL started
the transition in the early 60s, but it took awhile for it to be something
that was done 100% of time by everyone. The mid-70s is clearly the
transistion time - as you point out [2/3 self hosting, 1/3 assembler]. I
wonder what part was which?
Wirth wrote PL/360 to create Algol-W in the late 60s. But York/APL (and I
believe APL/360) which were the same timeframe, were assembler [I hacked on
the former on TSS in the early/mid 70s].
The first DEC compilers for the 360 bit and 12 bit lines were written in
assembler, but they switched to BLISS (and some other languages for
different front-ends) by the 70s for the newer generations of compilers.
Paul can give that history as he was part of it.
Clem
ᐧ
[-- Attachment #2: Type: text/html, Size: 2855 bytes --]
next prev parent reply other threads:[~2018-12-04 16:54 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-04 14:43 Noel Chiappa
2018-12-04 14:53 ` Clem Cole
2018-12-04 16:24 ` Tim Rylance
2018-12-04 16:53 ` Clem Cole [this message]
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
2018-12-05 17:49 ` [TUHS] Happy birthday, John Backus! Paul Winalski
2018-12-04 15:18 ` Toby Thain
-- strict thread matches above, loose matches on Subject: below --
2018-12-02 22:17 Dave Horsfall
2018-12-02 22:34 ` Toby Thain
2018-12-03 1:32 ` Rob Pike
2018-12-03 4:11 ` Toby Thain
2018-12-03 4:27 ` Rob Pike
2018-12-03 13:10 ` John P. Linderman
2018-12-03 22:44 ` ron
2018-12-03 16:25 ` Clem Cole
2018-12-03 20:20 ` Paul Winalski
2018-12-03 20:37 ` Clem Cole
2018-12-03 20:46 ` Hellwig Geisse
2018-12-03 22:24 ` Paul Winalski
2018-12-03 23:00 ` Lawrence Stewart
2018-12-04 11:53 ` Tony Finch
2018-12-04 14:23 ` Clem Cole
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='CAC20D2PsA=_Yf-hZRM6wCJL7H3Y9o6cSE02s5oPz_VHfqRYxRA@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=tuhs@tkr.bondplaza.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).