Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!lll-winken!indri!nic.MR.NET!hal!ncoast!allbery
From: allbery@ncoast.ORG (Brandon S. Allbery)
Newsgroups: comp.unix.wizards
Subject: Avoiding longjmp
Message-ID: <13624@ncoast.ORG>
Date: 7 May 89 17:45:47 GMT
Reply-To: allbery@ncoast.ORG (Brandon S. Allbery)
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 13

This should by rights be a followup, but the References: line is too long
for either our inews or our rn to cope with.

Might I suggest that the proper method for dealing with asynchronous signals
of any sort without "longjmp" or its equivalent has been known for some time
now.  It's called an event loop.

++Brandon
-- 
Brandon S. Allbery, moderator of comp.sources.misc	     allbery@ncoast.org
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery@hal.cwru.edu
      Send comp.sources.misc submissions to comp-sources-misc@<backbone>
NCoast Public Access UN*X - (216) 781-6201, 300/1200/2400 baud, login: makeuser