The common pattern used upto now is to specify serialization in one of two ways: a) For standard library components: "boost/serialization/vector.hpp" - or complex.hpp, etc b) For other libraries "boost/date_time/serialization.hpp" In this way, the macro is redundant. Also, those that don't use serialization don't have any need to even look at the code to verifiy that it is benign as its not even included if they don't need it. Finally, it'll be easier to convince whomever you need to convince to add an optional header to the trunk than to patch some code that someone else will be maintaining. Finally, Finally, such patches (i.e. new headers) should include a new test in order to demonstrate that it is in fact correct. This should be added to the test suite of the particular library - in this case random. Robert Ramey Neal Becker wrote:
Please consider adding this patch to add serialization to mersenne_twister. Since it is only active if BOOST_SERIALIZE_TWISTER is defined, it is completely harmless to those who don't use it.
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost