How can I completely disable calls to assert()?

c++ c assert
Abruzzo Forte e Gentile picture Abruzzo Forte e Gentile · Mar 18, 2011 · Viewed 60.8k times · Source

My code is full of calls to assert(condition). In the debug version I use g++ -g which triggers my assertions. Unexpectedly, the same assertions are also triggered in my release version, the one compiled without -g option.

How can I completely disable my assertions at compile time? Should I explicitly define NDEBUG in any build I produce regardless of whether they are debug, release or anything else?

Answer

GWW picture GWW · Mar 18, 2011

You must #define NDEBUG (or use the flag -DNDEBUG with g++) this will disable assert as long as it's defined before the inclusion of the assert header file.

Related questions

What is the "assert" function?

I've been studying OpenCV tutorials and came across the assert function; what does it do?

Read More
How to put assert into release builds in C/C++

I need to only run ship build and I need to assert on certain condition in release build to see if the problem is fixed. How do I do it?

Read More
Is assert evil?

The Go language creators write: Go doesn't provide assertions. They are undeniably convenient, but our experience has been that programmers use them as a crutch to avoid thinking about proper error handling and reporting. Proper error handling means that servers …

Read More