From: dave at horsfall.org (Dave Horsfall)
Subject: [COFF] How much Fortran?
Date: Tue, 4 Feb 2020 06:50:52 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.2002040647590.33501@aneurin.horsfall.org> (raw)
In-Reply-To: <CAC20D2Mc3-KgBbxoHt5cJOR7DnPJbA=EDzUso6TAf+vrq=zu+Q@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
On Mon, 3 Feb 2020, Clem Cole wrote:
> Frankly, I would have expected the folks at this(these) NASA
> contractor(s) to have used assembler in those days under the guise of
> "efficiency;" but Fortran-IV would definitely have been popular at many
> contractors that would have been doing the work. The article mentions
> Fortran-V which I find interesting because I did not believe it was
> really much of a thing (i.e. it was never standardized). Basically, as
> I understood it from my Fortran peeps at DEC/Intel, F-V was the Waterloo
> extensions (a.k.a. WatFor) that got picked up by most people and in
> particular, IBM added to the FORTRAN/G or H compiler for the S/360. DEC
> had gone in a different direction still with VMS FORTRAN, although I
> believe they had picked up the things like WRITE(*) from Waterloo.
And WATFIV as well, as I recall from my student days; it was closer to
FORTRAN than WATFOR was (both were "student" compilers e.g. better error
messages but not the best of generated code).
-- Dave
next prev parent reply other threads:[~2020-02-03 19:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 1:38 krewat
2020-02-03 3:47 ` lm
2020-02-03 15:53 ` clemc
2020-02-03 16:06 ` lm
2020-02-03 16:20 ` clemc
2020-02-03 19:50 ` dave [this message]
2020-02-03 17:01 ` thomas.paulsen
2020-02-03 4:50 ` drb
2020-02-03 17:06 ` crossd
2020-02-03 18:36 `
2020-02-03 19:26 ` cym224
2020-02-04 1:25 ` wobblygong
2020-02-06 4:59 rudi.j.blom
2020-02-06 20:04 ` dave
2020-02-07 21:09 dave
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=alpine.BSF.2.21.9999.2002040647590.33501@aneurin.horsfall.org \
--to=coff@minnie.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).