The if statement is SUPPOSED to fail... but it still goes into the if statement even though it clearly equals "false". is there a fix?
If statement glitch
Author
The if statement is SUPPOSED to fail... but it still goes into the if statement even though it clearly equals "false". is there a fix?
Author
because you see when i held my mouse over it how the overall if statement "= false" which means it's supposed to fail.
Author
just tried that, that didn't work either. that is really bizarre... but i'm going to need a fix soon... any other ideas?
dont use the debugger for device IO, use some sort of console output to see if the logic checks out ? is this just ur debugger?
Author
yea, i put a break a little before it, then stepped down to that code, put the mouse over that if statement (while highlighted to get the entire evaluation) and when in the tooltip box is what it's coming out to, but not apperently..
All I can think of is, since you're past that step in the program, the copmiler maybe started using the memory for something else, and now when you hold your mouse over it, it happens to evaluate to 'false'.
But in Debug mode a compiler shouldn't do anything like that I don't think.
But in Debug mode a compiler shouldn't do anything like that I don't think.
I'd print the values just before the if statement and double check that they are actually coming out as false.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
