From: David Abrahams (dave_at_[hidden])
Date: 2007-09-21 14:31:30
on Mon Sep 10 2007, "John Maddock" <john-AT-johnmaddock.co.uk> wrote:
> I've had a chance to look at this again, and have what seems to be a
> workable solution: however since the fix involves checking to see whether a
> define is set or not and then setting a guard macro appropriately - in order
> to suppress warnings from Boost.Config defined macros - I've had to include
> boost/config.hpp in workaround.hpp. Is this acceptable
It's OK with me. Did you ever check this change in?
-- Dave Abrahams Boost Consulting http://www.boost-consulting.com The Astoria Seminar ==> http://www.astoriaseminar.com