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=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID
	autolearn=no autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,af2ede15fd2320cb,start
X-Google-Attributes: gid103376,public
From: "Marc A. Criley" <marc.a.criley@lmco.com>
Subject: Socket programming in Ada
Date: 2000/05/05
Message-ID: <3912C128.1CB6E348@lmco.com>#1/1
X-Deja-AN: 619557805
Content-Transfer-Encoding: 7bit
X-Accept-Language: en
Content-Type: text/plain; charset=us-ascii
X-Complaints-To: usenet@news.vf.lmco.com
X-Trace: knight.vf.lmco.com 957529629 317 166.17.131.243 (5 May 2000 12:27:09
 GMT)
Organization: Lockheed Martin M&DS
Mime-Version: 1.0
NNTP-Posting-Date: 5 May 2000 12:27:09 GMT
Newsgroups: comp.lang.ada
Date: 2000-05-05T12:27:09+00:00
List-Id: <comp.lang.ada>

Are there any bindings and examples of using the select() socket
monitoring function within an Ada program?

The old PARADISE packages provides such a binding, but that all is
pretty heavyweight and was never updated for Ada 95.  (It still defines
its own C interface types and such.)

The AdaSockets packages are very nice and work well, but select() is not
part of them.

If there's nothing readily available, I'll crank through it myself, but
I'd like to leverage off previous work if possible.  I also have to take
into account that the socket monitoring code would be embedded within a
task, so one might have to worry about signals associated with all this
as well--I've had to worry about that in the past when porting PARADISE
from one platform to another.

Marc A. Criley