On Jan 21, 2010, at 4:17 AM, Paul A. Bristow wrote:
-----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Beman Dawes Sent: Tuesday, January 19, 2010 1:13 PM To: Boost Developers List Subject: [boost] [inspect] More changes to Inspection Report
More changes to the Inspection Report:
* Apple macros clashes now show the specific name causing the problem.
It is clearly a nuisance for all Boost authors to avoid using the lowercase name 'check' - and even more to have to change code retrospectively.
I agree.
(It wouldn't be quite so bad of they had followed the UPPERCASE for MACROS convention, or if macros were namespaced).
There is a way to deal with this which doesn't require any code changes. The macros in question are defined in a file "/usr/include/AssertMacros.h", which is guarded by an #ifndef __ASSERTMACROS__ #define __ASSERTMACROS__ ...... #endif construct. If we were to define __ASSERTMACROS__ in the darwin.jam file, then these macros would never be defined. However, this could lead to other problems down the road. -- Marshall