C++ Question, See if you got what it takes... No Cheating!

Dan Smith · 1999-11-24T21:36:00

Hello.First, Dont cheat. Dont compile this to see why it rocks (or why it sucks). Dont post a response if you compiled it to find out. Just look at this code, and tell me whats wrong with it, if anything... Maybe this is the best code ever... Or maybe its the worst.Look at it, and post your response to why its correct and has no bugs, and why its so great, or why it sucks and wont work the slighest.Anyway, here's the code://#define DEBUG#if defined (DEBUG)#define DebugCode( code_fragment ) { code_fragment }#else#define DebugCode ( code_fragment )#endifI'll be waiting for your answers...No Cheating!Dan Smith

GDNet Lounge Community

Started by Dan Smith November 24, 1999 09:36 PM

9 comments, last by Dan Smith 24 years, 4 months ago

Anonymous

November 24, 1999 09:36 PM

Ok this is what it looks like to me...

You have a macro called DebugCode that
does something unspecified. It only does
this when DEBUG has been defined. When
DEBUG is commented out (for your release
version of course), it defines a blank
macro.

This is cool because when DEBUG is defined
you can have all awesome messages for the programmer and log files and stuff, then you
just change 1 line to release it.

C++ Question, See if you got what it takes... No Cheating!

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

C++ Question, See if you got what it takes... No Cheating!

This topic is closed to new replies.

Popular Topics

Recommended Tutorials

Reticulating splines