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.8 required=5.0 tests=BAYES_00,URI_HEX autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c6c265459ff33db7,start X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-29 05:28:38 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!syros.belnet.be!news.belnet.be!feed.news.nacamar.de!fu-berlin.de!uni-berlin.de!69116-cm.able.ES!not-for-mail From: Jano Newsgroups: comp.lang.ada Subject: Gnat.Sockets and non-blocking connects Date: Sun, 29 Jun 2003 14:26:48 +0200 Message-ID: NNTP-Posting-Host: 69116-cm.able.es (212.97.169.116) X-Trace: fu-berlin.de 1056889717 32020835 212.97.169.116 (16 [49872]) X-Newsreader: MicroPlanet Gravity v2.50 Xref: archiver1.google.com comp.lang.ada:39885 Date: 2003-06-29T14:26:48+02:00 List-Id: Hello! I posted some time ago about non-blocking connects, and all went well. However, I have faced a new necessity I'm not sure how to address. I'm trying to determine if a asynchronous connect has failed. When it ends successfully, I detect it with a select checking for writeability. However, it seems I must check the exception set to detect failure. The problem is that Gnat.Sockets doesn't implement the exception selector in its Select. Any workarounds? I can't figure one right now. TIA, -- ------------------------- Jano 402450.at.cepsz.unizar.es -------------------------