Re: Exasperated with 64-bit integer builds of perl

You'll get more salutary results if you build a perl that uses long doubles too.

The whole preserve-results-as-an-integer is something of a bandaid - there are places it covers and places it doesn't.

The "design" is that pretty much any conversion or operation result in a floating point value. Doing anything else is the result of trying to make things "just work" after the fact.

Comment on Re: Exasperated with 64-bit integer builds of perl

Replies are listed 'Best First'.
Re^2: Exasperated with 64-bit integer builds of perl (long double) by tye (Sage) on May 28, 2007 at 16:52 UTC
build a perl that uses long doubles too Yes, it becomes very difficult to always pick the right choice when you build things such that some numbers only fit in IVs and some only fit in NVs. Perl has a long history of all IVs also fitting into NVs and trying to fight both that history and expecting some magical perfection in Perl opcodes being able to predict whether the results should be calculated as an IV or an NV is going to lead to disappointment. - tye	[reply]

Replies are listed 'Best First'.

Re^2: Exasperated with 64-bit integer builds of perl (long double)
by tye (Sage) on May 28, 2007 at 16:52 UTC

build a perl that uses long doubles too

Yes, it becomes very difficult to always pick the right choice when you build things such that some numbers only fit in IVs and some only fit in NVs. Perl has a long history of all IVs also fitting into NVs and trying to fight both that history and expecting some magical perfection in Perl opcodes being able to predict whether the results should be calculated as an IV or an NV is going to lead to disappointment.

- tye

[reply]