From: Joerg Walter (jhr.walter_at_[hidden])
Date: 2002-12-05 15:15:30
----- Original Message -----
From: "David Abrahams" <dave_at_[hidden]>
To: "boost" <boost_at_[hidden]>
Sent: Wednesday, December 04, 2002 9:27 PM
Subject: [boost] [Config] Testing instructions for compiler vendors
>
> Hi,
>
> I'm trying to come up with instructions for compiler vendors who want
> to use Boost to test their compilers. What preprocessor symbols do
> they need to define? So far, it looks like:
>
> - BOOST_NO_COMPILER_CONFIG
> - BOOST_NO_STDLIB_CONFIG - if they want to check the library
> - BOOST_STRICT_CONFIG - to disable some checks in source code
> - macros for any known-not-implemented features,
> e.g. BOOST_NO_TEMPLATE_TEMPLATES.
>
> Right?
>
> Questions:
>
> 1. Should we do something to make this easier for them?
No. We should focus on serving our users.
> 2. What about all the places we make compiler-specific checks in
> Boost code? Could we define some macros which make it easier
> and less error-prone to write these, and which can be globally
> turned off when needed?
>
> # if BOOST_COMPILER_WORKAROUND(__SUNPRO_CC, <= 0x540)
> ...
> #else
> ...
> #endif
I'm sometimes not even able to decide who is wrong ;-(
Best regards
Joerg