Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!think!snorkelwacker!apple!sun-barr!newstop!sun!kimba!hvr
From: hvr@kimba.Sun.COM (Heather Rose)
Newsgroups: comp.windows.x
Subject: Re: Forcing application to process events
Message-ID: <131911@sun.Eng.Sun.COM>
Date: 16 Feb 90 00:40:25 GMT
References: <9002011609.AA05640@ATHENA.MIT.EDU> <2654@bacchus.dec.com> <131133@sun.Eng.Sun.COM> <1647@acorn.co.uk>
Sender: news@sun.Eng.Sun.COM
Reply-To: hvr@sun.UUCP (Heather Rose)
Organization: Sun Microsystems, Mountain View
Lines: 13

In article <1647@acorn.co.uk> steve@acorn.UUCP (Steve "daffy" Hunt) writes:
>In article <131133@sun.Eng.Sun.COM> hvr@sun.UUCP (Heather Rose) writes:
>>3.  Use the XView toolkit.  The XView notifier supplies a function which
>>is tailored to your needs, notify_do_dispatch().  
>
>Yes, but what a shame Sun did not try to write it portably.  I am
>referring to the very dubious technique of redefining syscall wrappers
>for read, select (and something else) and then using some parochial
>method for accessing the 'real' syscalls.  Wacky.

We're working on making it portable.  Suggestions/fixes welcome ;-)

Heather