[comp.windows.x] select

pinkas@hobbit.intel.com (Israel Pinkas ~) (04/10/89)

One of our users is writing an application that uses pipes to start up
other processes.  (Similar to what xterm does.)  He is concerned about
getting the subprocess output and X events.  He does not want to "busy
wait", but is not sure what else to do.  He currently adds the file
descriptor returned by the dpyno() macro to the select call, but is worried
that this is not portable.  The O'Reilly books state that this is OK on
Unix, but what about other OS's?  Does it actually work on all flavors of
Unix?

E-Mail replies, I'll summarize.

-Israel Pinkas
--
--------------------------------------
Disclaimer: The above are my personal opinions, and in no way represent
the opinions of Intel Corporation.  In no way should the above be taken
to be a statement of Intel.

UUCP:	{amdcad,decwrl,hplabs,oliveb,pur-ee,qantel}!intelca!mipos3!cadev4!pinkas
ARPA:	pinkas%cadev4.intel.com@relay.cs.net
CSNET:	pinkas@cadev4.intel.com

beirne@richsun.UUCP (Michael G. Beirne) (11/01/89)

Hello,
Several programs running under X11R3, like kaleid and xemacs,
use the select system call, which does not return after the expected
timeout. I have a VAXstation II/GPX running Ultrix 2.2-1. The X server
is the one from the distribution X11R3 MIT source. 

Does anyone know of a work around/fix for this?

I just obtained the workstation a few weeks ago and have not been
a regular reader of either group, so if this has been gone over before
I'm sorry.

Michael G. Beirne
beirne@richp1.UUCP or beirne@richsun.reuter.com