From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from burdell.cc.gatech.edu ([130.207.3.207]) by hawkwind.utcs.toronto.edu with SMTP id <2764>; Fri, 16 Apr 1993 12:03:07 -0400
Received: from penfold.cc.gatech.edu by burdell.cc.gatech.edu with SMTP id AA09551
  (5.65c/IDA-1.4.4 for <rc@hawkwind.utcs.toronto.edu>); Fri, 16 Apr 1993 12:02:57 -0400
Received: by penfold.cc.gatech.edu (4.1/SMI-4.1)
	id AA02488; Fri, 16 Apr 93 12:02:50 EDT
From:	arnold@cc.gatech.edu (Arnold Robbins)
Message-Id: <9304161602.AA02488@penfold.cc.gatech.edu>
Date:	Fri, 16 Apr 1993 12:02:50 -0400
In-Reply-To: rsalz@osf.org's 31-line message on Apr 16, 11:30am
X-Ultrix: Just Say NO!
X-Important-Saying: Premature Optimization Is The Root Of All Evil.
X-Mailer: Mail User's Shell (7.2.3 5/22/91)
To:	rsalz@osf.org, arnold@cc.gatech.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re:  rc and signals

> >Then, at startup, sort the table, eliminate duplicates, and voila, the
> >signal can be used an index again.
> 
> No it can't; suppose I have a machine that leaves some signal numbers unused?

It's a Simple Matter Of Programming to fill in the blank spots with
an entry that says "invalid signal" or "signal 17 (noname)".  I don't *think*
there are too many systems where the signal numbers are non-contiguous.

> >  DGK is one smart guy
> 
> I remain mildly convinced that this is not true.

Let me rephrase this then.  He's a pretty good programmer.  I also think he's
too quick to add features, but that's a different issue from "is ksh well
written code or not".  In my experience, ksh comes up and runs > 95% of the
time on almost any kind of Unix system out there. Ksh is generally the first
thing I bring up on a new system that doesn't have it (long habit, sorry :-).
Probably soon that will no longer be true for me, it'll be es (+ or - readline).

Arnold