|
| static bool | serialize (Archive &ar, T &v) |
| |
| template<typename A > |
| static bool | serialize (Archive &ar, T &v, boost::false_type, boost::true_type, A a) |
| |
| template<typename A > |
| static bool | serialize (Archive &ar, T &v, boost::true_type, boost::false_type, A a) |
| |
| static bool | serialize (Archive &ar, T &v, boost::false_type, boost::false_type, boost::false_type) |
| |
| static bool | serialize (Archive &ar, T &v, boost::false_type, boost::false_type, boost::true_type) |
| |
| static void | serialize_custom (Archive &ar, T &v, boost::true_type) |
| |
template<class Archive, class T>
struct serializer< Archive, T >
... wouldn't a class be better?
\detailed The logic behind serializing data. Places the archive data into the supplied parameter. This dispatches based on the supplied T template parameter's traits of is_blob_type or it is an integral (as defined by the is_integral trait). Depends on the Archive parameter to have overloaded the serialize_blob(T v, size_t size) and serialize_int(T v) base on which trait it applied. When the class has neither types, it falls to the overloaded method do_serialize(Archive ar) in T to do the work.
