Joaquín Mª López Muñoz wrote:
Hello Robert,
and want to serialize objects of type mic_t, you'd have (according to the serialization header model) to include the following:
#include <boost/multi_index/serialization.hpp> #include <boost/multi_index/serialization/ordered_index.hpp> #include <boost/multi_index/serialization/hashed_index.hpp> #include <boost/multi_index/serialization/sequenced_index.hpp>
I would have had each more specialized one include the common one so it would look like #include <boost/multi_index/serialization/ordered_index.hpp> #include <boost/multi_index/serialization/hashed_index.hpp> #include <boost/multi_index/serialization/sequenced_index.hpp>
Which looks like excessively cumbersome to me.
And that's where we differ. The above seems totally natural to me. It goes with my normal expectation that to get more features, I have to add more "stuff" so that I know that my program is using - and only using - what I think it is.
Failing to include one of the headers won't result in less-capable serialization support, only in a compile-time error when trying to stream mic_t's.
Agreed - Its not a huge issue for me. I would say its more of a strong personal preference. Robert Ramey