From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] RIP John Backus
Date: Mon, 19 Mar 2018 11:46:54 -0400 [thread overview]
Message-ID: <CAC20D2Mtgr1Sbsbe7jxSL+r6FJ2cC3n+z1UtczmdH_kce-g64g@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PDOdvqv4-dGcNr7KTujE-aH7kAsUz+tspXZDhWPAix4w@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2758 bytes --]
arrgh -- dyslexia -- VT-100's are NOT full ansi [they use the ANSI
sequences, but do not implement all of the features/behaviors in the
spec]. VMS Fortran started the same way, although it did conform in time
because it had to pass the Fortran validation tests.
ᐧ
On Mon, Mar 19, 2018 at 11:43 AM, Clem Cole <clemc at ccc.com> wrote:
>
>
> On Mon, Mar 19, 2018 at 10:50 AM, Dan Cross <crossd at gmail.com> wrote:
>
>> I'm curious at the FORTRAN effort: what was that about, where did it come
>> from, and why was it abandoned?
>>
> I'll let Ken, Steve or Doug answer definitively that but I would suspect
> - it is a lot of work and at time t0, it was less valuable than some of the
> other efforts going at the time.
>
>
>
>>
>> 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)
>>
> Mumble, although probably true in absolute fact. The DEC VAX/VMS Fortran
> compiler was contemporary. I have always said that the best piece of work
> DEC Marketing ever did was convince the world that VMS Fortran was F77 (it
> was not). It ended up being a super-set, although it did not start out
> that way (similar to people believing VT-100's are ANSI - they are and in
> that case never did fully conform).
>
>
>
>
>>
>> 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?
>>
> I used the PCC/VAX version extensively (as well as ratfor) for the 'users
> space' part of my thesis work. My housemate, Tom Quarles, had developed
> SPICE3 (in C) and Ellis Cohen had written SPICE2 in FORTRAN. FPS had done
> a great deal of development on the array processor that was the basis for
> my work, all in Ratfor but assuming VMS under the coveres (they wrote an
> optimizing parallel Fortran compiler in same -- those guys are now the
> Portland Compiler Group).
>
>
> I worked, although moving stuff from VMS to BSD was huge because F77 !=
> VMS Fortran. Much of the 'grunt' work I had was making all that work. In
> fact, it was this work that I found a bug in the C compiler runtimes, that
> I have written about elsewhere. The ratfor code called F77, which shared
> C's runtime.
>
> ᐧ
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180319/df2c2825/attachment.html>
next prev parent reply other threads:[~2018-03-19 15:46 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
2018-03-19 15:43 ` Clem Cole
2018-03-19 15:46 ` Clem Cole [this message]
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=CAC20D2Mtgr1Sbsbe7jxSL+r6FJ2cC3n+z1UtczmdH_kce-g64g@mail.gmail.com \
--to=clemc@ccc.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).