rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: arnold@cc.gatech.edu (Arnold Robbins)
To: rsalz@osf.org, arnold@cc.gatech.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re:  rc and signals
Date: Fri, 16 Apr 1993 12:02:50 -0400	[thread overview]
Message-ID: <9304161602.AA02488@penfold.cc.gatech.edu> (raw)
In-Reply-To: rsalz@osf.org's 31-line message on Apr 16, 11:30am

> >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


             reply	other threads:[~1993-04-16 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1993-04-16 16:02 Arnold Robbins [this message]
  -- strict thread matches above, loose matches on Subject: below --
1993-04-16 15:30 rsalz
1993-04-20  1:29 ` John Mackin
1993-04-16 15:00 Arnold Robbins

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=9304161602.AA02488@penfold.cc.gatech.edu \
    --to=arnold@cc.gatech.edu \
    --cc=rc@hawkwind.utcs.toronto.edu \
    --cc=rsalz@osf.org \
    /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).