Date: Mon, 16 Feb 2004 14:35:23 -0500 (EST) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: David Schultz <das@FreeBSD.ORG> Cc: freebsd-standards@FreeBSD.ORG Subject: Re: writev(2) and IOV_MAX confusion Message-ID: <200402161935.i1GJZNfh046410@khavrinen.lcs.mit.edu> In-Reply-To: <20040216103254.GA7779@VARK.homeunix.com> References: <40309723.5020808@freebsd.org> <20040216103254.GA7779@VARK.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On Mon, 16 Feb 2004 02:32:54 -0800, David Schultz <das@FreeBSD.ORG> said:
> In POSIX, you get IOV_MAX only by including <limits.h>, and
> FreeBSD's <limits.h> includes <sys/syslimits.h>, so the code is
> correct here. As far as I can tell, the man page doesn't say
> anything about what you have to include to get IOV_MAX, but I
> suppose it could be more clear.
I have long advocated for support in -mdoc for POSIX's distinctive
{CONFIG_VAR} typograhpy to make it clear(er) what these variables are
(and incidentally not imply that they will always be defined).
-GAWollman
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200402161935.i1GJZNfh046410>