Wow this is greate information, helping a lot, I'm finding places where I can optimize using strings now, though still some are char*s. I prefer using a char* except when I gotta do a lot of manipulation on the string. That's where I'm converting it. Makes it much easier.
Using Dev-C++ on Windows
Not to advocate premature optimization here, but if you are doing a lot of conversion between the two forms, it'd probably be beneficial to stick to one (where possible). And, while a number of operations built into std::string are harder to accomplish with char*s, note that in a lot of cases, you can use STL algorithms on arrays (such as char*s), using the appropriate pointers to array elements as the iterators.
The word rap as it applies to music is the result of a peculiar phonological rule which has stripped the word of its initial voiceless velar stop.
>> if you're going to stick with char*...
vector<char>
>> ...which really ought to be limited to libraries and such that already have the dependency on C-style strings
Agreed!
>> but nothing really uses strings, so I just keep it char*s
>> [Problem is,] assigning [c_str()] to a non-const char*, which most of mine are.
Stop using char*'s then most won't be
If you find yourself using C-functions like strstr() or strchr() - ask yourself, "WWSD"?
If you don't know the C++ equivalent, or you think that the C equivalent is more efficient - post your scenario on this forum so others can have a crack at it.
gg
