Date: Wed, 20 Jun 2007 13:07:10 +0200 From: Stefan Farfeleder <stefan@fafoe.narf.at> To: Daniel Eischen <deischen@freebsd.org> Cc: current@freebsd.org Subject: Re: Multicast problems [PATCH] Message-ID: <20070620110702.GB929@lizard.fafoe.narf.at> In-Reply-To: <Pine.GSO.4.64.0706191823040.1099@sea.ntplx.net> References: <E1I0E3b-0000kk-Ky@clue.co.za> <46765CB9.9020105@incunabulum.net> <Pine.GSO.4.64.0706180833080.23884@sea.ntplx.net> <4676C30E.7040300@incunabulum.net> <Pine.GSO.4.64.0706181344060.24865@sea.ntplx.net> <4676C952.5000607@incunabulum.net> <4676D168.3050502@incunabulum.net> <4678529A.3080308@incunabulum.net> <Pine.GSO.4.64.0706191823040.1099@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 19, 2007 at 06:36:39PM -0400, Daniel Eischen wrote: > POSIX states that: > > o The <sys/socket.h> header shall define the type socklen_t, > which is an integer type of width of at least 32 bits; see > APPLICATION USAGE. > > and goes on to state: > > o The <sys/socket.h> header shall define the unsigned integer > type sa_family_t. > > This seems to imply that our socklen_t should not be an unsigned > integer (uint32_t), but a signed integer. In APPLICATION USAGE, > POSIX states: I don't understand how you come to that conclusion. Why does not mentioning whether socklen_t is signed or unsigned imply it should be signed? > > To forestall portability problems, it is recommended that > applications not use values larger than 23^1 -1 for the > socklen_t type. That just means that those values will wrap to negative values if socklen_t is a signed integer type.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070620110702.GB929>