    wxstring overviewclasses: wxstring, wxarraystring, wxstringtokenizer
introduction
introductionwxstring is a class which represents a character string of arbitrary length (limited by max_int which is usually 2147483647 on 32 bit machines) and containing arbitrary characters. the ascii nul character is allowed, but be aware that in the current string implementation some methods might not work correctly in this case. wxstring works with both ascii (traditional, 7 or 8 bit, characters) as well as unicode (wide characters) strings. this class has all the standard operations you can expect to find in a string class: 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 replacing and both c-like printf() and stream-like insertion functions as well as much more - see wxstring for a list of all functions.
comparison of wxstring to other string classesthe advantages of using a special string class instead of working directly with c strings are so obvious that there is a huge number of such classes available. the most important advantage is the need to always remember to allocate/free memory for c strings; working with fixed size buffers almost inevitably leads to buffer overflows. at last, c++ has a standard string class (std::string). so why the need for wxstring? there are several advantages:
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 length(), len() or length() 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 wxwidgets 1.xx way. so the question is: which one is better to use? and the answer is that: the usage of std::string compatible functions is strongly advised! it will both make your code more familiar to other c++ programmers (who are supposed to have knowledge of std::string but not of wxstring), let you reuse the same code in both wxwidgets and other programs (by just typedefing wxstring as std::string when used outside wxwidgets) and by staying compatible with future versions of wxwidgets which will probably start using std::string sooner or later too. in the situations where there is no corresponding std::string function, please try to use the new wxstring methods and not the old wxwidgets 1.xx variants which are deprecated and may disappear in future versions.
some advice about using wxstringprobably the main trap with using this class is the implicit conversion operator to const char *. it is advised that you use c_str() instead to clearly indicate when the conversion is done. specifically, the danger of this implicit conversion may be seen in the following code fragment:
// this function converts the input string to uppercase, output it to the screen
// and returns the result
const char *sayhello(const wxstring& input)
{
wxstring output = input.upper();
printf("hello, %s!\n", output);
return output;
}
there are two nasty bugs in these three lines. first of them is in the call to the
printf() function. although the implicit conversion to c strings is applied
automatically by the compiler in the case of
puts(output);
because the argument of puts() is known to be of the type const char *,
this is not done for printf() which is a function with variable
number of arguments (and whose arguments are of unknown types). so this call may
do anything at all (including displaying the correct string on screen), although
the most likely result is a program crash. the solution is to use
c_str(): just replace this line with
printf("hello, %s!\n", output.c_str());
the second bug is that returning output doesn't work. the implicit cast is
used again, so the code compiles, but as it returns a pointer to a buffer
belonging to a local variable which is deleted as soon as the function exits,
its contents is totally arbitrary. the solution to this problem is also easy:
just make the function return wxstring instead of a c string.this leads us to the following general advice: all functions taking string arguments should take const wxstring& (this makes assignment to the strings inside the function faster because of reference counting) and all functions returning strings should return wxstring - this makes it safe to return local variables.
other string related functions and classesas most programs use character strings, the standard c library provides quite a few functions to work with them. unfortunately, some of them have rather counter-intuitive behaviour (like strncpy() which doesn't always terminate the resulting string with a null) and are in general not very safe (passing null to them will probably lead to program crash). moreover, some very useful functions are not standard at all. this is why in addition to all wxstring functions, there are also a few global string functions which try to correct these problems: wxisempty() verifies whether the string is empty (returning true for null pointers), wxstrlen() also handles nulls correctly and returns 0 for them and wxstricmp() is just a platform-independent version of case-insensitive string comparison function known either as stricmp() or strcasecmp() on different platforms. the <wx/string.h> header also defines wxsnprintf and wxvsnprintf functions which should be used instead of the inherently dangerous standard sprintf() and which use snprintf() instead which does buffer size checks whenever possible. of course, you may also use wxstring::printf which is also safe. there is another class which might be useful when working with wxstring: wxstringtokenizer. it is helpful when a string must be broken into tokens and replaces the standard c library strtok() function. and the very last string-related class is wxarraystring: it is just a version of the "template" dynamic array class which is specialized to work with strings. please note that this class is specially optimized (using its knowledge of the internal structure of wxstring) for storing strings and so it is vastly better from a performance point of view than a wxobjectarray of wxstrings.
reference counting and why you shouldn't care about itall considerations for wxobject-derived reference counted objects are valid also for wxstring, even if it does not derive from wxobject. probably the unique case when you might want to think about reference counting is when a string character is taken from a string which is not a constant (or a constant reference). in this case, due to c++ rules, the "read-only" operator[] (which is the same as getchar()) cannot be chosen and the "read/write" operator[] (the same as getwritablechar()) is used instead. as the call to this operator may modify the string, its data is unshared (cow is done) and so if the string was really shared there is some performance loss (both in terms of speed and memory consumption). in the rare cases when this may be important, you might prefer using getchar() instead of the array subscript operator for this reasons. please note that at() method has the same problem as the subscript operator in this situation and so using it is not really better. also note that if all string arguments to your functions are passed as const wxstring& (see the section some advice) this situation will almost never arise because for constant references the correct operator is called automatically.
tuning wxstring for your application
note: this section is strictly about performance issues and is absolutely not necessary to read for using wxstring class. please skip it unless you feel familiar with profilers and relative tools. if you do read it, please also read the preceding section about reference counting.
for the performance reasons wxstring doesn't allocate exactly the amount of memory needed for each string. instead, it adds a small amount of space to each allocated block which allows it to not reallocate memory (a relatively expensive operation) too often as when, for example, a string is constructed by subsequently adding one character at a time to it, as for example in:
// delete all vowels from the string
wxstring deleteallvowels(const wxstring& original)
{
wxstring result;
size_t len = original.length();
for ( size_t n = 0; n < len; n++ )
{
if ( strchr("aeuio", tolower(original[n])) == null )
result += original[n];
}
return result;
}
this is quite a common situation and not allocating extra memory at all would
lead to very bad performance in this case because there would be as many memory
(re)allocations as there are consonants in the original string. allocating too
much extra memory would help to improve the speed in this situation, but due to
a great number of wxstring objects typically used in a program would also
increase the memory consumption too much.the very best solution in precisely this case would be to use alloc() function to preallocate, for example, len bytes from the beginning - this will lead to exactly one memory allocation being performed (because the result is at most as long as the original string). however, using alloc() is tedious and so wxstring tries to do its best. the default algorithm assumes that memory allocation is done in granularity of at least 16 bytes (which is the case on almost all of wide-spread platforms) and so nothing is lost if the amount of memory to allocate is rounded up to the next multiple of 16. like this, no memory is lost and 15 iterations from 16 in the example above won't allocate memory but use the already allocated pool. the default approach is quite conservative. allocating more memory may bring important performance benefits for programs using (relatively) few very long strings. the amount of memory allocated is configured by the setting of extra_alloc in the file string.cpp during compilation (be sure to understand why its default value is what it is before modifying it!). you may try setting it to greater amount (say twice nlen) or to 0 (to see performance degradation which will follow) and analyse the impact of it on your program. if you do it, you will probably find it helpful to also define wxstring_statistics symbol 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 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). it goes without saying that a profiler should be used to measure the precise difference the change to extra_alloc makes to your program.
|