]> git.saurik.com Git - wxWidgets.git/blame - docs/doxygen/groups/funcmacro_debug.h
Fix ribbon documentation warnings.
[wxWidgets.git] / docs / doxygen / groups / funcmacro_debug.h
CommitLineData
dae2800a
BP
1/////////////////////////////////////////////////////////////////////////////
2// Name: funcmacro_debug.h
3// Purpose: Debugging function and macro group docs
4// Author: wxWidgets team
526954c5 5// Licence: wxWindows licence
dae2800a
BP
6/////////////////////////////////////////////////////////////////////////////
7
8/**
9
7d9550df 10@defgroup group_funcmacro_debug Debugging macros
dae2800a
BP
11@ingroup group_funcmacro
12
13Useful macros and functions for error checking and defensive programming.
34f5c105
VZ
14
15Starting with wxWidgets 2.9.1, debugging support in wxWidgets is always
16compiled in by default, you need to explicitly define ::wxDEBUG_LEVEL as 0 to
17disable it completely. However, by default debugging macros are dormant in the
18release builds, i.e. when the main program is compiled with the standard @c
19NDEBUG symbol being defined. You may explicitly activate the debugging checks
20in the release build by calling wxSetAssertHandler() with a custom function if
21needed.
22
23When debugging support is active, failure of both wxASSERT() and wxCHECK()
24macros conditions result in a debug alert. When debugging support is inactive
25or turned off entirely at compilation time, wxASSERT() and wxFAIL() macros
26don't do anything while wxCHECK() still checks its condition and returns if it
27fails, even if no alerts are shown to the user.
28
29Finally, the compile time assertions don't happen during the run-time but
30result in the compilation error messages if the condition they check fail.
31They are always enabled and are not affected by ::wxDEBUG_LEVEL.
dae2800a 32
dbbca9fd
FM
33Related class group: @ref group_class_debugging.
34
dae2800a
BP
35*/
36