Apologies to TUHS - other than please don't think Fortran did not impact
UNIX and its peers. We owe that community our jobs, and for creating the
market in that we all would build systems and eventually improve.
Note: I'm CCing COFF - you want to continue this...
On Mon, Jun 12, 2023 at 5:39 PM G. Branden Robinson <
g.branden.robinson(a)gmail.com> wrote:
> It's an ill wind that blows a Fortran runtime using the same convention.
>
Be careful there, weedhopper ... Fortran gave a lot to computing
(including UNIX) and frankly still does. I did not write have too much
Fortran as a professional (mostly early in my career), but I did spent 50+
years ensuring that the results of the Fortran compiler ran >>really well<<
on the systems I built. As a former collegiate of Paul W and I once said,
"*Any computer executive that does not take Fortran seriously will not have
their job very long.* It pays our salary."
It's still the #1 language for science [its also not the same language my
Father learned in the late 50s/early 60s, much less the one I learned 15
years later - check out: In what type of work is the Fortran Programming
Language most used today
<https://www.quora.com/In-what-type-of-work-is-the-Fortran-programming-langu…>
, Is Fortran still alive
<https://www.quora.com/Is-Fortran-still-alive/answer/Clem-Cole>, Is Fortran
obsolete <https://www.quora.com/Is-Fortran-obsolete/answer/Clem-Cole>
FWIW: These days, the Intel Fortran compiler (and eventually the LLVM one,
which Intel is the primary developer), calls the C/C++ common runtime for
support. Most libraries are written in C, C++, (or assembler in some very
special cases) - so now it's C that keeps Fortran alive. But "in the
beginning" it was all about Fortran because that paid the bills then and
still does today.
ᐧ
