We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SetPort() and GetPort() in cip.h directly handles the value of struct sockaddr_in. https://github.com/LX3JL/xlxd/blob/master/src/cip.h#L51 https://github.com/LX3JL/xlxd/blob/master/src/cip.h#L54
CUdpSocket::Open() stores uiPort value via htons(). https://github.com/LX3JL/xlxd/blob/master/src/cudpsocket.cpp#L64
Is there any reason to omit htons()?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
SetPort() and GetPort() in cip.h directly handles the value of struct sockaddr_in.
https://github.com/LX3JL/xlxd/blob/master/src/cip.h#L51
https://github.com/LX3JL/xlxd/blob/master/src/cip.h#L54
CUdpSocket::Open() stores uiPort value via htons().
https://github.com/LX3JL/xlxd/blob/master/src/cudpsocket.cpp#L64
Is there any reason to omit htons()?
The text was updated successfully, but these errors were encountered: