It's a stab in the dark ...

Good stab - I can make use of that. The following outputs "True False" on the buggy compilers (and "True True" on sane compilers):

#include <stdio.h>

int main(void) {

   double nv = 2.0 / 3;
   float foo = 2.0 / 3;
   float truncated = (float)nv;

   if(foo == truncated) printf("True ");
   else printf("False ");

   if(foo == (float)nv) printf("True\n");
   else printf("False\n");

   return 0;
}
[download]

I can apply that method (used to obtain that "True") to PDL, which solves the problem I have asked about. Unfortunately, while it enables me to get the behaviour I want with my C demo scripts, it's still not producing the correct result with PDL - but this is such a fickle bug. I'll have to play around with it some more.

PS: This is relevant to the work I do ensuring Windows compatibility for my XS distros

#if defined _MSC_VER && _MSC_VER < 1400 then expect weirdness if you start comparing floats with doubles.

Thanks Marvin.

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.