Well if you set the compiler options correctly, the code won't even compile when you access a variable without initializing it. Unfortunately Valve's SDK still needs a lot of work to be at that level. (I posted some of the changes on the KI list.)
At 2006/04/27 03:57 AM, Garry Newman wrote: >-- >[ Picked text/plain from multipart/alternative ] >It always seemed backwards to me. > >When I'm in debug mode I want the compiler to do its best to try to make it >crash. I want it to throw a rain-man style spazz attack any time the >slightest thing is wrong. > >I dunno though, I've kind of heard the opposite too.. that the memory was >filled with random junk. > > > >On 4/27/06, Justin Krenz <[EMAIL PROTECTED]> wrote: >> >> What defines that all variables are initialized to 0? Is it a compiler >> flag, and why wouldn't you want this to be always set? This is the >> first I've heard of it. >> >> Ben Everett wrote: >> > The most common cause of crashes in release mode but not in debug are >> due to >> > variable initializations. In debug mode all variables are initialized to >> > '0', while in release mode they do not have a default initialization >> value. >> > >> > The most common cause of these crashes is failing to properly initialize >> > variables. >> > >> >> _______________________________________________ >> To unsubscribe, edit your list preferences, or view the list archives, >> please visit: >> http://list.valvesoftware.com/mailman/listinfo/hlcoders >> >> >-- > >_______________________________________________ >To unsubscribe, edit your list preferences, or view the list archives, please >visit: >http://list.valvesoftware.com/mailman/listinfo/hlcoders _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlcoders
