Amebis/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Typo correction patch [ 1208110 ] Lots of typo corrections

Browse Source 
Olly Betts


git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@34436 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Julian Smart
2005-05-31 09:20:43 +00:00
parent a6905d8b55
commit 3103e8a97e
155 changed files with 279 additions and 371 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/latex/wx/wxstring.tex
View File

@@ -1257,7 +1257,7 @@ buffer (which must be writable, of course) you might call it like this:
\end{verbatim}
Note that the exact usage of this depends on whether on not wxUSE\_STL is enabled. If
wxUSE\_STL is enabled, wxStringBuffer creates a seperate empty character buffer, and
wxUSE\_STL is enabled, wxStringBuffer creates a separate empty character buffer, and
if wxUSE\_STL is disabled, it uses GetWriteBuf() from wxString, keeping the same buffer
wxString uses intact. In other words, relying on wxStringBuffer containing the old
wxString data is probably not a good idea if you want to build your program in both
@@ -1322,7 +1322,7 @@ of the string, you might call it like this:
\end{verbatim}
Note that the exact usage of this depends on whether on not wxUSE\_STL is enabled. If
wxUSE\_STL is enabled, wxStringBuffer creates a seperate empty character buffer, and
wxUSE\_STL is enabled, wxStringBuffer creates a separate empty character buffer, and
if wxUSE\_STL is disabled, it uses GetWriteBuf() from wxString, keeping the same buffer
wxString uses intact. In other words, relying on wxStringBuffer containing the old
wxString data is probably not a good idea if you want to build your program in both