Re: [Mingw-users] Minor patch for winsock/winsock2

[Michael G. <mg...@te...>]

Hi Aaron !

> How did you manage to get GCC to issue a warning for this, anyway? I 
> can't get either MinGW's GCC 3.4.3 or FSF's GCC mainline to emit a
> diagnostic for this with any combination of options.

On linux this is because FD_SET is mapped to __FD_SET (in bits/select.h)
which uses inline assembler.

On Windows I'm getting this with -Wsign-compare...however:

After further investigation as to what happens I now know the true
reason for me getting said warning:
The code in question contains some legacy code originating from some
big third party company which redefines SOCKET to being signed.
The whole situation is a bit more complicated and somewhat convoluted
but the net effect is SOCKET being signed (and _THAT_ triggers said
warning).

I apologize for not having investigated that earlier.

Therefor the whole discussion is moot and I will have to reevaluate
some of my earlier statements.

I also will reevaluate my position w/r to signed/unsigned in general.

Last not least I'd like to thank you for helping me getting a better
understanding of the mechanics involved.

Best,
Michael
-- 
 Vote against SPAM - see http://www.politik-digital.de/spam/
 Michael Gerdau       email: mg...@te...
 GPG-keys available on request or at public keyserver