Lines Matching defs:for
23 for a list of all functions.
30 remember to allocate/free memory for C strings; working with fixed size buffers almost
32 (std::string). So why the need for wxString?
41 which may be enabled to fine tune the memory allocation strategy for your
47 very useful but don't exist in most of other string classes: for example,
54 \helpref{Unicode overview}{unicode} for more details) and maps to either
63 that there are often several functions to do exactly the same thing: for
111 this is {\bf not} done for {\it printf()} which is a function with variable
144 is empty (returning {\tt true} for {\tt NULL} pointers),
145 \helpref{wxStrlen()}{wxstrlen} also handles NULLs correctly and returns 0 for
165 knowledge of the internal structure of wxString) for storing strings and so it is
170 All considerations for wxObject-derived \helpref{reference counted}{trefcount} objects
171 are valid also for wxString, even if it does not derive from wxObject.
184 of the array subscript operator for this reasons. Please note that
189 never arise because for constant references the correct operator is called automatically.
191 \subsection{Tuning wxString for your application}\label{wxstringtuning}
194 absolutely not necessary to read for using wxString class. Please skip it unless
200 memory needed for each string. Instead, it adds a small amount of space to each
202 expensive operation) too often as when, for example, a string is constructed by
203 subsequently adding one character at a time to it, as for example in:
212 for ( size_t n = 0; n < len; n++ )
230 \helpref{Alloc()}{wxstringalloc} function to preallocate, for example, len bytes
242 important performance benefits for programs using (relatively) few very long
254 98\% for the default allocation policy, if it is less than 90\% you should
255 really consider fine tuning wxString for your application).