🚀 go-pugleaf

"Vladimir Stefanovic" <spam@not.needed> wrote in message
news:419cf046@newsgroups.borland.com...

> Remy, I havent seen this line before when dealing with sockets.

It only applies to non-blocking sockets, which TClientSocket and
TServerSocket are set it by default.  You should always check for
WSAEWOULDBLOCK when Send/ReceiveBuf() return -1.  -1 means that a socket
error occured, but WSAEWOULDBLOCK is a recoverable error.  It simply means
that no data could be transferred at that moment because it would cause
Send/ReceiveBuf() to block the caller for any length of time, which is not
allowed for non-blocking socket.  You simply call Send/ReceiveBuf() again
with the same parameters until the call finally succeeds without blocking,
or until a true error occcurs.

> In comparison, in such cases I usually did
'Application->ProcessMessages()'
> followed by 'continue', but obviously in that case I have no error
checking.

No, you do not.  And besides, calling ProcessMessages() can produce
side-effects anyway.

> Should I replace my code with this you have shown?

That is your choice.

> Really, is there any difference for compiler if __fastcall is missed?

If a function has parameters, then __fastcall is slightly faster in most
cases since the first few parameters are usually passed via CPU registers
instead of on the stack.


Gambit