Avoiding longjmp

[Brandon S. Allbery]

As quoted from <29105 at ucbvax.BERKELEY.EDU> by jas at ernie.Berkeley.EDU (Jim Shankland):
+---------------
| In article <13624 at ncoast.ORG> allbery at ncoast.ORG (Brandon S. Allbery) writes:
| >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.
| 
| At the risk of getting into a "dessert topping/floor wax" argument:
| the proper method for dealing with asynchronous signals is light-weight
| processes (a.k.a. threads).  Forget signal handlers altogether:  you
+---------------

Good point.  Let me modify my assertion to "the proper method of dealing
with asynchronous signals *when lightweight processes are not available*".
I'm not talking about Mach; I'm talking about the rest of us.

++Brandon
-- 
Brandon S. Allbery, moderator of comp.sources.misc	     allbery at ncoast.org
uunet!hal.cwru.edu!ncoast!allbery		    ncoast!allbery at 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