Ytukyg

Is it possible to get rid of compiler warnings trying to cast from SOCKET to int or from size_t to int using winsock2 functions like sendto, select etc? May there is a common approach? (Windows, MSVC15)

example:

C4267 conversion from 'size_t' to 'int', possible loss of data:

sendto(_socket, managedPtr, _bufferSize, NULL, PSOCKADDR(&_sockaddr), sizeof(_sockaddr))
____________________________________________________________~~~~~~~~~~~~~~

C4244 conversion from 'SOCKET' to 'int', possible loss of data:

select(_socket + 1, &readfds, nullptr, nullptr, GetTV())

_______~~~~~~~~~______________________________________

sendTo: The compiler possibly warns you about this, because you try to build a 64 bit application. Thus, size_t would be a 64 bit wide type and int would be 32 bit at most. To resolve this try to cast the result explicitely to an int so the compiler knows this was intended. Also this function may be replaced by send as read here MSDN "The sendto function is normally used on a connectionless socket to send a datagram to a specific peer socket identified by the to parameter. Even if the connectionless socket has been previously connected to a specific address, the to parameter overrides the destination address for that particular datagram only. On a connection-oriented socket, the to and tolen parameters are ignored, making sendto equivalent to send." so maybe check that too.

select: as MSDN states the first parameter is ignored but kept as compatibility to berkeley sockets. Apparently Microsoft wanted to provide easy code portability to UNIX systems and thus designed its API to fit the POSIX standard so code can almost just be copy pasted (with some slight changes obviously) Read more here. So if you use winsock2 Ignore this parameter and set it to 0 or whatever integer. If you want to port your App, copy your code and pass a file descriptor of a socket instead of 0.

Yes, it's possible:

SOCKET s;

int i = static_cast<int>(s);

For the functions taking an int just make sure your value isn't > std::numeric_limits<int>::max() and it should be ok to do static_cast<int>(value).

sendto(_socket, managedPtr, _bufferSize, NULL,

       &_sockaddr, static_cast<int>(sizeof(_sockaddr)));



select(static_cast<int>(_socket)+1, ...); // the nfds parameter is ignored on Windows