Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!wuarchive!texbell!texsun!newstop!sun!kimba!hvr
From: hvr@kimba.Sun.COM (Heather Rose)
Newsgroups: comp.windows.x
Subject: Re: X & signals
Keywords: xwindows signals, XView
Message-ID: <132613@sun.Eng.Sun.COM>
Date: 7 Mar 90 04:04:28 GMT
References: <1154@sdrc.UUCP> <132200@sun.Eng.Sun.COM> <2888@bacchus.dec.com>
Sender: news@sun.Eng.Sun.COM
Reply-To: hvr@sun.UUCP (Heather Rose)
Organization: Sun Microsystems, Mountain View
Lines: 21

In article <2888@bacchus.dec.com> asente@decwrl.dec.com (Paul Asente) writes:
>In article <132200@sun.Eng.Sun.COM> argv@sun.UUCP (Dan Heller) writes:
>>The problem is that Xlib has no layer for signal handling.  The
>>reason is dubious, but it's in many people's opinion that it's
>>due to DEC's strong involvement with X and since DEC really likes
>>VMS (brought to the US on one of Columbus' ships circa 1492) and
>>VMS does not support signals...
>
>That's a pretty dubious explanation.  Try
>1) Xlib version 11 is still rather similar internally to Xlib version 10,
>which DEC had nothing to do with, and which didn't support signals either.
>2) The developers of X11 had a huge amount of stuff on their plates as
>it was, and putting signal handling in Xlib was one of the 143 things they
>would have liked to have done but didn't have time for.

This is very true...as anyone who has looked at the XView notifier code
will tell you ;-)

Regards,

Heather