> This is yet another manifestation of the LastError problems I reported
> a few months ago (in response to someone else's difficulties like
> this). Quite frankly, I think that is by far the most serious problem
> (set of problems, actually) that Synapse has.
>
> I just ran through this quickly (don't have time for more), using the
> httpserv demo code, but this is what I see:
>
> You actually DO get an ACCURATE 10048 error ("Specified address
> already in use") inside the TBlockSocket.Bind() method (in
> SockCheck(Bind(FSocket, Sin)) call I think), which later, if not
> RaiseExcept, gets improperly translated into 10022--Invalid Argument;
> BUT THEN the next CanRead() call resets LastError back to 0 (in
> TBlockSocket.SockCheck(). So the next ExceptCheck() call doesn't see
> ANY error at all.
This is not true!
When you call 'bind' in server code, then it do just BIND and nothing
else! There is not any placa for any canread or others what can
replace error message.
If Bind call failed, then it dirrectly setting Lasterror and it not
calling nothing what can reset this value.
--
Lukas Gebauer.
E-mail: [EMAIL PROTECTED]
http://synapse.ararat.cz/ - Ararat Synapse - TCP/IP Lib.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
synalist-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synalist-public
