RE: Word of advice: Dont' close a socket you didn't create.

Ahh, yes, that would do it.

I generally do something like:
if ( socket != NULL )
   close (socket);

NULL in C/C++ being defined as 0 in my implementation.

I've never thought about the case where the socket number was actually 0,
and it's never come up, I had better double check my code and think about
socket number 0.

Regards,

Jim Langston

-----Original Message-----
From: David Gibbs [mailto:dgibbs@mks.com]

"Jim Langston" <jlangston@celsinc.com> wrote in message
4450A3C6B2D8F940821FB6B28A4D55FE230EC9@MAIL2.celsinc.com">news:4450A3C6B2D8F940821FB6B28A4D55FE230EC9@MAIL2.celsinc.com...
> How is it that you are closing socket 0 if you don't have a handle to it?

Apparently socket isn't really a handle ... it's *JUST* a number.  When my
program started, the int variable I use to hold the socket was initialized
to zero.  Before my program opened up a new connection, it tried to close
the current one (because it assumed the previous connection had been closed
by the other side).  Thus, my program would close socket 0.