I didn't think of it either

It's also worth pointing out that once you've isolated that critical bit, it's still not exactly braindead straightforward as to how best to make use of that info.
Think of an integer, find its least significant set bit, left-shift its value 53 places, subtract 1, flip all of the bits, and then & that result with the number you first thought of.

I made a small modification to the sub so that it handled negative and positive IV/UV values.
I also compounded the guts of the code into 2 lines. (It could be put into 1 line, but I didn't go that far.)
Here's what I ended up with ... minus explanatory comments.

int iv_fits_double(SV * t, ...) {
    dXSARGS;
    int i, count = 0;

  for(i = 0; i < items; i++) {
    IV arg = SvIV(ST(i));
    int sign = ( arg > 0 || SvUOK(ST(i)) ) ? 1 : -1;

    UV valid_bits = ((arg & -arg) << 53) - 1;
    if(!((arg * sign) & (~valid_bits))) count++;
  }
  return count;
}
[download]

Cheers,
Rob

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.