Very large numbers cause MOD to return negative numbers...
PRINT MOD(3124987331, 100), 30,30...for example.
The number is not out of bounds but its close, I don't know if that's where the problem lies.
oh no. Do you really, really need this?
Well, it showed up in Hash table alogorithms... I had to insert " (unsigned int) bigfloatvar % 100" as a inline to work around it...
What about INLINE...
that's what he did.
The problem is: when the number is negative, (unsigned int)n%m returns a wrong number. That might explain it. Also: The gp2x/pocketpc devices use 32bit floats only -> here you get this error much earlier. Please try to avoid these large numbers if possible.
Quote from: GernotFrischthat's what he did.
The problem is: when the number is negative, (unsigned int)n%m returns a wrong number. That might explain it. Also: The gp2x/pocketpc devices use 32bit floats only -> here you get this error much earlier. Please try to avoid these large numbers if possible.
Good to know, Ill add a note in the source and check it, when I get to the pocket PC version. ;)