Jump to content

  • Log In with Google      Sign In   
  • Create Account

Awesome job so far everyone! Please give us your feedback on how our article efforts are going. We still need more finished articles for our May contest theme: Remake the Classics

#Actualedd²

Posted 29 December 2011 - 08:49 AM

But assuming Im doing something wrong (I admit it have to be my fault), how can adding message boxes to the code make it work fine(make it behavior tottaly differently)?

Because the machine code generated may now be totally different. The kinds of optimization a compiler can perform are really, really extreme.

Look for uninitialized variables (initialize everything at the point of definition, always, no exceptions). Add lots of asserts that remain enabled in release mode. Put them around the code you believe is misbehaving.

#2edd²

Posted 29 December 2011 - 08:48 AM

But assuming Im doing something wrong (I admit it have to be my fault), how can adding message boxes to the code make it work fine(make it behavior tottaly differently)?

Because the machine code generated may now be totally different. The kinds of optimization a compiler can perform are really, really extreme.

Look for uninitialized variables (initialize everything at the point of definition, always, no exceptions). Add lots of asserts remain enabled in release mode. Put them around the code you believe is misbehaving.

#1edd²

Posted 29 December 2011 - 08:46 AM

But assuming Im doing something wrong (I admit it have to be my fault), how can adding message boxes to the code make it work fine(make it behavior tottaly differently)?

Because the machine code generated may now be totally different. The kinds of optimization a compiler can perform are really, really extreme.

Look for uninitialized variables (initialize everything at the point of definition, always, no exceptions). Add lots of asserts that are still enabled in release mode. Put them around the code you believe is misbehaving.

PARTNERS