To put it more simply, I gather you are asking about the difference between these two cases: 
perl -Mbigint -wle '($x,$y)=split " ","9 2"; $z = $x / $y; print $z'
4.5

perl -Mbigint -wle '($x,$y)=map {$_+= 0} split " ","9 2"; $z = $x / $y
+; print $z'
4

[download]
The manual for bigint says "Integer constants are created as proper BigInts. Floating point constants are truncated to integer."

It doesn't say anything about interpolating strings into "proper Bigints", so… while this behavior does seem to go against the spirit of DWIM, it's not officially a bug if strings have to be coerced explicitly into numbers in order for them to become bigints.

Or was there some other issue that you were trying to describe?

In reply to Re: is it a BigInt bug? by graff
in thread is it a BigInt bug? by rsFalse

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.