From: malte@techfak.uni-bielefeld.de
To: rc@hawkwind.utcs.toronto.edu
Subject: Re: aha
Date: Fri, 6 Nov 1992 07:14:58 -0500 [thread overview]
Message-ID: <9211061214.AA01731@dahlie.techfak.uni-bielefeld.de> (raw)
In-Reply-To: Mail from 'byron@netapp.com (Byron Rakitzis)' dated: Thu, 5 Nov 1992 21:25:59 -0500
Wait! $status already gets set asynchronously with signal handlers
every time they run a command.
Works great! Instead of
fn sigint { return 1 }
while( ~ $status(0) 0 ) { ... }
I use
fn false { return 1 }
fn sigint { false }
while( ~ $status(0) 0 ) { ... }
So perhaps the signal handler code
should stash away the old $status and restore it after the signal
handler is done running.
This make it impossible (I think) to program something as "do this as long
as it works but not longer than 10 seconds".
Malte
next reply other threads:[~1992-11-06 12:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-11-06 12:14 malte [this message]
[not found] <haahr@mv.us.adobe.com>
1992-11-06 13:36 ` aha malte
-- strict thread matches above, loose matches on Subject: below --
1992-11-06 13:29 aha Paul Haahr
1992-11-06 2:25 aha Byron Rakitzis
1992-11-06 1:22 aha Tom Culliton x2278
1992-11-06 0:28 aha Byron Rakitzis
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=9211061214.AA01731@dahlie.techfak.uni-bielefeld.de \
--to=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).