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.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,c6c265459ff33db7 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2003-06-29 06:42:20 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!newsfeed.icl.net!newsfeed.fjserv.net!feed.news.nacamar.de!news.belwue.de!news.uni-stuttgart.de!news.enyo.de!not-for-mail From: Florian Weimer Newsgroups: comp.lang.ada Subject: Re: Gnat.Sockets and non-blocking connects Date: Sun, 29 Jun 2003 15:42:19 +0200 Message-ID: <87he69j8zo.fsf@deneb.enyo.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: albireo.enyo.de 1056894139 12147 212.9.189.171 (29 Jun 2003 13:42:19 GMT) X-Complaints-To: Cancel-Lock: sha1:qKcvI2QEAwnA26L/XUyK9r4xQzA= Xref: archiver1.google.com comp.lang.ada:39886 Date: 2003-06-29T15:42:19+02:00 List-Id: Jano writes: > 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. No, this is a misunderstanding. The exception set is not for error reporting, but for exceptional situations. Errors are reported by the R/W selectors. However, nonblocking connect error reporting is not portable, see Steven's UNIX Network Programming.