Hi > Well I normally do, but since this is a project with WTL/ATL I > thought it would be easier to use CString since all WTL functions > take CString arguments, and that way I wouldn't have to do all the > ugly .c_str() thing every time. That and I like the .Format() way > better than std::ostringstream. I used to be very much against > CString as well but now that I've used it a bit more I can't really > think of any good reasons any more why to use std::string.
I don't think you'll find .Format() is type safe. Where as std::stringstream is. > Would it solve my problem? Dunno. I've never done any UNICODE programming. However, a good design would have all your back-end processing written in standard C++ seperate from your COM object (in a static lib or dll), so that you can unit test it easily without having to go through the COM layer. Then you should have the COM layer on to which takes the std::string from the backend processing and converts it where necessary. You should them have another set of unit tests for your COM stuff. Regards Paul Paul Grenyer Email: [EMAIL PROTECTED] Web: http://www.paulgrenyer.co.uk Have you met Aeryn: http://www.paulgrenyer.co.uk/aeryn/? Version 0.3.0 beta now available for download.
