Int32 bug in .Net Framework

Interesting Int32 bug resulted an overflow in arithmetic operation. More from Ladybug:

"I don't think it should overflow. Performing the equivalent operations with Int16 and Int64 work fine. This behavior is the same in VS2003."

Resolved as postponed:

"Because the scenario is corner-case and given where we are in the cycle, I'm going to track this as an issue for consideration in VNext. We do appreciate the issue, we're really just ensuring we're looking at critical issues, since we want to get this product to you ASAP."

Thats it. I used to be happy, but I cannot trust nothing anymore :)

Related Posts:

• Phalanger -- PHP compiler for .Net framework
• Win32 to .NET Framework API Map
• System.Net Namespace Blog
• Subscribe to Check in/Check out
• Comega revisited
• Year 2000 point of view on .NET
• System.Timers.Timer bug
• C omega
• Private User Group
• Reflection.Emit

An overflow isn't a critical issue? Since when...oh that's right since Microsoft. They are to busy churning developers with new .Net releases to fix the bugs. Heh. I am so glad I don't pay the MS .Net tax on my work projects.