From: Henry Bent <henry.r.bent@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Commercial UNIX was other stuff before
Date: Sun, 3 Feb 2019 17:14:05 -0500 [thread overview]
Message-ID: <CAEdTPBfzy=qhHfF3x8=-b3jBS0TT3GbTf-o7q576xaZT1GZQeA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2PQV7T4-LfdOhTjfW0Wraf8iK7=-agdZHfAXxyz9wbTkA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 920 bytes --]
On Sun, 3 Feb 2019 at 16:00, Clem Cole <clemc@ccc.com> wrote:
> BTW: this attitude was nothing new. I've said it before, the greatest
> piece of marketing DEC ever did was convince the world that VMS Fortran was
> Fortran-77. It was not close. And when you walked into most people
> writing real production code (in Fortran of course), you discovered they
> had used all of the VMS Fortran extensions. When the UNIX folks arrived
> on the scene the f77 in Seventh Edition was not good enough. You saw first
> Masscomp in '85, then a year later Apollo and 2 years after that, Sun
> develop really, really good Fortran's -- all that were VMS Fortran
> compatible.
>
This code was apparently so pervasive and long-lived that the GNU Fortran
compiler added compatibility for DEC extensions less than two years ago, in
version 7. There must be enough demand for DEC's additions to have made it
worthwhile.
-Henry
[-- Attachment #2: Type: text/html, Size: 1590 bytes --]
next prev parent reply other threads:[~2019-02-03 22:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 20:58 Clem Cole
2019-02-03 21:08 ` Cág
2019-02-03 22:20 ` Clem Cole
2019-02-04 9:33 ` Marcus MERIGHI
2019-02-04 12:32 ` Steffen Nurpmeso
2019-02-03 21:17 ` Larry McVoy
2019-02-03 22:14 ` Henry Bent [this message]
2019-02-03 22:23 ` Clem Cole
2019-02-04 2:16 ` 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='CAEdTPBfzy=qhHfF3x8=-b3jBS0TT3GbTf-o7q576xaZT1GZQeA@mail.gmail.com' \
--to=henry.r.bent@gmail.com \
--cc=clemc@ccc.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).