The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: usotsuki@buric.co (Steve Nickolas)
Subject: [TUHS] Bizarre job control, was csh
Date: Mon, 27 Jun 2016 11:23:43 -0400 (EDT)	[thread overview]
Message-ID: <alpine.BSF.2.02.1606271121490.46310@frieza.hoshinet.org> (raw)
In-Reply-To: <577142a7.64xQskFrCzJbQBN3%schily@schily.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 942 bytes --]

On Mon, 27 Jun 2016, Joerg Schilling wrote:

> Steve Nickolas <usotsuki at buric.co> 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.


  reply	other threads:[~2016-06-27 15:23 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-26 10:14 [TUHS] Origin year of BSD csh? Aharon Robbins
2016-06-26 16:30 ` Mary Ann Horton
2016-06-26 18:14   ` Larry McVoy
2016-06-26 18:32     ` Ronald Natalie
2016-06-26 20:43       ` John Cowan
2016-06-27  0:59         ` Larry McVoy
2016-06-27  1:11           ` John Cowan
2016-06-27 11:27       ` Sven Mascheck
2016-06-27 12:47         ` Steve Nickolas
2016-06-27 14:58         ` Joerg Schilling
2016-06-27 15:29           ` Ronald Natalie
2016-06-27 16:22         ` John Cowan
2016-06-27 16:35           ` Steve Nickolas
2016-06-27 20:00         ` Dave Horsfall
2016-06-27 20:33         ` Ronald Natalie
2016-06-27 20:44           ` Clem Cole
2016-06-27 21:02           ` Steve Nickolas
2016-06-27 21:15             ` Ronald Natalie
2016-06-27 21:20           ` John Cowan
2016-06-27 21:28             ` Ronald Natalie
2016-06-27 21:45               ` John Cowan
2016-06-28  6:49               ` Peter Jeremy
2016-06-28  7:51                 ` arnold
2016-06-27 21:29           ` Random832
2016-06-28 14:47         ` Tony Finch
2016-06-26 19:41     ` Clem Cole
2016-06-27 10:31       ` Joerg Schilling
2016-06-27 13:01         ` Ronald Natalie
2016-06-27 13:15           ` Steffen Nurpmeso
2016-06-27 15:17           ` Joerg Schilling
2016-06-27 13:39         ` [TUHS] Bizarre job control, was csh Warren Toomey
2016-06-27 15:00           ` Steve Nickolas
2016-06-27 15:13             ` Joerg Schilling
2016-06-27 15:23               ` Steve Nickolas [this message]
2016-06-26 20:58     ` [TUHS] Origin year of BSD csh? Steve Nickolas
2016-06-27 10:03 ` Joerg Schilling

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=alpine.BSF.2.02.1606271121490.46310@frieza.hoshinet.org \
    --to=usotsuki@buric.co \
    /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).