Index: libs/serialization/doc/extended_type_info.html =================================================================== --- libs/serialization/doc/extended_type_info.html (révision 80815) +++ libs/serialization/doc/extended_type_info.html (copie de travail) @@ -309,7 +309,7 @@
-virtual void * destroy(void const * const ptr ) ) const;
+virtual void * destroy(void const * const ptr ) const;
-singleton<T>
-
-
-, the type T must be default constructable.
+singleton<T>, the type T must be default constructable.
It doesn't require static variables - though it may have them.
Since the library guarentees that only one instance of
-singleton<T>
-
-
+singleton<T>
and all accesss is through the above static interface
functions, common member functions of T become
the functional equivalent of
@@ -162,12 +157,12 @@
which contains the following code:
-typedef std::set ktmap;
+typedef std::set<const extended_type_info *, key_compare> ktmap;
...
void
extended_type_info::key_register(const char *key) {
...
- result = singleton::get_mutable_instance().insert(this);
+ result = singleton<ktmap>::get_mutable_instance().insert(this);
...
}
@@ -180,9 +175,7 @@
A second way is to use
-singleton<T>
-
-
+singleton<T>
as one of the base classes of the type. This is illustrated by a simplified
excerpt from
Index: libs/serialization/doc/tutorial.html
===================================================================
--- libs/serialization/doc/tutorial.html (révision 80815)
+++ libs/serialization/doc/tutorial.html (copie de travail)
@@ -327,7 +327,7 @@
classes to be serialized. This is referred to as "registration" or "export"
of derived classes. This requirement and the methods of
satisfying it are explained in detail
-here
+here.
All this is accomplished automatically by the serialization library. The above code is all that is necessary to accomplish