extracted the part of ProcessEvent() which is repeated multiple times during the...

[wxWidgets.git] / docs / doxygen / groups / funcmacro_debug.h

diff --git a/docs/doxygen/groups/funcmacro_debug.h b/docs/doxygen/groups/funcmacro_debug.h
index 74bc4819f531e9b8a35929029435db85e0876be4..5024ec607fada9a0183f263834ec786905af705e 100644 (file)
--- a/docs/doxygen/groups/funcmacro_debug.h
+++ b/docs/doxygen/groups/funcmacro_debug.h
@@ -12,15 +12,13 @@
 @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
+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 event in release builds but a check failure
-doesn't generate any user-visible effects then. 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.
-
-@header{wx/debug.h}
+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.
 
 */