7d9550df50
By default include assertions and debug logging in both debug and release builds but disable them in application release builds (when NDEBUG is defined). Also update (more accurately, replace) debugging overview. git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@61886 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
27 lines
1.1 KiB
C
27 lines
1.1 KiB
C
/////////////////////////////////////////////////////////////////////////////
|
|
// Name: funcmacro_debug.h
|
|
// Purpose: Debugging function and macro group docs
|
|
// Author: wxWidgets team
|
|
// RCS-ID: $Id: funcmacro_gdi.h 52454 2008-03-12 19:08:48Z BP $
|
|
// Licence: wxWindows license
|
|
/////////////////////////////////////////////////////////////////////////////
|
|
|
|
/**
|
|
|
|
@defgroup group_funcmacro_debug Debugging macros
|
|
@ingroup group_funcmacro
|
|
|
|
Useful macros and functions for error checking and defensive programming.
|
|
wxWidgets defines three families of the assert-like macros: the wxASSERT() and
|
|
wxFAIL() macros only do anything if __WXDEBUG__ is defined (in other words, in
|
|
the debug build) but disappear completely in the release build. On the other
|
|
hand, the wxCHECK() macros stay in release builds but a check failure doesn't
|
|
generate any user-visible effects. Finally, the compile time assertions don't
|
|
happen during the run-time but result in the compilation error messages if the
|
|
condition they check fail.
|
|
|
|
Related class group: @ref group_class_debugging.
|
|
|
|
*/
|
|
|