-// ----------------------------------------------------------------------------
-/**
- @name Debugging macros
-
- All debugging macros rely on ASSERT() which in turn calls user-defined
- OnAssert() function. To keep things simple, it's called even when the
- expression is TRUE (i.e. everything is ok) and by default does nothing: just
- returns the same value back. But if you redefine it to do something more sexy
- (popping up a message box in your favourite GUI, sending you e-mail or
- whatever) it will affect all ASSERTs, FAILs and CHECKs in your code.
- <BR>
- <BR>
- <b>Warning</b>: if you don't like advices on programming style, don't read
- further! ;-)
- <BR>
- <BR>
- Extensive use of these macros is recommended! Remember that ASSERTs are
- disabled in final (without WXDEBUG defined) build, so they add strictly
- nothing to your program's code. On the other hand, CHECK macros do stay
- even in release builds, but in general are not much of a burden, while
- a judicious use of them might increase your program's stability.
-
- @memo Debugging macros (replacement for standard assert()) and more.
- */
-// ----------------------------------------------------------------------------
-//@{
-
-/** @name Macros which are completely disabled in 'release' mode */
-//@{
-#ifdef __WXDEBUG__
- /**
- this function may be redefined to do something non trivial and is called
- whenever one of debugging macros fails (i.e. condition is false in an
- assertion)
- @param szFile and nLine - file name and line number of the ASSERT
- szMsg - optional message explaining the reason
+#include "wx/wxchar.h" /* for __TFILE__ and wxChar */
+
+/* ---------------------------------------------------------------------------- */
+/* Defines controlling the debugging macros */
+/* ---------------------------------------------------------------------------- */
+
+/* if _DEBUG is defined (MS VC++ and others use it in debug builds), define */
+/* __WXDEBUG__ too */
+#ifdef _DEBUG
+ #ifndef __WXDEBUG__
+ #define __WXDEBUG__
+ #endif /* !__WXDEBUG__ */
+#endif /* _DEBUG */
+
+/* if NDEBUG is defined (<assert.h> uses it), undef __WXDEBUG__ and WXDEBUG */
+#ifdef NDEBUG
+ #undef __WXDEBUG__
+ #undef WXDEBUG
+#endif /* NDEBUG */
+
+/* if __WXDEBUG__ is defined, make sure that WXDEBUG is defined and >= 1 */
+#ifdef __WXDEBUG__
+ #if !defined(WXDEBUG) || !WXDEBUG
+ #undef WXDEBUG
+ #define WXDEBUG 1
+ #endif /* !WXDEBUG */
+#endif /* __WXDEBUG__ */
+
+/* ---------------------------------------------------------------------------- */
+/* Debugging macros */
+/* */
+/* All debugging macros rely on ASSERT() which in turn calls user-defined */
+/* OnAssert() function. To keep things simple, it's called even when the */
+/* expression is TRUE (i.e. everything is ok) and by default does nothing: just */
+/* returns the same value back. But if you redefine it to do something more sexy */
+/* (popping up a message box in your favourite GUI, sending you e-mail or */
+/* whatever) it will affect all ASSERTs, FAILs and CHECKs in your code. */
+/* */
+/* Warning: if you don't like advice on programming style, don't read */
+/* further! ;-) */
+/* */
+/* Extensive use of these macros is recommended! Remember that ASSERTs are */
+/* disabled in final build (without __WXDEBUG__ defined), so they add strictly */
+/* nothing to your program's code. On the other hand, CHECK macros do stay */
+/* even in release builds, but in general are not much of a burden, while */
+/* a judicious use of them might increase your program's stability. */
+/* ---------------------------------------------------------------------------- */
+
+/* Macros which are completely disabled in 'release' mode */
+/* */
+/* NB: these functions are implemented in src/common/appcmn.cpp */
+#if defined(__cplusplus) && defined(__WXDEBUG__)
+ /*
+ this function may be redefined to do something non trivial and is called
+ whenever one of debugging macros fails (i.e. condition is false in an
+ assertion)
+
+ parameters:
+ szFile and nLine - file name and line number of the ASSERT
+ szMsg - optional message explaining the reason