The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Greg 'groggy' Lehey <grog@lemis.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Obscene languages (was: Does anybody know the etymology of the term "word" as in collection of bits?)
Date: Sat, 10 Sep 2022 11:49:20 +1000	[thread overview]
Message-ID: <20220910014919.GA9081@eureka.lemis.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2209100734520.71191@aneurin.horsfall.org>

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

On Saturday, 10 September 2022 at  7:44:57 +1000, Dave Horsfall wrote:
> COBOL?  FORTRAN?  RPG?  Those are all swear words to me :-)

Is this an indirect reference to the "Programmer's ABC" in the March
1976 issue of Datamation?  I have a copy of the lot at
http://www.lemis.com/grog/Humour/ABC.php, but the one I think you're
referring to is:

  L is for language; use these three.
  Cobol, Fortran, RPG.
  Avoid all others, friend, and shun
  Those with the suffix "L slash I."

And yes, I share your sentiment.

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 --]

      reply	other threads:[~2022-09-10  1:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09 19:39 [TUHS] Re: Does anybody know the etymology of the term "word" as in collection of bits? Nelson H. F. Beebe
2022-09-09 20:27 ` Bakul Shah
2022-09-09 21:12   ` Henry Bent
2022-09-09 21:44   ` Dave Horsfall
2022-09-10  1:49     ` Greg 'groggy' Lehey [this message]

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=20220910014919.GA9081@eureka.lemis.com \
    --to=grog@lemis.com \
    --cc=dave@horsfall.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).