Le mar 02/03/2004 à 09:57, Pavel Vozenilek a écrit :
"Beman Dawes" <bdawes@acm.org> wrote
We deal with __GNUC__ inconsistently by defining BOOST_INTEL rather than BOOST_GCC.
BOOST_INTEL_LINUX and BOOST_INTEL_WIN32 please.
They are different animals and different set of bugs.
/Pavel
They are not totally different and have some bugs (or features) in common; it's the reason why BOOST_INTEL was added in the first place. There were places in Boost where there was this preprocessor test: #if defined(__ICL) || defined(__ICC) || defined(__ECC) || defined(__INTEL_COMPILER) Now it looks a bit saner thanks to BOOST_INTEL. If you want to add BOOST_INTEL_LINUX and BOOST_INTEL_WIN32 and BOOST_INTEL_??? (how do you call the macro for the HP/UX version of the compiler? and the other versions? Intel does a bit more than just supporting Linux and Windows), fine. But please don't remove BOOST_INTEL, it has its own utility. Regards, Guillaume