Matthias Troyer wrote: > > On Tuesday, May 27, 2003, at 05:44 PM, John Torjo wrote: > >>>> - does not work for wchar_t. While this might seem silly, it's not, >> since >>>> VC allows for a TCHAR* command line string. >>> >>> I have to consider this. An obvious approach would be to add template >>> parameter to every class, telling which char type to use. So >>> investigation >>> is needed to find alternatives --- making everything a template would >>> conflict with ability to compiler everything as shared library. >>> >> >> I don't think we need a template param. >> Just something like 'boost::program_options::char_type', which is by >> default >> char, and can be changed. >> >> It's not like we have multiple command lines or something ;-) > > We could have some programs that use plain ASCII characters, and some > programs that want to support Unicode filenames. We should thus still > have support for both narrow and wide characters, and not just one > character type.
I think the point is that you hardly want both ascii and unicode in single program. In that case two versions of shared library can be built: for ascii and unicode, and you will link to the desired one. It's actually not necessary to add templates --- probably preprocessor will do. - Volodya _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
