21 Aug
2017
21 Aug
'17
6:29 a.m.
2017-08-20 0:46 GMT+02:00 Vladimir Batov via Boost
2) As I think I mentioned before impl_ptr is not part of any namespace by design... because the way proxy and implementation are connected, the specialization of impl_ptr<>::implementation. As I also mentioned it is IMO only a "problem" for "purists" but not for "practitioners" as from outside it is all kosher and accessed via boost::impl_ptr.
Could you summarize why using the global namespace is necessary? Is it only to be able to write template<> class _boost_impl_ptr_ instead of namespace boost { template<> class impl_ptr } or something more? Maybe it is described in the docs somewhere, but I couldn't find it. Regards, &rzej;