Jump to content

  • Log In with Google      Sign In   
  • Create Account


Member Since 15 Dec 2012
Offline Last Active Dec 23 2012 01:31 AM

Topics I've Started

CHandle Wrapper overloaded operator help

23 December 2012 - 01:03 AM

say i have the following wrapper class
Class CHandle
how would i make an overloaded operator that will return the address of m_h member so that i can mimic the following api function
so that mine can be used like so..
CHandle h;

Winsock Simple Class Advice

15 December 2012 - 05:39 PM

I wanted to make a simple wrapper class around winsock that programmers could use in order to obtain information about a certain host. The programmer can easily do the following with my wrapper class.

[source lang="cpp"]int main(){CHostInfo hostInfo;// winsock initializeif (hostInfo.Initialize() == false){ // initialization of winsock failed return -1;}// obtain host information using winsockLPHOSTENT lpHostEnt = hostInfo.GetHostInfo("www.google.com");if ( lpHostEnt == NULL ){ // winsock failed to obtain host information return -1;}return 0;}[/source]

My class hides the details of winsock initialization and other function behind the scenes and avoids users from the details of Winsock. I'm not quite sure on the recommended method for returning error information to the caller of my wrappers functions. ATM i simply return bool for success and failure. I would like to return the WSAGetLastError() code instead. Does anyone have any recommended advice on the approach i should take?

Methods i thought of
1.) Simply have a variable in the class that holds the error code
2.) Simply have a function that calls WSAGetLastError() like so

int CHostInfo::GetWinSockError()
return WSAGetLastError();

I know the above are valid options but not sure if one is better then the other or if any other better methods exist

In summary, What method is recommended in order to shield users from the WINSOCK API and use my wrapper class API and yet still get valuable information back when an error occurs in the winsock functions? thanks!