Lines Matching refs:and
8 {\it MAX\_INT} which is usually 2147483647 on 32 bit machines) and containing
18 construction from other strings, C strings and characters, assignment operators,
19 access to individual characters, string concatenation and comparison, substring
20 extraction, case conversion, trimming and padding (with spaces), searching and
21 replacing and both C-like \helpref{Printf()}{wxstringprintf} and stream-like
39 char *} pointer, sing \helpref{reference counting}{wxstringrefcount}) and speed.
42 particular application - and the gain might be quite big.
45 class and 90\% of the functionality of std::string class.
53 to and from ANSI and Unicode strings in any build mode (see the
54 \helpref{Unicode overview}{unicode} for more details) and maps to either
68 is "native" wxString version and the last one is wxWidgets 1.xx way. So the
74 in both wxWidgets and other programs (by just typedefing wxString as std::string
75 when used outside wxWidgets) and by staying compatible with future versions of
79 try to use the new wxString methods and not the old wxWidgets 1.xx variants
80 which are deprecated and may disappear in future versions.
91 // and returns the result
112 number of arguments (and whose arguments are of unknown types). So this call may
130 \helpref{reference counting}{wxstringrefcount}) and all functions returning
134 \subsection{Other string related functions and classes}\label{relatedtostring}
139 resulting string with a NULL) and are in general not very safe (passing NULL
145 \helpref{wxStrlen()}{wxstrlen} also handles NULLs correctly and returns 0 for
146 them and \helpref{wxStricmp()}{wxstricmp} is just a platform-independent
151 and \helpref{wxVsnprintf}{wxvsnprintf} functions which should be used instead
152 of the inherently dangerous standard {\tt sprintf()} and which use {\tt
159 be broken into tokens and replaces the standard C library {\it
165 knowledge of the internal structure of wxString) for storing strings and so it is
168 \subsection{Reference counting and why you shouldn't care about it}\label{wxstringrefcount}
177 \helpref{GetChar()}{wxstringgetchar}) cannot be chosen and the "read/write"
181 and so if the string was really shared there is some performance loss (both in
182 terms of speed and memory consumption). In the rare cases when this may be
186 this situation and so using it is not really better. Also note that if all
193 \normalbox{{\bf Note:} this section is strictly about performance issues and is
195 you feel familiar with profilers and relative tools. If you do read it, please
222 This is quite a common situation and not allocating extra memory at all would
234 However, using Alloc() is tedious and so wxString tries to do its best. The
236 least 16 bytes (which is the case on almost all of wide-spread platforms) and so
238 multiple of 16. Like this, no memory is lost and 15 iterations from 16 in the
247 which will follow) and analyse the impact of it on your program. If you do it,
249 which tells the wxString class to collect performance statistics and to show
251 strings your program manipulates, their average initial length and also the