|
-
Jun 19th, 2004, 03:10 PM
#1
Thread Starter
New Member
Debug vs. Release
Sorry for the lame question but, what's the difference between Debug and Release versions?
-
Jun 19th, 2004, 03:46 PM
#2
Addicted Member
Debug versions contain debugging information which can make the EXE a LOT bigger. They are also generally slower than their Release version counterparts which are usually optimised for faster execution/smaller executables.
I'm sure someone else could explain this better, but I think this is the jist.
Using Visual Studio .NET 2005
-
Jun 19th, 2004, 03:49 PM
#3
Thread Starter
New Member
No, no! That's possibly the best reply I could've expected - short and sweet! Drills down like water. Thankzzo much!
-
Jun 20th, 2004, 03:18 AM
#4
Compilers in debug mode also usually define symbols and other symbols in release mode. In other words, on MSVC you can do:
#ifdef _DEBUG
code here
#endif
and this code will only be compiled in debug versions of the program. Some macros, like ASSERT, use this to make sure they get replaced by nothing in release versions.
All the buzzt
 CornedBee
"Writing specifications is like writing a novel. Writing code is like writing poetry."
- Anonymous, published by Raymond Chen
Don't PM me with your problems, I scan most of the forums daily. If you do PM me, I will not answer your question.
-
Jun 20th, 2004, 08:27 AM
#5
Originally posted by CornedBee
Compilers in debug mode also usually define symbols and other symbols in release mode. In other words, on MSVC you can do:
#ifdef _DEBUG
code here
#endif
and this code will only be compiled in debug versions of the program. Some macros, like ASSERT, use this to make sure they get replaced by nothing in release versions.
Ohhh...I didn't know that.. ..thanks. Then if I get that memory manager up and running I can enclose it into _DEBUG. Smart...
ØØ
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|