rc-list - mailing list for the rc(1) shell
 help / color / mirror / Atom feed
From: byron@netapp.com (Byron Rakitzis)
To: malte@techfak.uni-bielefeld.de, rc@hawkwind.utcs.toronto.edu
Subject: Re:  rc and signal handlers
Date: Thu, 5 Nov 1992 17:00:28 -0500	[thread overview]
Message-ID: <9211052200.AA21626@netapp.netapp.com> (raw)

signal handlers ARE function definitions. They just have the
added feature that they get run at "interrupt level". If
it's not obvious that you can't "return" from a signal
handler, then you need to think a little more carefully
about what signals are.

btw,

; fn sigint { echo hi }
; sigint
hi
;


             reply	other threads:[~1992-11-05 22:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-11-05 22:00 Byron Rakitzis [this message]
     [not found] <cks@hawkwind.utcs.toronto.edu>
1992-11-06 12:03 ` malte
  -- strict thread matches above, loose matches on Subject: below --
1992-11-05 20:45 malte
1992-11-05 23:16 ` Chris Siebenmann

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=9211052200.AA21626@netapp.netapp.com \
    --to=byron@netapp.com \
    --cc=malte@techfak.uni-bielefeld.de \
    --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).