From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from minnie.tuhs.org (minnie.tuhs.org [IPv6:2600:3c01:e000:146::1]) by inbox.vuxu.org (Postfix) with ESMTP id D5BDF2164B for ; Mon, 20 May 2024 02:59:15 +0200 (CEST) Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id A5FD843AD9; Mon, 20 May 2024 10:59:11 +1000 (AEST) Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) by minnie.tuhs.org (Postfix) with ESMTPS id AFED843682 for ; Mon, 20 May 2024 10:59:06 +1000 (AEST) Received: by mail-pl1-x631.google.com with SMTP id d9443c01a7336-1ee42b97b32so60659415ad.2 for ; Sun, 19 May 2024 17:59:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1716166746; x=1716771546; darn=tuhs.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=Vtbq/2fnEg2CPgtXIPP09maE+FVLvF4bI21769fHlog=; b=fcO24B3azY9P2SSU1BYx9//NF4+3mqfEJ31v7J5J9543mYaAf5hjOLmDfqWfEuiEuA 2Mc4poYSXjNZDP9XqlsIsG5CdKVxbSfJwMHDtIjmkLWZUCqF7z6A075UXSJI1PmNTepZ 0/6SLZzQJMT0pZdLWJYDTTmMWvsnZWy0nLPvT8wu19Yl6J2+S5c/vgff9TrXox+uwMNF IDeQV1p3guzsHmriVG6o7nx3Pm19CfY4lyG47argDsT9rllIHxud78gLoSLC5r6apB+f 1t/0eUeSDtMUpTy6kMbYD6EO3RrMdchKB33ham2oPoIwFvlPn9k2N8s/38i1F/J8X7KD AXhQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716166746; x=1716771546; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=Vtbq/2fnEg2CPgtXIPP09maE+FVLvF4bI21769fHlog=; b=UvNsLWB70huaSsV4yFnmTYqo+Yy+/mdCL0m8EcQgseSqlpjmOGHDkXIJNzta2QlNP9 JFfoP9mTMBP1Y3Hlpbc7ejabBUI7f/YDi0Yc45ipjVyvHscdRVLfDDOsyVQ3hivT5JIJ hqFsKWEZyji7++iXkz/JCUg1M0j2E+VSnYx8GMAxzuwD59ynXPSsdPuOxIBmrT6aD4dn rPppu6zQmJEqdhUyn/UqJec+g3w+VLCUI8O4YFvVzw7sek2BsHgaEr0jCGBh/VzKC0hU WwBUGG5cVlfDOfAsMNVVwSbWmDry7kyXeyI8hQQ9+TTUcYUDnxXc+eQX09Zp0kOyIsCH JEIA== X-Gm-Message-State: AOJu0YwtwtL6yCiYpNsWAMHk9sH1oDQo7H3MJgom3XvuT5Qonxya8yzb YdcQNXvxiMsHo20WximhFY2gOag1iv+luLtkSf/hvf2EcC2R1guO3EzgendtO4gRJWCOSWTZjMJ 7TE4xK1SnK4ut66f/Xc2srXjbhfgyGQ== X-Google-Smtp-Source: AGHT+IFUg4p9L8Ib+U+/HBwP95cw1iGZCeHC1x2okC+6DwKp08LbFBH6f62r85jlSI8X0rVKr0rdAQqYOxsLYIJIzzA= X-Received: by 2002:a17:90a:df10:b0:2a0:2fb3:c1ff with SMTP id 98e67ed59e1d1-2b6cc773ffdmr24385112a91.15.1716166745919; Sun, 19 May 2024 17:59:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Rob Pike Date: Mon, 20 May 2024 10:58:54 +1000 Message-ID: To: Douglas McIlroy Content-Type: multipart/alternative; boundary="0000000000004418f30618d83560" Message-ID-Hash: ETEJHZ2GCB7UGKRP6RS4GKU5THU5YZVQ X-Message-ID-Hash: ETEJHZ2GCB7UGKRP6RS4GKU5THU5YZVQ X-MailFrom: robpike@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: TUHS main list X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: The 'usage: ...' message. (Was: On Bloat...) List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --0000000000004418f30618d83560 Content-Type: text/plain; charset="UTF-8" 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 --0000000000004418f30618d83560 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
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 par= sing error by inserting some token - semicolon, parenthesis, whatever seeme= d 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, despit= e PL/I being plastered with semicolons, but it did tend to ferret out more = errors per run. I found the tactic helpful.

-rob

--0000000000004418f30618d83560--