Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!texbell!texsun!newstop!sun!kimba!hvr
From: hvr@kimba.Sun.COM (Heather Rose)
Newsgroups: comp.windows.x
Subject: Re: X & Signals
Message-ID: <132766@sun.Eng.Sun.COM>
Date: 9 Mar 90 23:23:43 GMT
References: <9003052147.AA25962@expo.lcs.mit.edu>
Sender: news@sun.Eng.Sun.COM
Reply-To: hvr@sun.UUCP (Heather Rose)
Organization: Sun Microsystems, Mountain View
Lines: 21

In article <9003052147.AA25962@expo.lcs.mit.edu> PARCEL@INTELLICORP.COM (Scott Parcel) writes:
>
>Our need to process events within a signal handler comes from the following
>constaints:
>   1.  Arbitrary, mostly unconstrained and uncooperative code may be running
>       within the same process as our X code.  
>   2.  We want to handle any x events that occur even while this arbitrary
>       code is running.
>   3.  We do not believe that it is practical to separate our X code into
>       a separate process.
>I know this is considered a bad idea, however I am very familiar with writing
>event driven code and multiprocess applications and it does not appear that
>these solutions will do the trick this time.  I am presently looking into
>how to detect having interupted nonreentrant system library calls.

Take a look at the XView notify code.  It sounds to me that this is just
what you're looking for.  <X11R4>/contrib/toolkits/XView/lib/libxvin/notify.

Regards,

Heather