🚀 go-pugleaf

In article bruniau@cenatls.cena.dgac.fr (Christophe Bruniau) writes:
>|> 
>|> > and Why X libraries are not reentrant?,
>|> 
>|> Because it's a lot of work and nobody's been willing to do it.
>|> 
>
>At this point, there is an interesting question:
> How does one address the problem of handling interrupts (for instance Unix
> Signals) involving X Window actions in a sequential language like C ?

Isn't this in the FAQ yet?

One (perhaps inelegant) solution involves opening a pipe and write() to
the pipe in the signal handler.  Write is re-entrant.

You can then select() for read on both the pipe and your Display connection 
and safely perform your "signal triggered" routine upon receipt of data on 
the pipe.

>An example of such a problem is when one wants to process data from a network
> while computing the MainLoop. Is the interleaving of busy waiting of Network
> data and X events the only solution ?

Network data?  In Xlib, select() on both the Display connection and the 
network data connection.  In Xt, use XtAppAddInput().

-- 

Kaleb Keithley                               kaleb@jpl-devvax.jpl.nasa.gov