From: lm at mcvoy.com (Larry McVoy)
Subject: [COFF] How much Fortran?
Date: Sun, 2 Feb 2020 19:47:29 -0800 [thread overview]
Message-ID: <20200203034729.GN3216@mcvoy.com> (raw)
In-Reply-To: <acbac8c4-fb0f-4419-bb22-2349493b2236@kilonet.net>
When I was in school the calling convention had been sorted, just barely.
You could call libc stuff from fortran but it didn't really work, the
types didn't match up. But if you stuck to the basics, you could make
it work.
My Dad was a physics prof, theory guy, I coded some Fortran for him.
It was definitely _the_ language for the physics guys. I'm close
friends with Bill Long at Cray, he's been on the Fortran steering
committee for decades.
It is still a thing. Big in the physics world and it has evolved.
It's much better than it was.
How big was it 30 years ago? In my opinion, tiny compared to C.
On Sun, Feb 02, 2020 at 08:38:43PM -0500, Arthur Krewat wrote:
> So, given the membership here, I wonder, does anyone have the inside scoop?
> How much Fortran was used ?
>
> https://science.slashdot.org/story/20/01/31/1837209/nasa-is-trying-to-save-voyager-2-after-a-power-glitch-shut-down-its-instruments
>
>
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2020-02-03 3:47 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 [this message]
2020-02-03 15:53 ` clemc
2020-02-03 16:06 ` lm
2020-02-03 16:20 ` clemc
2020-02-03 19:50 ` dave
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=20200203034729.GN3216@mcvoy.com \
--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).