Glen Fernandes wrote:
What would be the most appropriate home for it? A Boost.AddressOf sub-module similar to Boost.Assert?
My initial idea was to extract Boost.Ref and move addressof there. It doesn't make much sense from a classification point of view... but boost::ref is a client of boost::addressof, libraries often use both and I've been (semi-officially) maintaining them, so... A separate module just for addressof also doesn't make much sense. Another candidate is probably Config, boost::addressof being ideally a one-liner that imports std::addressof. Unfortunately, some std::addressof implementations at this time tend to fail the boost::addressof tests so it's not that simple. :-) Andrey's suggested approach of tackling things from the other side and removing everything from Utility that depends on something other than Config also deserves consideration.