From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=0.7 required=5.0 tests=BAYES_00,INVALID_DATE,
	MSGID_SHORT,REPLYTO_WITHOUT_TO_CC autolearn=no autolearn_force=no
	version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sun-barr!apple!uokmax!munnari.oz.au!sirius.ucs.adelaide.edu.au!chook!bradley
From: bradley@chook.adelaide.edu.au (Bradley Schmerl)
Newsgroups: comp.lang.ada
Subject: Ada and Unix Sockets
Keywords: sockets unix blocking
Message-ID: <1873@sirius.ucs.adelaide.edu.au>
Date: 19 Nov 90 04:15:03 GMT
Sender: news@ucs.adelaide.edu.au
Reply-To: bradley@chook.adelaide.edu.au (Bradley Schmerl)
Organization: Adelaide University Computer Science Department
Nntp-Posting-Host: chook.ua.oz.au
List-Id: <comp.lang.ada>


Greetings,

	I am writing a program in Ada which uses a blend of X events and socket
communication with other ada programs. I am running into a problem doing this,
because when a call is made to wait for a socket (or get the next X Event), the
whole Ada program (only one Unix process) blocks, and so other tasks don't 
continue running. Is there any way of overcoming this problem, apart from using
a busy loop to continually poll for events?

	Oh, I am using Verdix Ada 5.5 on an Encore MultiMax under Unix.

	Could you also e-mail me directly, as I don't read this newsgroup 
often.

Bradley.
--
bradley@cs.adelaide.edu.au