From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FROM,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 28588 invoked from network); 3 Jan 2023 17:09:30 -0000 Received: from minnie.tuhs.org (50.116.15.146) by inbox.vuxu.org with ESMTPUTF8; 3 Jan 2023 17:09:30 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id 09259424FF; Wed, 4 Jan 2023 03:09:25 +1000 (AEST) Received: from mail-pj1-f53.google.com (mail-pj1-f53.google.com [209.85.216.53]) by minnie.tuhs.org (Postfix) with ESMTPS id 56288424FE for ; Wed, 4 Jan 2023 03:09:20 +1000 (AEST) Received: by mail-pj1-f53.google.com with SMTP id o1-20020a17090a678100b00219cf69e5f0so36455973pjj.2 for ; Tue, 03 Jan 2023 09:09:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=X/5GxxnjJOJvAVFuHx4cLYqkBvhRZgS9sasD4RIiG7E=; b=Ae4Yh9htGEWE2gylpfaz1dlUvqZasCZOoCtlXltgu8wXKzfEbtZ01r9lRlzDjv1nbI v1l/asbgg3nd/M5eBCEYvcf8vJNNr1d79eZQ09xQwR2dp7y0iDStBP8l5ApIDQmpyVhJ Eokvm+phe4MrfVqIyVTQMAQJjUiSaODpMQLr5sWZ+1d2Q0K9UAU+e1J8PLOFPFFwP7O8 uZA3Dyq48esUqCTyYG1i7rs9wleTt6iqElymbtA+BBTi15eBHgT13vQ1gb8Xh7uVv3vR t7US10GUfZlsBVWttpQhFN/rEbGqJk+HvCFKDYRVM2PBzMlIQeWq5Bz3RZoNndPBY6q/ Rszw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=X/5GxxnjJOJvAVFuHx4cLYqkBvhRZgS9sasD4RIiG7E=; b=CNfEYxBQNinUODEqqzLjO9yLOibQTtTjVmZdY7zznh2bDN80zmDS5iuGtHQrd9l5sk anDRuYwDqP1y/LQ52o94D8yddt+ar9dgnrGRpLfSqjCvMwadwKAYvK41rTY8ALZzZJwv G8YyqZY/h90WMEKlhD0N84OMEPD+4jxY6gW0ZDUckmimsyR8QSW9DjdvsHFEjz7Pw0oM HivX4tzLcQHTW8xQ7NQ2rVGRWRGQ1407o4TIm8vx8YoTGBmt1N+FGe28gMzEpCREoE7F mWxgRtPIMY/OozJaLkq/FVsnKBPAwiWPBKinc/8bfSmNFZ7/iuUP45JKsLF88kP9Vo52 JUYw== X-Gm-Message-State: AFqh2kpeDSWkAyIUZcMT2BjNyY/8VL5z9BKII8FonTx7UeCpmF3pjWii 0MMDNwiGRmafM6qB12hvaMhgd9JABeXb2gk9grWl6osK X-Google-Smtp-Source: AMrXdXvP0/nEs5VKrFBDi3DvB11MoDko1OSBOTeYNyTEjd+u2hJ20VtJVZA32XQjpQAfUVtuhTd9F4zaRsxp16oiW0M= X-Received: by 2002:a17:902:9a8d:b0:190:fc95:b01e with SMTP id w13-20020a1709029a8d00b00190fc95b01emr788746plp.128.1672765699757; Tue, 03 Jan 2023 09:08:19 -0800 (PST) MIME-Version: 1.0 Received: by 2002:a05:6a10:6811:b0:36a:70b3:9101 with HTTP; Tue, 3 Jan 2023 09:08:18 -0800 (PST) In-Reply-To: References: <52FB6638-AEFF-4A4F-8C2E-32089D577BA0@planet.nl> <464819f0-d2f6-2a60-6481-a194f4428b4d@case.edu> <20221230200246.GW5825@mcvoy.com> <88f83b4c-b3f9-ed87-b2fa-560fb369742a@makerlisp.com> <20221231035931.GG5825@mcvoy.com> <528f0c53-ccc2-88a1-5a7b-120362c648dd@mhorton.net> <20230102165120.GK25547@mcvoy.com> From: Paul Winalski Date: Tue, 3 Jan 2023 12:08:18 -0500 Message-ID: To: Clem Cole Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Message-ID-Hash: HUFTOWNLWXOLQEUHSGI32K3DPRI4E455 X-Message-ID-Hash: HUFTOWNLWXOLQEUHSGI32K3DPRI4E455 X-MailFrom: paul.winalski@gmail.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-tuhs.tuhs.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: tuhs@tuhs.org X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: A few comments on porting the Bourne shell List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On 1/2/23, Clem Cole wrote: > > FWIW: In my start-up times, under the same rules of being disciplined, as > VP of Engineering, I insisted, all C and C++ code was required to > 'flex-e-lint' warning clean. I gave my folks a 3-week week slip to clea= n > everything up. I was cursed during that time. But guess what, the > outstanding bug list dropped to =E2=85=92 of what it had been. Created q= uite a few > true believers. And we made those 3 weeks back before we were done. This was also the policy in DEC's compiler and software development tools groups. This was mainly VMS stuff and we didn't have flex and lint, but as Clem can attest the C and C++ compilers had very extensive warning capabilities. It was group policy that all code had to compile cleanly, without triggering diagnostic messages, before check-in was allowed. Once you get through the initial cleanup of existing code, this policy pays back big time in avoidance of nasty Heisenbugs. -Paul W.