Date: Wed, 24 Oct 2001 15:36:58 -0400 (EDT) From: Garrett Wollman <wollman@khavrinen.lcs.mit.edu> To: Dag-Erling Smorgrav <des@ofug.org> Cc: arch@FreeBSD.org Subject: Re: "types" man page Message-ID: <200110241936.f9OJaws46582@khavrinen.lcs.mit.edu> In-Reply-To: <xzpn12gyhxv.fsf@flood.ping.uio.no> References: <200110241902.f9OJ2vA46197@khavrinen.lcs.mit.edu> <xzpn12gyhxv.fsf@flood.ping.uio.no>
next in thread | previous in thread | raw e-mail | index | archive | help
<<On 24 Oct 2001 21:08:28 +0200, Dag-Erling Smorgrav <des@ofug.org> said: > Our printf(3) man page does not mention a 'j' conversion specifier, > and I don't have a copy of C99 at hand. I suppose it's a C99 thing? > Does our printf(3) (and our printf(9)) support it? I have patches for printf(3), which were posted to the freebsd-standards list; I haven't even looked at the kernel printf, but the changes would be fairly similar. The other new C99 modifiers are `r' (for ptrdiff_t) and `z' (for size_t). C99 also adds the `a' conversion for floating-point numbers, and POSIX/SUS adds the `'' (single close quote) modifier to print using thousands-separators; neither of these are likely to be useful in the kernel. The advice for 4.x should probably say to use `long' almost all the time, except for those types which are documented as `might be longer than long'. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200110241936.f9OJaws46582>