Archived

This topic is now archived and is closed to further replies.

Winsock and custom wrapper class.

This topic is 5752 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

Lets say I have a class which wraps the Winsock API...
class cSocket
{
private:
   SOCKET sock;
public:
   // A few methods here...

   void closeSocket()
   {
      shutdown(sock);
      closesocket(sock);
   }
};
 
Now in my app some where...
cSocket sock1;
cSocket sock2;

// Initialize sock1 here and connect

sock2 = sock1; // <-- Make a copy...

// Do stuff here...

sock2.closeSocket();
 
Will sock2.closeSocket close the socket and free the resources correctly?

Share this post


Link to post
Share on other sites
Guest Anonymous Poster
Yes....but, remember that sock2 and sock1 are using the same socket/file descriptor, so if you copy sock1 to sock2, and then closesocket() on sock2, it will also invalidate sock1''s socket....I think that may have been what you were getting at anyway.

Share this post


Link to post
Share on other sites