Re: [boost] Re: Better Intel-Win32 support

2003-06-06 Thread Beman Dawes
At 02:10 AM 6/5/2003, Daryle Walker wrote: On Wednesday, June 4, 2003, at 3:54 PM, Beman Dawes wrote: Hum... I just had a thought. Is it possible to detect if wchar_t is a typedef at compile time? Yes, I think so. Won't boost::is_same unsigned short, wchar_t ::value be true if wchar_t is a

Re: [boost] Re: Better Intel-Win32 support

2003-06-05 Thread John Maddock
Gak! These compiler vendors are going to drive us all crazy! What do they expect us to do, use ESP to know what compiler options are set? If you had ESP, then you would know the answer to that :- John. ___ Unsubscribe other changes:

Re: [boost] Re: Better Intel-Win32 support

2003-06-05 Thread Beman Dawes
At 07:58 AM 6/4/2003, John Maddock wrote: That will certainly work, but you shouldn't have to do that since the compiler itself defines _WCHAR_T_DEFINED. Since I made the fix earlier this afternoon I am able to compile some non-boost code correctly which had previously be failing. Just let

[boost] Re: Better Intel-Win32 support

2003-06-05 Thread Daryle Walker
On Wednesday, June 4, 2003, at 3:54 PM, Beman Dawes wrote: Hum... I just had a thought. Is it possible to detect if wchar_t is a typedef at compile time? Yes, I think so. Won't boost::is_same unsigned short, wchar_t ::value be true if wchar_t is a typedef, and false if a distinct type? I'll

Re: [boost] Re: Better Intel-Win32 support

2003-06-04 Thread John Maddock
That will certainly work, but you shouldn't have to do that since the compiler itself defines _WCHAR_T_DEFINED. Since I made the fix earlier this afternoon I am able to compile some non-boost code correctly which had previously be failing. Just let me jump in here: you absolutely can not use

[boost] Re: Better Intel-Win32 support

2003-06-04 Thread David Abrahams
Beman Dawes [EMAIL PROTECTED] writes: Hum... I just had a thought. Is it possible to detect if wchar_t is a typedef at compile time? Yes, I think so. Won't boost::is_same unsigned short, wchar_t ::value be true if wchar_t is a typedef, and false if a distinct type? Yes, but you can't use the

[boost] Re: Better Intel-Win32 support

2003-06-04 Thread David Abrahams
Beman Dawes [EMAIL PROTECTED] writes: So this is yet another case (like /Qoption,c,--arg_dep_lookup) where Boost config code just has to assume the option has been set. Well, the build system can tell boost what option's in use. That doesn't help users of other build systems, but I know that

Re: [boost] Re: Better Intel-Win32 support

2003-06-03 Thread Beman Dawes
At 07:02 AM 6/2/2003, David Abrahams wrote: Since I made the fix earlier this afternoon I am able to compile some non-boost code correctly which had previously be failing. What fix is that... Fixes to boost/config/compiler/intel.hpp. I just did a commit of that file that brings it into sync

[boost] Re: Better Intel-Win32 support

2003-06-02 Thread Pavel Vozenilek
Beman Dawes [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I'll try to trace where BOOST_NO_INTRINSIC_WCHAR_T is being set. I'm not so worried about ADL, at least with VC++ 7.1. You may look on test table http://aspn.activestate.com/ASPN/Mail/Message/boost/1614864. (Warning : when

[boost] Re: Better Intel-Win32 support

2003-06-02 Thread David Abrahams
Beman Dawes [EMAIL PROTECTED] writes: The fresh regression tests are now posted. Here is what changed in the Intel results, presumably as a result of the intel-win32 changes: New fails: config/limits_test integer/integer_traits_test

Re: [boost] Re: Better Intel-Win32 support

2003-06-02 Thread Beman Dawes
At 02:50 PM 6/1/2003, Pavel Vozenilek wrote: Beman Dawes [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I'll try to trace where BOOST_NO_INTRINSIC_WCHAR_T is being set. I'm not so worried about ADL, at least with VC++ 7.1. You may look on test table

[boost] Re: Better Intel-Win32 support

2003-06-02 Thread David Abrahams
Pavel Vozenilek [EMAIL PROTECTED] writes: Beman Dawes [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I'll try to trace where BOOST_NO_INTRINSIC_WCHAR_T is being set. I'm not so worried about ADL, at least with VC++ 7.1. You may look on test table

Re: [boost] Re: Better Intel-Win32 support

2003-06-02 Thread Beman Dawes
At 03:09 PM 6/1/2003, David Abrahams wrote: Pavel Vozenilek [EMAIL PROTECTED] writes: Beman Dawes [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I'll try to trace where BOOST_NO_INTRINSIC_WCHAR_T is being set. I'm not so worried about ADL, at least with VC++ 7.1. You may look

Re: [boost] Re: Better Intel-Win32 support

2003-06-02 Thread Beman Dawes
At 03:08 PM 6/1/2003, David Abrahams wrote: Beman Dawes [EMAIL PROTECTED] writes: The fresh regression tests are now posted. Here is what changed in the Intel results, presumably as a result of the intel-win32 changes: New fails: config/limits_test

[boost] Re: Better Intel-Win32 support

2003-06-02 Thread David Abrahams
Beman Dawes [EMAIL PROTECTED] writes: At 02:50 PM 6/1/2003, Pavel Vozenilek wrote: Beman Dawes [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I'll try to trace where BOOST_NO_INTRINSIC_WCHAR_T is being set. I'm not so worried about ADL, at least with VC++ 7.1.

[boost] Re: Better Intel-Win32 support

2003-06-02 Thread David Abrahams
Beman Dawes [EMAIL PROTECTED] writes: At 03:09 PM 6/1/2003, David Abrahams wrote: Pavel Vozenilek [EMAIL PROTECTED] writes: Beman Dawes [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] I'll try to trace where BOOST_NO_INTRINSIC_WCHAR_T is being set. I'm not so