----- Original Message -----
From: "Jan Dubois" <[EMAIL PROTECTED]>
To: "'Sisyphus'" <[EMAIL PROTECTED]>; "'perl-win32-users'"
<[email protected]>
Sent: Tuesday, June 05, 2007 3:14 AM
Subject: RE: uselongdouble=undef in 64-bit build (why?)
> On Mon, 04 Jun 2007, Sisyphus wrote:
>> Just wondering why ActiveState's 64-bit build of perl has
>> "use64bitint=define" but "uselongdouble=undef".
>>
>> I have no doubt that there are good reasons - just wondering what they
>> are :-)
>
> The Microsoft compilers (both 32 and 64-bit) use the same 8-byte
> representation for the "double" and "long double" types. The C standard
> only requires that they are being treated as distinct types, but doesn't
> mandate that "long double" uses a higher precision than "double".
>
> I just verified that at least the 64-bit Platform SDK compilers still
> use 8 bytes for "long double" variables. Therefore defining
> uselongdouble would be pointless.
>
Does that mean it's impossible to build a 64-bit perl (using the 64-bit
Platform SDK compiler) where the NV provides greater precision than the IV ?
I see that $Config{longdblsize} reports '10'. Does that open a door to the
possibility of building a perl where the NV uses 10 bytes ?
Cheers,
Rob
_______________________________________________
Perl-Win32-Users mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
