Weird gcc behavior
#4
It needn't. It's a bool value and any nonzero is "true". That's why I made a commit recently removing all "== true" comparisons - they needn't work as intended, two true values needn't be equal Wink
When I get home (yes, I'm on a train), I'll try putting the CanBe into the log inside the condition, to see if it changed externally; but that is highly unlikely.
Reply
Thanks given by:


Messages In This Thread
Weird gcc behavior - by xoft - 11-18-2012, 11:35 PM
RE: Weird gcc behavior - by ThuGie - 11-19-2012, 01:15 AM
RE: Weird gcc behavior - by FakeTruth - 11-19-2012, 03:10 AM
RE: Weird gcc behavior - by xoft - 11-19-2012, 03:50 AM
RE: Weird gcc behavior - by xoft - 11-19-2012, 07:43 AM
RE: Weird gcc behavior - by FakeTruth - 11-19-2012, 07:57 AM
RE: Weird gcc behavior - by xoft - 11-19-2012, 04:19 PM
RE: Weird gcc behavior - by FakeTruth - 11-19-2012, 05:56 PM



Users browsing this thread: 1 Guest(s)