in reply to Re: Numeric overloading with 64-bit Perl
in thread Numeric overloading with 64-bit Perl

No, it is not the result of number-to-string conversion. Consider the following: 
my $x = 100000000000000;
for my $ii (14..25) {
    print("10^$ii: ", 0 + $x, "\n");
    $x *= 10;
}

[download]
which outputs: 
10^14: 100000000000000
10^15: 1000000000000000
10^16: 10000000000000000
10^17: 100000000000000000
10^18: 1000000000000000000
10^19: 10000000000000000000
10^20: 1e+20
10^21: 1e+21
10^22: 1e+22
10^23: 1e+23
10^24: 1e+24
10^25: 1e+25
This shows that Perl can output 20-digit integers, and verifies that the integer return value is being coerced into a floating-point result by the overload handling code.

Remember: There's always one more bug.

Replies are listed 'Best First'.
Re^3: Numeric overloading with 64-bit Perl
by tonyc (Hermit) on Oct 07, 2005 at 00:51 UTC

    You're right. Sorry for the assumption.

    I think I see the cause of the problem. If you look at pp_add (pp_hot.c) you'll see that it checks for the IV and UV flags on the scalar (SvIOK, SvUOK) and since neither of these is set it falls through to do the arithmetic with NVs.

    To fix this the magic code would need to be hoisted out of sv_2iv_flags() and the check for SvIOK (or SvUOK) done on the scalar returned by the numeric overload.

    Fixing this for every operator would be a big change.

    Edit: pp_add is in pp_hot.c, not sv.c

[reply]
      I put in a bug report for this. Thanks for the confirmation.

      Remember: There's always one more bug.
[reply]

In Section Seekers of Perl Wisdom