AuroraMiddleware/wxWidgets
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

clear up wxStringBuffer docs a bit

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@30338 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Ryan Norton 2004-11-07 11:42:51 +00:00
parent aa13eec585
commit 5687a67ce1
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -1262,6 +1262,13 @@ 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
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
with and without wxUSE\_STL.
\wxheading{Derived from}
None
@ -1320,6 +1327,13 @@ 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
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
with and without wxUSE\_STL.
Note that SetLength {\tt must} be called before wxStringBufferLength destructs.
\wxheading{Derived from}