The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: crossd@gmail.com (Dan Cross)
Subject: [TUHS] RIP John Backus
Date: Mon, 19 Mar 2018 10:50:37 -0400	[thread overview]
Message-ID: <CAEoi9W6_JLMubF0yM4dH+ep6DTHCia9X666kSQGPCuOodUR2LQ@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2POLKfgPefXSOECX3N5AKffxGKMjNJLi9pD-xWkX8Ffhg@mail.gmail.com>

On Sun, Mar 18, 2018 at 5:07 PM, Clem Cole <clemc at ccc.com> wrote:
>
> [...]
> I do remember, one of the big issues with UNIX being picked up into the EE
> department was the lack of a 'proper Fortran.'    As much as modern
> languages like C and Pascal were clearly the direction, a lot of professors
> had a lot of code in FORTRAN they wanted to run.
>
> So now I live in a world were the best FORTRAN compilers are UNIX based
> and I don't write with FORTRAN anymore.   I still have a ton of respect for
> those that do and even more for the wizards like Paul and co that have
> spent their careers creating compilers for FORTRAN that have spanned such
> changes in the underlying system hardware, as well as the language itself
> and keep those same user codes getting correct answers and using the
> hardware as well as can be.
>

And to bring this back around to Unix, here are a couple of random
questions....

First, in Dennis Ritchie's paper, "The Development of the C Language" (
https://www.bell-labs.com/usr/dmr/www/chist.html) he mentions the early
days of Unix, Ken taking Doug McIlroy's implementation of "TMG" on the
PDP-7 as a challenge and deciding to produce a "systems programming
language." The first effort was, apparently, "a rapidly scuttled attempt at
Fortran", followed by B.

I'm curious at the FORTRAN effort: what was that about, where did it come
from, and why was it abandoned?

Second, 7th Edition came with the "f77" command implementing
(unsurprisingly) Fortran 77. A paper by Stu Feldman and Peter Weinberger in
Volume 2 describes the compiler and includes this line: "This is believed
to be the first complete Fortran 77 system to be implemented." (
https://s3.amazonaws.com/plan9-bell-labs/7thEdMan/vol2/f77.txt)

Was that true? Notable in this paper is mention that the Fortran compiler
can drive the backend of either Ritchie's PDP-11 C compiler *or* Johnson's
portable C compiler. What was the local story? Did this see local use?

        - Dan C.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180319/5452fa3e/attachment.html>


  reply	other threads:[~2018-03-19 14:50 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 21:52 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 [this message]
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
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
     [not found] <mailman.17.1521243734.3788.tuhs@minnie.tuhs.org>
2018-03-17 14:47 ` Paul McJones
2018-03-17 15:54   ` Dave Horsfall
     [not found] <mailman.19.1521302091.3788.tuhs@minnie.tuhs.org>
2018-03-17 17:49 ` Paul McJones
2018-03-17 18:52   ` Arthur Krewat
2018-03-18  3:39     ` Greg 'groggy' Lehey
2018-03-18  7:35     ` Otto Moerbeek
     [not found] <mailman.21.1521314548.3788.tuhs@minnie.tuhs.org>
2018-03-17 20:01 ` Paul McJones
2018-03-17 20:14 ` Paul McJones
2018-03-17 22:27   ` Steve Johnson
2018-03-18 13:33 Noel Chiappa

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=CAEoi9W6_JLMubF0yM4dH+ep6DTHCia9X666kSQGPCuOodUR2LQ@mail.gmail.com \
    --to=crossd@gmail.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).