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=-1.0 required=5.0 tests=MAILING_LIST_MULTI
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 23354 invoked from network); 2 Jan 2023 18:13:11 -0000
Received: from minnie.tuhs.org (50.116.15.146)
  by inbox.vuxu.org with ESMTPUTF8; 2 Jan 2023 18:13:11 -0000
Received: from minnie.tuhs.org (localhost [IPv6:::1])
	by minnie.tuhs.org (Postfix) with ESMTP id 2A5E94248A;
	Tue,  3 Jan 2023 04:12:50 +1000 (AEST)
Received: from mcvoy.com (mcvoy.com [192.169.23.250])
	by minnie.tuhs.org (Postfix) with ESMTPS id 85DE14248A
	for <tuhs@tuhs.org>; Tue,  3 Jan 2023 04:12:42 +1000 (AEST)
Received: by mcvoy.com (Postfix, from userid 3546)
	id 95A8E35E848; Mon,  2 Jan 2023 10:12:42 -0800 (PST)
Date: Mon, 2 Jan 2023 10:12:42 -0800
From: Larry McVoy <lm@mcvoy.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Message-ID: <20230102181242.GO25547@mcvoy.com>
References: <88f83b4c-b3f9-ed87-b2fa-560fb369742a@makerlisp.com>
 <20221231035931.GG5825@mcvoy.com>
 <alpine.BSF.2.21.9999.2212311516330.69068@aneurin.horsfall.org>
 <528f0c53-ccc2-88a1-5a7b-120362c648dd@mhorton.net>
 <CAC20D2NZbBa9PK_F50iWVn+t7m8=_mcw4mR2mKcTgDbdqxJi=w@mail.gmail.com>
 <20230102165120.GK25547@mcvoy.com>
 <E977D385-604F-49A9-83FD-8C5270623066@gmail.com>
 <20230102174304.GM25547@mcvoy.com>
 <59004a29-5119-9dd9-c248-518b8c4e7928@makerlisp.com>
 <20230102180020.p6gmiwhrnidfbfsc@illithid>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20230102180020.p6gmiwhrnidfbfsc@illithid>
User-Agent: Mutt/1.5.24 (2015-08-30)
Message-ID-Hash: QLNGBCOCGVVIDFTSBOITZ26AD53RPEW7
X-Message-ID-Hash: QLNGBCOCGVVIDFTSBOITZ26AD53RPEW7
X-MailFrom: lm@mcvoy.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 <tuhs.tuhs.org>
Archived-At: <https://www.tuhs.org/mailman3/hyperkitty/list/tuhs@tuhs.org/message/QLNGBCOCGVVIDFTSBOITZ26AD53RPEW7/>
List-Archive: <https://www.tuhs.org/mailman3/hyperkitty/list/tuhs@tuhs.org/>
List-Help: <mailto:tuhs-request@tuhs.org?subject=help>
List-Owner: <mailto:tuhs-owner@tuhs.org>
List-Post: <mailto:tuhs@tuhs.org>
List-Subscribe: <mailto:tuhs-join@tuhs.org>
List-Unsubscribe: <mailto:tuhs-leave@tuhs.org>

On Mon, Jan 02, 2023 at 12:00:20PM -0600, G. Branden Robinson wrote:
> > > If it ain't broke, don't fix it.
> 
> They were all broken.  Badly.  If your scripts worked, you got lucky at
> Russian Roulette.  No greater claim to robustness can be made.
> 
> POSIX shell conformance still proves challenging for vendors, but is an
> immense improvement over the status quo ante.

You are talking to a dude with 40+ years of Unix experience, supporting
commercial products most of that time.  I didn't get "lucky at Russian
Roulette", I wrote scripts that were portable.  I have 40 year old scripts
that _still_ work and they work on virtually every Unix ever built.
How do I know?  I was a contractor for my first job, I got plopped down
in front of every random unix you could imagine and each time I polished
off the warts.

I spent decades supporting my own products on every flavor of Unix and
processors from Arm to System/360.  Oh, and Windows XP and on and MacOS.

My scripts worked with /bin/sh being whatever it was.

It's interesting to me that other old timers, like Clem, are saying
exactly the same thing as I am.  Are we all wrong?