2008-03-14 01:47:17 -04:00
|
|
|
/////////////////////////////////////////////////////////////////////////////
|
|
|
|
// 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 $
|
2010-07-13 09:29:13 -04:00
|
|
|
// Licence: wxWindows licence
|
2008-03-14 01:47:17 -04:00
|
|
|
/////////////////////////////////////////////////////////////////////////////
|
|
|
|
|
|
|
|
/**
|
|
|
|
|
2009-09-12 07:28:52 -04:00
|
|
|
@defgroup group_funcmacro_debug Debugging macros
|
2008-03-14 01:47:17 -04:00
|
|
|
@ingroup group_funcmacro
|
|
|
|
|
|
|
|
Useful macros and functions for error checking and defensive programming.
|
2008-03-14 23:14:51 -04:00
|
|
|
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
|
2008-03-14 01:47:17 -04:00
|
|
|
the debug build) but disappear completely in the release build. On the other
|
2008-03-14 23:14:51 -04:00
|
|
|
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.
|
2008-03-14 01:47:17 -04:00
|
|
|
|
2008-12-12 13:51:54 -05:00
|
|
|
Related class group: @ref group_class_debugging.
|
|
|
|
|
2008-03-14 01:47:17 -04:00
|
|
|
*/
|
|
|
|
|