Fix discrepancy between different ways of measuring text extents under Mac.

[wxWidgets.git] / docs / doxygen / mainpages / devtips.h

diff --git a/docs/doxygen/mainpages/devtips.h b/docs/doxygen/mainpages/devtips.h
index 3aa29be9acab0ddfc319c5e9047763607cb430a1..085b4ea96060f77ca590bdde1aea4b30f9c86429 100644 (file)
--- a/docs/doxygen/mainpages/devtips.h
+++ b/docs/doxygen/mainpages/devtips.h
@@ -266,19 +266,6 @@ switched off by default) since it is a notoriously unportable feature.
 wxWidgets does not use C++ run-time type information since wxWidgets provides
 its own run-time type information system, implemented using macros.
 
 wxWidgets does not use C++ run-time type information since wxWidgets provides
 its own run-time type information system, implemented using macros.
 

-@subsection page_multiplatform_cpp_null Type of NULL
-
-Some compilers (e.g. the native IRIX cc) define @NULL to be 0L so that no
-conversion to pointers is allowed. Because of that, all these occurrences of
-@NULL in the GTK+ port use an explicit conversion such as
-
-@code
-wxWindow *my_window = (wxWindow*) NULL;
-@endcode
-
-It is recommended to adhere to this in all code using wxWidgets as this make
-the code (a bit) more portable.
-

 @subsection page_multiplatform_cpp_precompiledheaders Precompiled Headers
 
 Some compilers, such as Borland C++ and Microsoft C++, support precompiled
 @subsection page_multiplatform_cpp_precompiledheaders Precompiled Headers
 
 Some compilers, such as Borland C++ and Microsoft C++, support precompiled


@@ -429,7 +416,7 @@ the end of the program if wxWidgets is suitably configured. Depending on the
 operating system and compiler, more or less specific information about the
 problem will be logged.
 
 operating system and compiler, more or less specific information about the
 problem will be logged.
 

-You should also use @ref group_funcmacro_debugging as part of a "defensive
+You should also use @ref group_funcmacro_debug as part of a "defensive

 programming" strategy, scattering wxASSERT()s 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.
 programming" strategy, scattering wxASSERT()s 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.