Re: A simple preprocessor question
Re: A simple preprocessor question
- Subject: Re: A simple preprocessor question
- From: Shamyl Zakariya <email@hidden>
- Date: Tue, 20 Mar 2007 13:29:55 -0400
In that case, is there any preprocessor constant that *is* defined
when building a debug executable ( that isn't when building a release )?
email@hidden
On Mar 20, 2007, at 1:22 PM, alex wrote:
DEBUG must not be defined.
#ifndef DEBUG
#error "DEBUG not defined"
#endif
alex
At 1:17 PM -0400 3/20/07, Shamyl Zakariya wrote:
I have a framework ( wrapping some base opengl functionality )
which defines a macro which (in a debug build) queries for OpenGL
errors, and in a release build does nothing -- since querying for
GL errors is runtime expensive.
The macro looks like this:
#if DEBUG
#define glError() { \
GLenum err = glGetError(); \
while (err != GL_NO_ERROR) { \
printf("glError: %s caught at %s:%u\n", (char *)gluErrorString
(err), __FILE__, __LINE__); \
err = glGetError(); \
} \
}
#else
#define glError() ;
#endif
As far as I can tell, this used to work. In debug builds, the
macro expanded and would query for runtime errors. And in release
builds, it went away and my code ran quickly, like it should.
Now, at some recent point ( I can't say exactly when ) it began to
follow the #else path in both debug and release builds. I assume
I'm using the wrong preprocessor directive... so can anybody tell
me how better to bracket this?
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden