From: David Abrahams (dave_at_[hidden])
Date: 2003-11-19 13:37:31
"John Maddock" <john_at_[hidden]> writes:
>> I guess that's their problem, since AFAICT we're unable to properly
>> detect all the conditions which say whether wchar_t is supported.
>> I'm sympathetic to users who want to do that, but we have one build
>> system which we're claiming to support. It seems to me that we
>> should support it, no?
> Yep, how about defining our own macro when wchar_t is really a type, and
> defining it in the build system, and documenting it as a user settable macro
> in the config system. How about BOOST_NATIVE_WCHAR_T for want of a better
I guess I need to know more details about what you're proposing, and
especially how it differs from what we have now.
> BTW the msvc toolset now has a <native-wchar_t> setting, maybe we could do
> the same for the Intel one?
I think it'd be a good idea, especially since most intel-win32 users
are expecting the compiler to emulate some version of msvc.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk