Date: Thu, 17 Jun 2004 07:39:50 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/lib/libc/sys read.2 Message-ID: <20040617073321.Q1632@gamplex.bde.org> In-Reply-To: <200406161543.i5GFhYq7009877@khavrinen.lcs.mit.edu> References: <200406150124.i5F1Ofp9084012@repoman.freebsd.org> <20040616062409.GC20866@ip.net.ua> <200406161543.i5GFhYq7009877@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 16 Jun 2004, Garrett Wollman wrote:
> <<On Wed, 16 Jun 2004 09:24:09 +0300, Ruslan Ermilov <ru@FreeBSD.org> said:
>
> >> [I wrote:]
> >> Actually, it's {IOV_MAX}.
>
> > You mean you want it marked up like in POSIX, with curlies?
>
> I don't care that much about how it is marked up. The important point
> is that it is a configuration variable, not a constant. POSIX makes
> no guarantee:
>
> - that IOV_MAX will be defined as a preprocessor macro,
> - that sysconf(_SC_IOV_MAX) is time-invariant, or
> - that implementations will have any maximum at all.
>
> I have argued for a long time that such system parameters are due
> special markup. POSIX writes it {IOV_MAX}.
A macro for this would be good, since parameters like IOV_MAX should
be marked up even if they are non-POSIX constants, and changing the
markup would be easier than adding braces (something like s/Dv/Pv/).
Bruce
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040617073321.Q1632>