realbasic-nug
[Top] [All Lists]

Re: Socket error code 22 - what is that?!

To: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Subject: Re: Socket error code 22 - what is that?!
From: Charles Yeomans <charles@declareSub.com>
Date: Thu, 26 Feb 2009 13:23:08 -0500
Authentication-results: mx.google.com; spf=neutral (google.com: 74.124.194.228 is neither permitted nor denied by best guess record for domain of realbasic-nug-bounces@lists.realsoftware.com) smtp.mail=realbasic-nug-bounces@lists.realsoftware.com
Delivered-to: listarchive@realsoftware.com
In-reply-to: <89fe53800902260948i1946e2a0nc4cbe8cb5324570f@mail.gmail.com>
References: <89fe53800902260948i1946e2a0nc4cbe8cb5324570f@mail.gmail.com>
Reply-to: REALbasic NUG <realbasic-nug@lists.realsoftware.com>
Sender: realbasic-nug-bounces@lists.realsoftware.com

On Feb 26, 2009, at 12:48 PM, Thomas Tempelmann wrote:

I'm getting the error code 22 from a TCPSocket, on OS X.

The SocketCore documentation lists only codes from 100 to 108. It
can't be a OSX-provided code because those are all negative, AFAIK.

So, is this a bug, or doc error, or what shall I make of it? And who
knows what this code means?


I wrote the following crap last year:


"Probably it's

#define EINVAL          22              /* Invalid argument */

from /usr/include/sys/errno.h .

You might see this if you call TCPSocket.Write on a socket that has been disconnected.

Note that calling TCPSocket.Write on a socket that has never been connected will not result in an error. Instead it appears that the data is buffered until a connection is established."

Charles Yeomans

_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>


<Prev in Thread] Current Thread [Next in Thread>