From: Greg 'groggy' Lehey <grog@lemis.com>
To: Clem Cole <clemc@ccc.com>
Cc: COFF <coff@tuhs.org>
Subject: [COFF] Weedhopper? (was: crt0 -- what's in that name?)
Date: Tue, 13 Jun 2023 09:57:08 +1000 [thread overview]
Message-ID: <20230612235708.GI83871@eureka.lemis.com> (raw)
In-Reply-To: <CAC20D2MCf6bk9QeO3gV0FnkYmB8GV304aK8seY-tAOchEa6POA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Monday, 12 June 2023 at 18:39:32 -0400, Clem Cole wrote:
> 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 ...
Now there's a word I have never heard before. Neither have my
dictionaries, and Google gets sidetracked. What's the meaning and the
background?
On the other hand, I have heard of BSS and BES. It was in the DDP-516
(basis for the IMP) assembler. Is that how it found its way into
Unix?
Greg
--
Sent from my desktop computer.
Finger grog@lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA.php
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 163 bytes --]
next prev parent reply other threads:[~2023-06-12 23:57 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 ` [COFF] Re: [TUHS] Re: crt0 -- what's in that name? Clem Cole
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 ` Greg 'groggy' Lehey [this message]
2023-06-13 0:30 ` [COFF] Re: Weedhopper? (was: crt0 -- what's in that name?) 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=20230612235708.GI83871@eureka.lemis.com \
--to=grog@lemis.com \
--cc=clemc@ccc.com \
--cc=coff@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).