Fabs has side effects
Yes, Microsoft. Taking the absolute value of a number changes the original number.
Or was it the subtraction? Yeah, those subtraction-with-side-effects things are pretty hard to work around.
Getting the z property has a 0 chance of changing vecStart or vecEnd.
Wow, that is major WTFery.
fabsover-ridden? Or maybe the
I'm so glad my tools reject improperly typed side effects.
You guys know that you can't do function calls in a hardware-based conditional breakpoint, right?
(edit: clarified breakpoint type)
Shame on you, Microsoft engineers, for not being able to verify that a function has no side effects! I mean, this cannot be an unsolvable or hard problem, can it?
NP stands for "No Problemo!" right?
I'm more concerned that they consider being fabulous a problem.
Filed under: That's what it means, right?
So, I'm assuming that
vecEnd.z - vecStart.z > 4 || vecStart.z - vecEnd.z > 4
would have probably worked just fine?
I can't read Algol-based languages anymore. It's like a foreign language to me.
Just rewrite everything in Haskell. Problem solved.
Let me introduce you to the FPU status word: