From: John Maddock (john_at_[hidden])
Date: 2004-11-20 05:56:18
> I appreciate that this case is somewhat handled by the compatibility
> header, but this isn't always an available solution. We were able to
> change headers, so this problem was solved, but this may not always be
> possible (ie third party software). Perhaps the developers could include
> some protection against this kind of error by checking to see if
> the offending constants are defined before the boost declarations are
> made and #undef-ing them as needed. This kind of error can be difficult
> to track down in mid-large projects.
I am aware of this snag: I hope to have a reasonable solution in place for
Boost-1.33.
John.