Path: utzoo!attcan!uunet!cs.utexas.edu!usc!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: XIOErrorHandler
Message-ID: <8910161324.AA02566@expire.lcs.mit.edu>
Date: 16 Oct 89 13:24:21 GMT
References: <100689.093908.dan@watson.ibm.com>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 12


    Is this an IBM problem, or is it a genetic defect?

It is a genetic defect in Unix, not X.

    I can get around the problem by saying
    "signal(SIGPIPE, SIG_IGN);" in my application, but I think this call
    should be in Xlib.

Sorry, I have to disagree.  Signals are a scarce resource, and SIGPIPE
might be used/handled by the application for other reasons.  Having Xlib
step on the signal handler would be a significant incompatible change.