From mboxrd@z Thu Jan 1 00:00:00 1970 From: usotsuki@buric.co (Steve Nickolas) Date: Mon, 27 Jun 2016 11:23:43 -0400 (EDT) Subject: [TUHS] Bizarre job control, was csh In-Reply-To: <577142a7.64xQskFrCzJbQBN3%schily@schily.net> References: <201606261014.u5QAE1qX015184@skeeve.com> <5770032F.8030306@mhorton.net> <20160626181450.GK26734@mcvoy.com> <57710068.Y5JOWn5FNyxO2PxU%schily@schily.net> <2D2E5333-6FCF-43DA-82D9-25B0E86CB325@tuhs.org> <577142a7.64xQskFrCzJbQBN3%schily@schily.net> Message-ID: On Mon, 27 Jun 2016, Joerg Schilling wrote: > Steve Nickolas wrote: > >> I tried a couple times to figure out how to implement a Bourne shell, and >> just couldn't figure it out. But then, I was never much of a programmer. > > It is hard and you cannot do it from just reading the POSIX standard. > > This is because the POSIX standard tries to write descriptions in an abstract > notation that missleads people that did never see a working implementation > before. > > After a few years of maintaining the Bourne Shell, I would know how to do it but > I am not interested to do it from scratch. > > Jörg > > Eh. I had a specific reason for doing it that most people would find idiotic - I was using OSes (DOS - mainly on a Tandy 1000, which in no way could ever hope to handle DJGPP - and Win32) that weren't remotely POSIX and I wanted to make them feel more Unixy without outright *emulating Unix*. -uso.