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

merged 2.2 branch

Browse Source 
git-svn-id: https://svn.wxwidgets.org/svn/wx/wxWidgets/trunk@7748 c3d73ce0-8a6f-49c7-b76d-6d57e0e08775
This commit is contained in:
Bryan Petty
2000-07-15 19:51:35 +00:00
parent 8a693e6e04
commit f6bcfd974e
1835 changed files with 237729 additions and 67990 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
docs/latex/wx/tstring.tex
View File

@@ -13,7 +13,7 @@ wxString only works with ASCII (8 bit characters) strings as of this release,
but support for UNICODE (16 but characters) is planned for the next one.
This class has all the standard operations you can expect to find in a string class:
dynamic memory management (string extends to accomodate new characters),
dynamic memory management (string extends to accommodate new characters),
construction from other strings, C strings and characters, assignment operators,
access to individual characters, string concatenation and comparison, substring
extraction, case conversion, trimming and padding (with spaces), searching and
@@ -60,8 +60,8 @@ wxString internally by wxWindows.
However, there are several problems as well. The most important one is probably
that there are often several functions to do exactly the same thing: for
example, to get the length of the string either one of
\helpref{length()}{wxstringlength}, \helpref{Len()}{wxstringlen} or
\helpref{Length()}{wxstringLength} may be used. The first function, as almost
length(), \helpref{Len()}{wxstringlen} or
\helpref{Length()}{wxstringlength} may be used. The first function, as almost
all the other functions in lowercase, is std::string compatible. The second one
is "native" wxString version and the last one is wxWindows 1.xx way. So the
question is: which one is better to use? And the answer is that:
@@ -73,7 +73,7 @@ in both wxWindows and other programs (by just typedefing wxString as std::string
when used outside wxWindows) and by staying compatible with future versions of
wxWindows which will probably start using std::string sooner or later too.
In the situations where there is no correspondinw std::string function, please
In the situations where there is no corresponding std::string function, please
try to use the new wxString methods and not the old wxWindows 1.xx variants
which are deprecated and may disappear in future versions.
@@ -171,7 +171,7 @@ share the same data.
But as soon as one of the two (or more) strings is modified, the data has to be
copied because the changes to one of the strings shouldn't be seen in the
otheres. As data copying only happens when the string is written to, this is
others. As data copying only happens when the string is written to, this is
known as COW.
What is important to understand is that all this happens absolutely
@@ -259,7 +259,7 @@ which tells the wxString class to collect performance statistics and to show
them on stderr on program termination. This will show you the average length of
strings your program manipulates, their average initial length and also the
percent of times when memory wasn't reallocated when string concatenation was
done but the alread preallocated memory was used (this value should be about
done but the already preallocated memory was used (this value should be about
98\% for the default allocation policy, if it is less than 90\% you should
really consider fine tuning wxString for your application).