In crypto/bio/b_sock.c, there's a call to getsockopt() that gets &size
as last argument. size is of type int, but according to X/Open, the
socket routines like getsockopt() shall get sizes with the type
size_t. On most systems, size_t is the same as "unsigned int", which
in pedantic mode (gcc -pedantic, or DEC C by default) will get you a
warning.
So, the question is, shall we go for X/Open standards? I think we
should. Question is how many compilers will break because of this.
Another solution would be to cast &size to (void *) <hawk, spit>...
Uhmmm, actually haven't tested that yet, I'll come back on it...
--
Richard Levitte \ Spannv�gen 38, II \ [EMAIL PROTECTED]
Redakteur@Stacken \ S-161 43 BROMMA \ T: +46-8-26 52 47
\ SWEDEN \ or +46-708-26 53 44
Procurator Odiosus Ex Infernis -- [EMAIL PROTECTED]
Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
