I'm just looking at the lack of elegance - that's pretty much it.
I've no objection to inelegant code (of which I've written heaps) if it needs to be that way.
If not for the portability concerns, I'd pick up on stevieb's suggestion and just have the XSub as :

int uv_fits_double(UV arg) {

  arg >>= __builtin_ctzll(arg);
  if(arg < 9007199254740993) return 1;
  return 0;
}
[download]

That seems to work fine on MinGW-built Windows perls, where $Config{ivtype} is 'long long', and I'd be happy with that even if it wasn't any more efficient.
I didn't know about the existence of __builtin_ctz() and friends. Thanks, stevieb for bringing it to my attention. I'll do some benchmarking later on, and see how much time it saves.
It's an option that could come in handy to me in the future.

I guess that, mainly, I just want to know if there are some more elegant (&& portable) options available.

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.