From 5687a67ce1e365d010c6282aa57b4f99f7f5ea29 Mon Sep 17 00:00:00 2001 From: Ryan Norton Date: Sun, 7 Nov 2004 11:42:51 +0000 Subject: [PATCH] clear up wxStringBuffer docs a bit git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@30338 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775 --- docs/latex/wx/wxstring.tex | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/docs/latex/wx/wxstring.tex b/docs/latex/wx/wxstring.tex index b9a5031754..c17955959b 100644 --- a/docs/latex/wx/wxstring.tex +++ b/docs/latex/wx/wxstring.tex @@ -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}