No one else is commenting, so I'll take a wild stab.

Why not add more elsif branches to your sub? You say you're worried about bmul behaving badly if it's handed something other than a BigInt, so why not just check for it?

You could also run some tests or read the source to find out what bmul really does if the 2nd operand isn't a BigInt.

Why would you have to explicitly bless your integers if you made a subclass of Math::BigInt?

And to step back a little: are you sure you want to do overloading? Will future users (or yourself) be flummoxed that $a*$b isn't doing what they expect? Is typing '$obj->mult($other_thing)' really that bad? At least that way you know exactly what you just did.

Okay, that's about all I can think of. I hope I was helpful.

--Pileofrogs

In reply to Re: Overloading multiplication involving BigInt by pileofrogs
in thread Overloading multiplication involving BigInt by grondilu

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.