Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!mips!zaphod.mps.ohio-state.edu!rpi!batcomputer!cornell!rochester!kodak!ispd-newsserver!sydorow
From: sydorow@bisco.kodak.com (Steve Sydorowicz)
Newsgroups: comp.windows.x
Subject: X I/O Errors
Message-ID: <1991Apr17.205355.16190@ssd.kodak.com>
Date: 17 Apr 91 20:53:55 GMT
Sender: news@ssd.kodak.com
Organization: Eastman Kodak
Lines: 17


    Could someone "in the know" summarize the reasons for using the
compile-time defines of EWOULDBLOCK/EMSGSIZE when making
the X11R4 release? My curiosity relates to _XFlush() and the possible
errors returned from WriteToServer(). I have an application that works
well on SUN 3/80 systems, but seems to have occasional problems on
Sparcs. I suspect that there is some difference in file buffers or
something, and was curious as to the reasoning of "ifdefing"
in the _XFlush code.

                      Thanks much,
                      Steve
-- 
--------------------------------------------------------------------------------
Stephen J. Sydorowicz                                 Azatar Computer Systems
REPLY TO: sydorow@bisco.kodak.com                     (716)726-5636
		Opinions expressed do not reflect those of my employer