From: bakul@bitblocks.com (Bakul Shah)
Subject: [TUHS] FORTRAN
Date: Tue, 20 Mar 2018 16:00:32 -0700 [thread overview]
Message-ID: <8E0EC81A-D1EB-4070-AAD5-FBFF3139975E@bitblocks.com> (raw)
In-Reply-To: <CAC20D2NNxp-3Qpw1=_3+3ZT6pk-b_answ88-KLZCw7j3gf7WOw@mail.gmail.com>
On Mar 20, 2018, at 2:36 PM, Clem Cole <clemc at ccc.com> wrote:
>
> Paul can correct me, but I don't think DEC even developed a Pascal for TOPS originally - IIRC the one I used came from the universities. I think the first Pascal sold was targeted for the VAX. Also, RT11 and RSX were 'laboratory' systems and those systems were dominated by Fortran back in the day - so DEC marketing thought in those terms.
True re TOPS-10.
The TOP-10 Pascal compiler was ported from the one for
CDC-6000 (authors: Urs Amman, Kesav Nori and may be others).
The CDC version was what was described in the Pascal User
Manual and Report by Jensen and Wirth. IIRC, someone at Purdue
was maintaining it. I knew it well as I had added formatted IO
for scalars, sets & a few more things that I forget now + I
was studying it with an aim to write my own compiler. I
believe this was the port:
https://www.researchgate.net/publication/220846309_A_pascal_compiler_bootstrapped_on_a_DEC-System_10
[Even the portable "P4" Pascal compiler must've been derived
from the same original code as I recognize its code shape and
random stuff like variable names etc. p4 sources are online
but I don't see the tops-10 ones]
next prev parent reply other threads:[~2018-03-20 23:00 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 21:52 [TUHS] RIP John Backus Dave Horsfall
2018-03-16 23:42 ` Dan Stromberg
2018-03-17 0:08 ` Dave Horsfall
2018-03-17 0:26 ` Arthur Krewat
2018-03-17 0:36 ` Dave Horsfall
2018-03-17 1:40 ` Charles H Sauer
2018-03-17 1:57 ` Nemo
2018-03-17 7:20 ` Bakul Shah
2018-03-17 13:43 ` Clem Cole
2018-03-17 17:06 ` Steve Simon
2018-03-17 19:15 ` Pierre DAVID
2018-03-17 19:41 ` Charles Anthony
2018-03-18 11:02 ` Steve Simon
2018-03-17 19:22 ` Tim Bradshaw
2018-03-17 19:28 ` Mike Markowski
2018-03-18 18:51 ` Paul Winalski
2018-03-18 21:07 ` Clem Cole
2018-03-19 14:50 ` Dan Cross
2018-03-19 15:43 ` Clem Cole
2018-03-19 15:46 ` Clem Cole
2018-03-19 17:39 ` Paul Winalski
2018-03-19 17:43 ` George Michaelson
2018-03-19 18:16 ` Steve Nickolas
2018-03-19 17:48 ` Clem Cole
2018-03-19 17:59 ` Jon Forrest
2018-03-19 18:40 ` Tom Ivar Helbekkmo
2018-03-19 19:40 ` Arthur Krewat
2018-03-19 15:55 ` Clem Cole
2018-03-19 16:58 ` [TUHS] FORTRAN Steve Johnson
2018-03-19 17:32 ` Jon Forrest
2018-03-20 17:42 ` Paul Winalski
2018-03-20 17:47 ` George Michaelson
2018-03-19 18:47 ` Larry McVoy
2018-03-20 18:15 ` Dan Cross
2018-03-20 19:55 ` Ron Natalie
2018-03-20 20:21 ` Paul Winalski
2018-03-20 20:27 ` Warner Losh
2018-03-21 8:10 ` Peter Jeremy
2018-03-21 20:56 ` Ron Natalie
2018-03-21 21:15 ` Dennis Boone
2018-03-20 21:36 ` Clem Cole
2018-03-20 21:59 ` Ron Natalie
2018-03-20 23:00 ` Bakul Shah [this message]
2018-03-21 13:48 ` Paul Winalski
2018-03-21 20:55 ` Ron Natalie
2018-03-18 21:26 ` [TUHS] RIP John Backus Tim Bradshaw
2018-03-19 0:26 ` Steve Johnson
2018-03-19 14:26 ` Warner Losh
2018-03-21 14:51 [TUHS] FORTRAN Noel Chiappa
2018-03-21 21:57 ` Charles Anthony
[not found] <mailman.48.1521640130.3788.tuhs@minnie.tuhs.org>
2018-03-21 22:58 ` 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=8E0EC81A-D1EB-4070-AAD5-FBFF3139975E@bitblocks.com \
--to=bakul@bitblocks.com \
/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).