Re: [9fans] libfmt/libutf and long double

[David Presotto <presotto@closedmind.org>]

[-- Attachment #1: Type: text/plain, Size: 176 bytes --]

On plan 9 double and long double are the same.  Therefore, the
fact that the libfmt library ignores the ll part of the %llE
doesn't break anything on plan 9 but does on Unix.

[-- Attachment #2: Type: message/rfc822, Size: 3274 bytes --]

From: suspect@suspicious.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] libfmt/libutf and long double
Date: Wed, 31 Dec 2003 13:43:31 -0500
Message-ID: <3B0EB7C6-3BC1-11D8-906F-000A95C53D8A@suspicious.org>

Hello,

Actually, my curiosity was about why it worked on my
Plan 9 machine but gave the strange behavior when
using libfmt on a UNIX system.

 From http://www.cs.bell-labs.com/magic/man2html/2/fprintf:
	"... or an optional L specifying that a following e, E, f, g,
	or G conversion specifier applies to a long double argument."

The above made it make sense to me that it worked on
my Plan 9 machine. I'm therefore a bit confused by your
response. Thanks.


cheers,


On Dec 31, 2003, at 11:17 AM, Russ Cox wrote:
>
> yes, plan 9 doesn't implement long double and your unix does.
>




>> Hello,
>>
>> I've run into a behavior with libfmt/libutf on UNIX system
>> that does not seem intuitive:
>>
>> 	long double ldv = 3.3;
>> 	print("long double var = %llE\n", ldv);
>>
>> gives:
>> 	long double var = -6.257775E+92
>>
>> Identical code under Plan 9 gives the expected output of:
>>
>> 	long double var = 3.300000E+00
>>
>> Is there any particular reason why the behaviors should
>> differ in this manner  ?