From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Clem Cole <clemc@ccc.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 17:50:13 -0500 [thread overview]
Message-ID: <20230612225013.ru6jfhv2tmjjftxn@illithid> (raw)
In-Reply-To: <CAC20D2MCf6bk9QeO3gV0FnkYmB8GV304aK8seY-tAOchEa6POA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 987 bytes --]
Hi Clem,
At 2023-06-12T18:39:32-0400, Clem Cole wrote:
> 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.
Absolutely. Fortran (77) was the first language this weedhopper learned
after BASIC (which, while much despised by the sorts of people who
update jargon files, _also_ had early support in CSRC Unix). While I
intensely disliked the fixed-source format (a defect Fortran 90
remedied), I acquired it more easily than C, to the relief of the guys
on my class project team who already knew C and _hated_ Fortran.
My wisecrack was not meant as a derogation of Fortran in any way, but
rather as a sly (not really) allusion to a word also appearing in your
expansion of the COFF list's name as seen above...
Best regards to you and to Fortran, and a nod to the copy of
Metcalf/Reid/Cohen on my bookshelf,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-06-12 22:50 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
2023-06-12 22:50 ` G. Branden Robinson [this message]
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=20230612225013.ru6jfhv2tmjjftxn@illithid \
--to=g.branden.robinson@gmail.com \
--cc=clemc@ccc.com \
--cc=coff@tuhs.org \
--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).