The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Paul Winalski <paul.winalski@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 21:16:37 -0500	[thread overview]
Message-ID: <CABH=_VRt01u3W7GFVw-wjyuVFP5wsvutKAqt4Ek5B=BKYWbhRw@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2MNv7naAON2S9kUAuOZzHJJzwNg8gqxy4s_C4E=-8qPZg@mail.gmail.com>

On 2/3/19, Clem Cole <clemc@ccc.com> wrote:
> On Sun, Feb 3, 2019 at 5:14 PM Henry Bent <henry.r.bent@gmail.com> wrote:
>
>> 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.
>>
> Truth is most of the important ones went into Fortran-90 if I understand it
> correctly (I'd trust Paul W.s comments if he knows).  Again, I'm not a
> compiler guy, but I've been known to eat lunch with a few of them :-)

The de facto standard for Fortran in the 1970s was IBM Fortran IV.
All of the important academic packages, both in the physical sciences
and the stats packages (SPSS, BMDP, etc.) used in Economics,
Psychology, Sociology, etc., were written in Fortran IV.  The ANSI
(later ISO) standards committee was more or less an irrelevancy.
Vendors added their own proprietary extensions to Fortran IV.  With
the VAX DEC was able to supplant IBM in the educational/research
marketplace by offering mainframe-level performance at a fraction of
the IBM price.  VAX Fortran, and its extensions to Fortran IV, thus
became the new de facto standard in the education/research market in
the early 1980s.  VAX Fortran did eventually implement all of the
features of Fortran 77, but for quite a long time we didn't bother
implementing the missing pieces because there was no market demand for
them.  As Clem said, the important VAX Fortran extensions to Fortran
IV have over time made their way into the ISO standard.

-Paul W.

      reply	other threads:[~2019-02-04  2:17 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
2019-02-03 22:23   ` Clem Cole
2019-02-04  2:16     ` Paul Winalski [this message]

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='CABH=_VRt01u3W7GFVw-wjyuVFP5wsvutKAqt4Ek5B=BKYWbhRw@mail.gmail.com' \
    --to=paul.winalski@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).