> Ok, > we're finally there. Setup now can use libstdc++ routines, > allowing the full range of C++ programming constructs. Probably even > exceptions, but I have not tested that yet. >
As the late Kool-Aid man once said, "OH YEAH!"! [snip] > We can also use the C++ string class. However, except for the trivial - > such as option parsing - we should still use the cistring or String++ > classes, as we need unicode support eventually, and also formatmessage > support. They can of course use string as an underlying container if > appropriate. > There's a cute 'trick' here that gives you the best of both worlds: typedef basic_string< TCHAR > StringAW; Now the "StringAW" type is either wide or narrow depending on build-time defines. -- Gary R. Van Sickle Brewer. Patriot.
