Lines Matching defs:of
7 wxString is a class which represents a character string of arbitrary length (limited by
23 for a list of all functions.
25 \subsection{Comparison of wxString to other string classes}\label{otherstringclasses}
27 The advantages of using a special string class instead of working directly with
28 C strings are so obvious that there is a huge number of such classes available.
38 in terms of size (each wxString objects takes exactly the same space as a {\it
45 class and 90\% of the functionality of std::string class.
46 \item {\bf Rich set of functions} Some of the functions present in wxString are
47 very useful but don't exist in most of other string classes: for example,
56 \item {\bf Used by wxWidgets} And, of course, this class is used everywhere
58 conversions of objects of any other string class (including std::string) to
64 example, to get the length of the string either one of
71 {\bf The usage of std::string compatible functions is strongly advised!} It will
73 have knowledge of std::string but not of wxString), let you reuse the same code
75 when used outside wxWidgets) and by staying compatible with future versions of
87 danger of this implicit conversion may be seen in the following code fragment:
102 There are two nasty bugs in these three lines. First of them is in the call to the
104 automatically by the compiler in the case of
110 because the argument of {\it puts()} is known to be of the type {\it const char *},
112 number of arguments (and whose arguments are of unknown types). So this call may
125 just make the function return wxString instead of a C string.
129 strings inside the function faster because of
137 a few functions to work with them. Unfortunately, some of them have rather
147 version of case-insensitive string comparison function known either as
152 of the inherently dangerous standard {\tt sprintf()} and which use {\tt
163 is just a version of the "template" dynamic array class which is specialized to work
165 knowledge of the internal structure of wxString) for storing strings and so it is
166 vastly better from a performance point of view than a wxObjectArray of wxStrings.
182 terms of speed and memory consumption). In the rare cases when this may be
184 of the array subscript operator for this reasons. Please note that
199 For the performance reasons wxString doesn't allocate exactly the amount of
200 memory needed for each string. Instead, it adds a small amount of space to each
226 a great number of wxString objects typically used in a program would also
235 default algorithm assumes that memory allocation is done in granularity of at
236 least 16 bytes (which is the case on almost all of wide-spread platforms) and so
237 nothing is lost if the amount of memory to allocate is rounded up to the next
238 multiple of 16. Like this, no memory is lost and 15 iterations from 16 in the
243 strings. The amount of memory allocated is configured by the setting of {\it
247 which will follow) and analyse the impact of it on your program. If you do it,
250 them on stderr on program termination. This will show you the average length of
252 percent of times when memory wasn't reallocated when string concatenation was