From: Rob Pike <robpike@gmail.com>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: The 'usage: ...' message. (Was: On Bloat...)
Date: Mon, 20 May 2024 10:58:54 +1000 [thread overview]
Message-ID: <CAKzdPgyr25oP2GP90H0r6U2H6SJjNMxhoWZ6JZmHsrapogYNoQ@mail.gmail.com> (raw)
In-Reply-To: <CAKH6PiUoQBjD3cMHWELN3Hp+jf0=2fyFcqNbfwwe76YfKjGFiw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 561 bytes --]
The Cornell PL/I compiler, PL/C, ran on the IBM 360 so of course used batch
input. It tried automatically to keep things running after a parsing error
by inserting some token - semicolon, parenthesis, whatever seemed best -
and continuing to parse, in order to maximize the amount of input that
could be parsed before giving up. At least, that's what I took the
motivation to be. It rarely succeeded in fixing the actual problem, despite
PL/I being plastered with semicolons, but it did tend to ferret out more
errors per run. I found the tactic helpful.
-rob
[-- Attachment #2: Type: text/html, Size: 873 bytes --]
next prev parent reply other threads:[~2024-05-20 0:59 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 ` Rob Pike [this message]
2024-05-20 3:19 ` [TUHS] " 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
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=CAKzdPgyr25oP2GP90H0r6U2H6SJjNMxhoWZ6JZmHsrapogYNoQ@mail.gmail.com \
--to=robpike@gmail.com \
--cc=douglas.mcilroy@dartmouth.edu \
--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).