Subject: Re: [boost] [uuid] Dependency on Boost.MPL & Boost.TypeTraits
From: Steven Maitlall (m.steven_at_[hidden])
Date: 2010-06-21 11:01:39
On Mon, Jun 21, 2010 at 10:45 AM, Vicente Botet Escriba <
> Kedar Bodas wrote:
> > Hello,
> > The <boost/uuid/uuid.hpp> header currently has a dependency on
> > <boost/mpl/bool.hpp> & <boost/type_traits/is_pod.hpp>. This is only used
> > to
> > declare the type_trait is_pod<uuids::uuid> AFAICT for the
> > uuid_serialize.hpp
> > header. No other part of the library seems to have any dependency on it.
> > Here's my problem:
> > By company policy I am not allowed to make any changes to a boost library
> > header. The MPL & type_traits libraries are not currently authorized for
> > use
> > within our code. This means I can't use Boost.Uuid either. Is it possible
> > for the above included headers to be enclosed within an inclusion guard
> > like
> > UUID_NO_TYPE_TRAITS_DEPENDENCY so that by defining this macro I can
> > this dependency without having to change the <boost/uuid/uuid.hpp>
> > Or better still since only uuid_serialize.hpp seems to need it this
> > dependency might be moved there. Since we don't use Boost.Serialization
> > our code this will solve my problem. This will also serve the purpose of
> > reducing the dependencies of the core part of the library and make it
> > modular.
> If you don't have a better response, you could stub these two files with
I wonder if that would fall under the policy of modifying boost files.
> BTW, why your company doesn't authorize the use of type_traits and mpl? You
> will have a lot of libraries that you can not use due to this dependency.
> View this message in context:
> Sent from the Boost - Dev mailing list archive at Nabble.com.
> Unsubscribe & other changes:
-- Steven Maraj http://www.marajservices.com
Boost list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk