From: John Cowan <cowan@ccil.org>
To: John Levine <johnl@taugh.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: The 'usage: ...' message. (Was: On Bloat...)
Date: Mon, 20 May 2024 21:14:55 -0400 [thread overview]
Message-ID: <CAD2gp_T06aeZ607fr6veE9T2CmSpxOPE+=nT5ywAUxAhGBjVZQ@mail.gmail.com> (raw)
In-Reply-To: <20240520201100.50BE18B94A62@ary.qy>
[-- Attachment #1: Type: text/plain, Size: 1465 bytes --]
On Mon, May 20, 2024 at 4:11 PM John Levine <johnl@taugh.com> wrote:
It appears that Clem Cole <clemc@ccc.com> said:
> >“The PL/C compiler had the unusual capability of never failing to compile
> >> any program, through the use of extensive automatic correction of many
> >> syntax errors and by converting any remaining syntax errors to output
> >> statements.”
> PL/C was a long time ago in the early 1970s. People used it on batch
> systems whre you handed in your cards at the window, waited a while,
> and later got your printout back. Or at advanced places, you could
> run the cards through the reader yourself, then wait until the batch
> ran.
PL/C was a 3rd-generation autocorrection programming language. CORC was
the 1962 version and CUPL was the 1966 version (same date as DWIM), neither
of them based on PL/I. There is an implementation of both at <
http://www.catb.org/~esr/cupl/>.
The Wikipedia DWIM article also points to Magit, the Emacs git client.
>
> In that environment, the benefit from possibly guessing an error
> correction right meant fewer trips to the card reader. In my youth I
> did a fair amount of programming that way in WATFOR/WATFIV and Algol W
> where we really tried to get the programs right since we wanted to
> finish up and go home.
>
> When I was using interactive systems where you could fix one bug and
> try again, over and over, it seemed like cheating.
>
> R's,
> John
>
[-- Attachment #2: Type: text/html, Size: 2636 bytes --]
next prev parent reply other threads:[~2024-05-21 1:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-19 23:08 [TUHS] " Douglas McIlroy
2024-05-20 0:58 ` [TUHS] " Rob Pike
2024-05-20 3:19 ` arnold
2024-05-20 3:43 ` Warner Losh
2024-05-20 4:46 ` arnold
2024-05-20 9:20 ` [TUHS] A fuzzy awk. (Was: The 'usage: ...' message.) Ralph Corderoy
2024-05-20 11:58 ` [TUHS] " arnold
2024-05-20 13:10 ` Chet Ramey
2024-05-20 13:30 ` [TUHS] Re: A fuzzy awk Ralph Corderoy
2024-05-20 13:48 ` Chet Ramey
2024-05-20 3:54 ` [TUHS] Re: The 'usage: ...' message. (Was: On Bloat...) Bakul Shah via TUHS
2024-05-20 14:23 ` Clem Cole
2024-05-20 17:30 ` Greg A. Woods
2024-05-20 20:10 ` John Levine
2024-05-21 1:14 ` John Cowan [this message]
2024-05-20 17:40 ` Stuff Received
-- strict thread matches above, loose matches on Subject: below --
2024-05-19 14:03 [TUHS] " Douglas McIlroy
2024-05-19 16:18 ` [TUHS] " Paul Winalski
2024-05-19 16:21 ` Paul Winalski
2024-05-19 20:42 ` Dave Horsfall
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='CAD2gp_T06aeZ607fr6veE9T2CmSpxOPE+=nT5ywAUxAhGBjVZQ@mail.gmail.com' \
--to=cowan@ccil.org \
--cc=johnl@taugh.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).