From: rsalz@osf.org
To: arnold@cc.gatech.edu, rc@hawkwind.utcs.toronto.edu
Subject: Re: rc and signals
Date: Fri, 16 Apr 1993 11:30:40 -0400 [thread overview]
Message-ID: <9304161530.AA13016@earth.osf.org> (raw)
> #ifdef SIGFOO
> { SIGFOO, "sigfoo", "murphy came to town"},
> #endif /* SIGFOO */
Yes, of course, this is the right way to do it.
>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?
> DGK is one smart guy
I remain mildly convinced that this is not true.
/r$
next reply other threads:[~1993-04-16 15:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-04-16 15:30 rsalz [this message]
1993-04-20 1:29 ` John Mackin
-- strict thread matches above, loose matches on Subject: below --
1993-04-16 16:02 Arnold Robbins
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=9304161530.AA13016@earth.osf.org \
--to=rsalz@osf.org \
--cc=arnold@cc.gatech.edu \
--cc=rc@hawkwind.utcs.toronto.edu \
/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).