Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>,
	Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Re: crt0 -- what's in that name?
Date: Mon, 12 Jun 2023 18:39:32 -0400	[thread overview]
Message-ID: <CAC20D2MCf6bk9QeO3gV0FnkYmB8GV304aK8seY-tAOchEa6POA@mail.gmail.com> (raw)
In-Reply-To: <20230612213912.mywv5znz66pk3n5q@illithid>

[-- Attachment #1: Type: text/plain, Size: 1888 bytes --]

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@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-language-most-used-today/answer/Clem-Cole>
,  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.

ᐧ

[-- Attachment #2: Type: text/html, Size: 3647 bytes --]

       reply	other threads:[~2023-06-12 22:40 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAP6exYKUbHjLJm=PNuxtzF49NfOc3q1rpkRLeGqaPpp-=RwFTw@mail.gmail.com>
     [not found] ` <CAEoi9W4DJXEXfr=iMOnTQVedHzcOamPyvpWy413j3_=dXrMB1g@mail.gmail.com>
     [not found]   ` <alpine.BSF.2.21.9999.2306130615560.16633@aneurin.horsfall.org>
     [not found]     ` <CAC20D2PiOh-p48G83ChUYZnfHTdNXROcJsewwmbM1xnyrt4c9w@mail.gmail.com>
     [not found]       ` <20230612213912.mywv5znz66pk3n5q@illithid>
2023-06-12 22:39         ` Clem Cole [this message]
2023-06-12 22:50           ` G. Branden Robinson
2023-06-12 22:57             ` Clem Cole
2023-06-12 23:04           ` Paul Winalski
2023-06-12 23:49             ` G. Branden Robinson
2023-06-13 16:28               ` Paul Winalski
2023-06-13 17:04                 ` segaloco via COFF
2023-06-13 17:32                   ` Clem Cole
2023-06-13 17:02               ` [COFF] Re: UNIX and its users - new or old Clem Cole
2023-06-14 13:33                 ` Dan Cross
2023-06-14 15:39                   ` Clem Cole
2023-06-14 22:13                     ` Dan Cross
2023-06-15  4:20                       ` Adam Thornton
2023-06-15 12:13                         ` Dan Cross
2023-06-12 23:57           ` [COFF] Weedhopper? (was: crt0 -- what's in that name?) Greg 'groggy' Lehey
2023-06-13  0:30             ` [COFF] " G. Branden Robinson
2023-06-13  3:07               ` Clem Cole
2023-06-13  3:05             ` Clem Cole
2023-06-13  3:26               ` Bakul Shah

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=CAC20D2MCf6bk9QeO3gV0FnkYmB8GV304aK8seY-tAOchEa6POA@mail.gmail.com \
    --to=clemc@ccc.com \
    --cc=coff@tuhs.org \
    --cc=g.branden.robinson@gmail.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).