Re: RFC3678: header incompatibility

>       there is no guarantee that
>       <sys/socket.h> is included prior to <netinet/in.h>, and it is not
>       possible for <netinet/in.h> to blindly include <sys/socket.h>.
Why not?  POSIX seems to anticipate this:

> Inclusion of the <netinet/in.h> header may also make visible all symbols
> from <inttypes.h> and <sys/socket.h>.
  Bill

_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf