It's hard to say for certain what the cause is for your "cryptic error", since you didn't include it with the question. Fortunately, my openSuSE 11.1 box has both bignum and Tk available on it, and when I run your code (with use strict ;-) ) I do see _an_ error which may or may not be applicable:
Assertion ((svtype)((_svi)->sv_flags & 0xff)) >= SVt_PV failed: file " +objGlue.c", line 307 at /usr/lib/perl5/vendor_perl/5.10.0/x86_64-linu +x-thread-multi/Tk/Widget.pm line 205. at ./foo.pl line 9
This appears to be failed assert from Tk. My best guess is that the integer width constant is being translated into a bignum, and that Tk doesn't like it. Question: do you really need seamless big integers, or would it be sufficient to specify a few variables as big numbers with a module like Math::BigInt?

In reply to Re: Problems with Tk and bignum by papidave
in thread Problems with Tk and bignum by Microcebus

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.