From: David Abrahams (dave_at_[hidden])
Date: 2006-05-24 20:38:35
David Abrahams <dave_at_[hidden]> writes:
> Aside from boost/pfto.hpp, there are several other examples of
> Boost.Serialization-specific functionality that was inappropriately
> pushed up into the top-level namespace. These headers are all in that
> category: boost/smart_cast.hpp, boost/state_saver.hpp,
> boost/static_warning.hpp, boost/strong_typedef.hpp.
> There is also at least one macro in that category: BOOST_EXPORT. That
> in particular seems likely to cause problems, because after all
> "export" is a keyword that's supported only on a few compilers and a
> natural stand-in, for those who want to support export, would be
> BOOST_EXPORT. This should've been BOOST_SERIALIZATION_EXPORT.
BOOST_DLLEXPORT, BOOST_USED, ...
> This is clearly a broad issue across the serialization library design,
> and I request that Robert examine these and any other instances of the
> problem and take whatever steps are practical to correct it. Because
> some of these names are in the library's public interface, that may
> require a plan that spans several Boost releases.
-- 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