From: David Abrahams (dave_at_[hidden])
Date: 2005-03-03 14:33:37
"Thorsten Ottosen" <nesotto_at_[hidden]> writes:
> "Jody Hagins" <jody-boost-011304_at_[hidden]> wrote in message
> | In range/config.hpp, I see this code...
> | #if BOOST_WORKAROUND(__BORLANDC__, BOOST_TESTED_AT(0x564))
> | #define BOOST_RANGE_DEDUCED_TYPENAME
> | #else
> | #define BOOST_RANGE_DEDUCED_TYPENAME BOOST_DEDUCED_TYPENAME
> | #endif
> | Why is there a special version of this?
> I guess the explanation would be historic reasons, I used it in some
> workaround code. It will go away in the next release.
It's on my outstanding mental list of Boost-wide changes that
BOOST_DEDUCED_TYPENAME should be changed simply to BOOST_TYPENAME,
because it's used in all kinds of contexts where there's no deduction
involved. Older compilers simply need a disappearing "typename"
keyword, and that's the role that it fills.
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk