Date: Wed, 16 Jun 2004 20:47:37 +0300 From: Ruslan Ermilov <ru@FreeBSD.org> To: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> Cc: doc@FreeBSD.org Subject: Re: cvs commit: src/lib/libc/sys read.2 Message-ID: <20040616174737.GA25398@ip.net.ua> In-Reply-To: <200406161543.i5GFhYq7009877@khavrinen.lcs.mit.edu> References: <200406150124.i5F1Ofp9084012@repoman.freebsd.org> <200406151522.i5FFMeIc001885@khavrinen.lcs.mit.edu> <20040616062409.GC20866@ip.net.ua> <200406161543.i5GFhYq7009877@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--pf9I7BMVVzbSWLtt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 16, 2004 at 11:43:34AM -0400, Garrett Wollman wrote: > <<On Wed, 16 Jun 2004 09:24:09 +0300, Ruslan Ermilov <ru@FreeBSD.org> sai= d: >=20 > >> [I wrote:] > >> Actually, it's {IOV_MAX}. >=20 > > You mean you want it marked up like in POSIX, with curlies? >=20 > 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: >=20 > - 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. >=20 > I have argued for a long time that such system parameters are due > special markup. POSIX writes it {IOV_MAX}. >=20 But FreeBSD *is* the implementation, and in this implementation IOV_MAX is the #define. Does that make sense? Cheers, --=20 Ruslan Ermilov ru@FreeBSD.org FreeBSD committer --pf9I7BMVVzbSWLtt Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFA0Ie5qRfpzJluFF4RAjZaAJ0dGBIvKsboiLxesbpaUtKvVWgwqACeOs/t sQcIMczMFBjo0RfMC5e2OoE= =E+Ji -----END PGP SIGNATURE----- --pf9I7BMVVzbSWLtt--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040616174737.GA25398>