If your goal is to have fewer warnings then you should fix the causes of
warnings (probably using const char* instead of char* in most places).
Yes, using C strings doesn't mean you should have compiler warnings;
something else is wrong.
If you want to convert to std::string you can replace all "char *" with
"const std::string&", then fix compiling errors, then fix unit test errors.
Perhaps a bit too naive approach, and I'm pretty sure he has no unit
tests. (You could argue that he should create them, or not rewrite the
code using std::string.)
I'd try it on a piece of the code first -- in some of the classes for
example. And I would first analyze the code for:
- use of C-style casts (gcc can warn for them)
- use of memcpy(), bzero(), memset() and the other functions which
you cannot safely use on objects
/Jorgen