made wxString::Replace, Matches and Find work with any form of string argument

[wxWidgets.git] / docs / latex / wx / body.tex

diff --git a/docs/latex/wx/body.tex b/docs/latex/wx/body.tex
index d23380c7bd927f597a0fcaea71f1f4a76ae79536..5e5483f3794ee24ef4f89deb0c8714e125529689 100644 (file)
--- a/docs/latex/wx/body.tex
+++ b/docs/latex/wx/body.tex
@@ -264,8 +264,9 @@ the following section before any other includes:
 The file {\tt "wx/wxprec.h"} includes {\tt "wx/wx.h"}. Although this incantation
 may seem quirky, it is in fact the end result of a lot of experimentation,
 and several Windows compilers to use precompilation which is largely automatic for
-compilers with necessary support. Currently it is used for Visual C++ (including 
-embedded Visual C++), Borland C++, Open Watcom C++ and newer versions of GCC.
+compilers with necessary support. Currently it is used for Visual C++ (including
+embedded Visual C++), Borland C++, Open Watcom C++, Digital Mars C++
+and newer versions of GCC.
 Some compilers might need extra work from the application developer to set the
 build environment up as necessary for the support.
 
@@ -534,14 +535,6 @@ Helpgen can be found in {\tt utils/HelpGen}.
 Xnest-based display emulator for X11-based PDA applications. On some
 systems, the Xnest window does not synchronise with the
 'skin' window. This program can be found in {\tt utils/emulator}.
-\item[{\bf Configuration Tool}]
-The wxWidgets Configuration Tool is a work in progress
-intended to make it easier to configure wxWidgets
-features in detail. It exports setup.h configurations and will
-eventually generate makefile config files. Invoking compilers is
-also on the cards. Since configurations are
-handled one at a time, the tool is of limited used until further
-development can be done. The program can be found in {\tt utils/configtool}.
 \item[{\bf XRC resource system}]
 This is the sizer-aware resource system, and uses
 XML-based resource specifications that can be generated by tools
@@ -599,7 +592,7 @@ it can alert you to problems later on.
 
 \subsection{Use wxString in preference to character arrays}\label{usewxstring}
 
-Using wxString can be much safer and more convenient than using char *.
+Using wxString can be much safer and more convenient than using wxChar *.
 Again, I haven't practiced what I'm preaching, but I'm now trying to use
 wxString wherever possible. You can reduce the possibility of memory
 leaks substantially, and it is much more convenient to use the overloaded