22 Sep
2007
22 Sep
'07
9:27 a.m.
David Abrahams wrote:
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?
Nope, still sitting on my hard drive, OK I'll commit and hope it doesn't cause any catastrophic issues :-) John.