well, i guess debug mode lets u debug and stuff but i got a project that compiles fine in debug mode and works like its supposed to. in release mode, it compiles too but it sometimes crashes i''m using vc++6.0 btw, if any other program has both debug and release. thuned life is unfair, take advantage of it. UNMB2 - if the link doesn''t work, try clicking it

Well, Debug has additional statements added to aid in tracking were in the C++ file(s) (not in the ASM output ) the error is. That''s also half of why it runs slower. It does things like flush pointers after they''re done being used, et cetera.

Your position is kind of the opposite of mine. I can''t get my code to work in Debug, but it works great in Release .

"Finger to spiritual emptiness underlying everything." -- How a C manual referred to a "pointer to void." --Things People Said

http://www.gdarchive.net/druidgames/

i never even knew there was a release mode until like an hour ago. so i just developed my prog using debug. oh well


thuned

life is unfair, take advantage of it.
UNMB2 - if the link doesn''t work, try clicking it

Debug is a lot slower, so try to get it to work in Release if you can.

"Finger to spiritual emptiness underlying everything." -- How a C manual referred to a "pointer to void." --Things People Said

http://www.gdarchive.net/druidgames/

yeah, i noticed.. framerate doubles. well, i found the error. in debug, i had something like
char* text = "abc";
if (text == "abc") blah

and that worked. in release i narrowed it down to that and changed it to strcmp and it worked. any1 know why there''s this difference?

thuned

life is unfair, take advantage of it.
UNMB2 - if the link doesn''t work, try clicking it

Sting literals are not required to be reused. That is to say, in your compiler''s Debug mode, both "abc"s point to the same memory address, which is not the case in it''s Release mode.