for self educational purposes I tried to find a way to create a height map all by myself. I googled a little bit and found a function that creates pseudo-random numbers.
public static float Noise(int x)
{
x = (x << 13) ^ x;
return (1f - ((x * (x * x * 15731 + 789221) + 1376312589) & 0x7FFFFFFF) / 1073741824.0f);
}
Since the language of choice for me is VB.net I translated this function to:
Private Function Noise(ByVal x As Integer) As Double
x = (x << 13) Xor x
Return (1.0R - ((x * (x * x * 15731.0R + 789221.0R) + 1376312589.0R) And &H7FFFFFFF) / 1073741824.0R)
End Function
If I use the C# version I get results for x values from 1 to 100. If I use the VB.net version I get values for x<6 but an OverFlowException
for x=6. When I disassembled the parts of this function I found out the the part that overflows is
(x * x * 15731.0R)
So, my first question is: Why do I get an OverflowException
in VB.net but not in C#? If an interim result is too big for its containing variable it should be too big no matter what language I use.
And my second question is: What can I do to make it work in VB.net as well?
Thank you for your answers.
Why do I get an OverflowException in VB.net but not in C#?
Because VB projects check for overflow by default, while C# does not. You'd see the same exception in C# if you either set the project to check for overflow or put the code in a checked{ }
block:
public static float Noise(int x)
{
x = (x << 13) ^ x;
checked{
return (1f - ((x * (x * x * 15731) + 1376312589) & 0x7FFFFFFF) / 1073741824.0f);
}
}
What can I do to make it work in VB.net as well?
I doubt it "works" for C#. Since it overflows silently you are probably getting incorrect results.
However, you can prevent the overflow by casting x
to a double:
Private Function Noise(ByVal x As Integer) As Double
x = (x << 13) Xor x
Dim y As Double = x
Return (1.0R - ((y * (y * y * 15731.0R) + 1376312589.0R) And &H7FFFFFFF) / 1073741824.0R)
End Function
You can also turn on the "Remove integer overflow checks" property of your VB project, but that's a project wide setting. VB currently doesn't have a way of turning off overflow checks for specific lines of code like C# does.
Whatever you do, I would test it thoroughly since you are computing a floating-point value, bit-masking it (And &H7FFFFFFF
) and then dividing by another floating-point value. Mixing integer and floating point math can be very tricky.
Also note that your two code segments are NOT equivalent. Your C# function returns a float
while VB returns a Double
. And you are using floating-point literals in VB but integer literals in C#. It may not seem like a big difference but it can change the math unexpectedly.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With