Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!mcgill-vision!bloom-beacon!dawn.crd.ge.COM!stpeters
From: stpeters@dawn.crd.ge.COM (Dick St.Peters)
Newsgroups: comp.windows.x
Subject: Re: Forcing application to process events
Message-ID: <9002151623.AA19195@dawn.crd.Ge.Com>
Date: 15 Feb 90 16:23:45 GMT
Sender: daemon@athena.mit.edu (Mr Background)
Organization: The Internet
Lines: 21

(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.

That "parochial" method is available on Ultrix machines, Masscomps,
and even under Eunice, the Wollongong UNIX emulation for VMS.  What a
shame some vendors don't provide it.

What would you have Sun do?  Rewrite everyone's OS?  I'll bet this
method is available in SysVR4 :-)

--
Dick St.Peters, GE Corporate R&D, Schenectady, NY
stpeters@dawn.crd.ge.com	uunet!dawn.crd.ge.com!stpeters