[Boost-users] [tr1/config] portably including unordered_<X>

Subject: [Boost-users] [tr1/config] portably including unordered_<X>
From: Jim Bell (Jim_at_[hidden])
Date: 2011-02-28 12:45:20

It appears that <boost/tr1/unordered_X.hpp> includes the native
<unordered_X> when Boost.config says it's able.

So if one were writing a portable library that uses boost (or bug-fixing
an existing boost component), would including
<boost/tr1/unordered_X.hpp> be the way to bring it in, or should one
look at BOOST_HAS_TR1_UNORDERED_SET and make a decision that way?

There's no mechanism analogous to BOOST_HAS_HASH / BOOST_HASH_<X>_HEADER
that has to be navigated, right?