On May 10, 2016, at 12:26 , Gilles Gouaillardet wrote:
except if you #include the libc header in your app, *and* your send function has a different prototype, I do not see how clang can issue a warning(except of course if clang "knows" all the libc subroutines ...)
not sure if that helps the OP, but for those who have it available: IBM xlc "knows" all the libc names and will warn (assuming the corresponding flags are set) even when not including the header in question. Expect to get warnings for things like parameters named index though.
Regards, Thomas
smime.p7s
Description: S/MIME cryptographic signature
