From 6c75df878428c2c65d7c4e8b2165880d65e2b902 Mon Sep 17 00:00:00 2001 From: Francesco Montorsi Date: Sun, 6 Apr 2008 14:49:48 +0000 Subject: [PATCH] small typo fix git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@53044 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/doxygen/overviews/debugging.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/doxygen/overviews/debugging.h b/docs/doxygen/overviews/debugging.h index 0eea7c5698..1bb7d01f18 100644 --- a/docs/doxygen/overviews/debugging.h +++ b/docs/doxygen/overviews/debugging.h @@ -11,7 +11,7 @@ @page overview_debugging Debugging Classes, functions and macros: wxDebugContext, wxObject, wxLog, - @ref group_funcmacro_log, @ref group_funcmacro_debugging + @ref group_funcmacro_log, @ref group_funcmacro_debug Various classes, functions and macros are provided in wxWidgets to help you debug your application. Most of these are only available if you compile both wxWidgets, @@ -73,7 +73,7 @@ compilers allow this definition to work properly, but most do. @section overview_debugging_dbgmacros Debug macros -You should also use @ref group_funcmacro_debugging as part of a 'defensive programming' +You should also use @ref group_funcmacro_debug as part of a 'defensive programming' strategy, scattering wxASSERTs liberally to test for problems in your code as early as possible. Forward thinking will save a surprising amount of time in the long run. -- 2.45.2