Date: Sat, 13 Apr 2002 18:13:33 +1000 From: "Tim J. Robbins" <tim@robbins.dropbear.id.au> To: "M. Warner Losh" <imp@village.org> Cc: freebsd-standards@FreeBSD.ORG Subject: Re: standards/36783 Message-ID: <20020413181333.A9914@treetop.robbins.dropbear.id.au> In-Reply-To: <20020412.220826.123419371.imp@village.org>; from imp@village.org on Fri, Apr 12, 2002 at 10:08:26PM -0600 References: <200204121639.g3CGdOZ90234@khavrinen.lcs.mit.edu> <20020412.121645.03985114.imp@village.org> <20020413135358.A9710@treetop.robbins.dropbear.id.au> <20020412.220826.123419371.imp@village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Apr 12, 2002 at 10:08:26PM -0600, M. Warner Losh wrote: > : What I'll do is leave the format string the same as for a double, and > : make a note explaining that it was working around a printf limitation. > : Thanks for the info. > > I don't understand this. You print doubles with %f and long doubles > with %Lf. Sorry for being unclear, I meant the hexdump pseudo-format string, and was mainly referring to the field width & precision it used. It starts of as %e in odsyntax.c then gets changed to %Le in parse.c when it sees it needs a 12-byte data type (long double). (It may seem like a hack, but it already does similar things to convert %x to %qx). Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-standards" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020413181333.A9914>