🚀 go-pugleaf

Remy Lebeau (TeamB) wrote:
> "Stormy" <s70rmy@hotmail.com> wrote in message
> news:434fa1c3@newsgroups.borland.com...
>
>> Unfortunately, this is the case where exception is thrown
>> before OnError event occurs...
>
> That bug was already fixed in BCB6.  The lookup error triggers the
> OnError event before throwing the exception.

Tried recompiling my code with BCB6 today and got same result. Well, not
entirely... Exception does not get thrown before OnError event any more,
(and you can supress it by resetting error code to 0 in OnError event) but
if you try to connect TClientSocket to server that doesn't exist, OnError
event gets triggered with error code #11001. OK. Now if you try to connect
same socket to server that does exist and is running, OnError event gets
triggered again (for some reason unknown to me) with error #10049. If you
try connecting it to same server again, OnRead event gets triggered
(finally!) and everything seems fine. I dont understand why #11001 and
#10049 have to come in pairs.?. VCL, winsock, bug, feature, standard???
*Confused*.