blind PCH-less build fixes: add missing headers

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

diff --git a/docs/doxygen/mainpages/devtips.h b/docs/doxygen/mainpages/devtips.h
index 0ca7bea32f0467d0c5763e18af016829126cfde3..085b4ea96060f77ca590bdde1aea4b30f9c86429 100644 (file)
--- a/docs/doxygen/mainpages/devtips.h
+++ b/docs/doxygen/mainpages/devtips.h
@@ -152,11 +152,10 @@ For details on using makefiles, configure, and project files, please see
 @c "docs/xxx/install.txt" in your distribution, where @c "xxx" is the platform
 of interest, such as @c msw, @c gtk, @c x11, @c mac.
 
-All wxWidgets makefiles are generated using
-@link http://www.bakefile.org Bakefile @endlink. wxWidgets also provides (in
-the @c "build/bakefiles/wxpresets" folder) the wxWidgets bakefile presets.
-These files allow you to create bakefiles for your own wxWidgets-based
-applications very easily.
+All wxWidgets makefiles are generated using Bakefile <http://www.bakefile.org/>.
+wxWidgets also provides (in the @c "build/bakefiles/wxpresets" folder) the
+wxWidgets bakefile presets. These files allow you to create bakefiles for your
+own wxWidgets-based applications very easily.
 
 
 
@@ -267,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.
 
-@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
@@ -430,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.
 
-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.