[Note: this is a dark corner of the language, and the - corresponding issue has not been resolved yet.] +
[Note: this is a dark corner of the language, and the + corresponding issue has only recently been resolved.]
namespace boost{ namespace regex_constants{
-typedef implemenation-specific-bitmask-type match_flag_type;
+typedef implementation-specific-bitmask-type match_flag_type;
static const match_flag_type match_default = 0;
static const match_flag_type match_not_bob;
Index: libs/serialization/doc/archive_reference.html
===================================================================
RCS file: /cvsroot/boost/boost/libs/serialization/doc/archive_reference.html,v
retrieving revision 1.2
diff -u -p -b -B -r1.2 archive_reference.html
--- libs/serialization/doc/archive_reference.html 19 Jul 2004 07:00:00 -0000 1.2
+++ libs/serialization/doc/archive_reference.html 20 Jul 2004 15:21:17 -0000
@@ -173,7 +173,7 @@ implement partial function template orde
The serialization library injects bookkeeping data into the serialization archive.
This data includes things like object ids, version numbers, class names etc. Each
of these objects is included in a wrapper so that the archive class can override the
-implemenation of void load_override(T & t, int);.
+implementation of void load_override(T & t, int);.
For example, in the XML archive, the override for this type renders an object_id equal to 23 as
"object_id=_23". The following table lists the types used by the serialization library:
@@ -284,7 +284,7 @@ typedef boost::archive::text_oarchive te
typedef std::ofstream test_ostream;
// repeat the above for input archive
-#include <boost/archive/text_iarchive.hpp>
+#include <boost/archive/text_iarchive.hpp>
typedef boost::archive::text_iarchive test_iarchive;
typedef std::ifstream test_istream;
@@ -347,7 +347,7 @@ show how polymorphic archives are to be
demo_polymorphic_A.hpp and
demo_polymorphic_A.cpp
-contain no templates and no reference to any specific archive implemenation. That is, they will
+contain no templates and no reference to any specific archive implementation. That is, they will
only have to be compiled once for all archive implementations. The even applies to archives classes
created in the future.
demo_polymorphic.cpp
@@ -361,7 +361,7 @@ accomplished by the templates
polymorphic_iarchive_impl.hpp
and
polymorphic_oarchive_impl.hpp.
-As these contain no code specific to the particular implemenation archive, they can be used to create
+As these contain no code specific to the particular implementation archive, they can be used to create
a polymorphic archive implementation from any functioning templated archive implementation.
As a convenience, small header files have been included which contain Index: libs/serialization/doc/headers.html =================================================================== RCS file: /cvsroot/boost/boost/libs/serialization/doc/headers.html,v retrieving revision 1.2 diff -u -p -b -B -r1.2 headers.html --- libs/serialization/doc/headers.html 19 Jul 2004 07:00:00 -0000 1.2 +++ libs/serialization/doc/headers.html 20 Jul 2004 15:21:17 -0000 @@ -269,8 +269,8 @@ boost/archive/basic_text_iprimitive.hpp
template<class Archive, class T>
inline void serialize(
- Archive & ar,
- T & t,
+ Archive & ar,
+ T & t,
const unsigned long int file_version
){
// invoke member function for class T
@@ -67,7 +67,7 @@ or loaded from an archive. The default
existence of a class member function template of the following signature:
template<class Archive>
-void serialize(Archive &ar, const unsigned int version){
+void serialize(Archive &ar, const unsigned int version){
...
}
@@ -88,14 +88,14 @@ saving data to an archive as well as loa
The key is that the & operator is
defined as <<
for output archives and as >> input archives. The
-"polymorphic" behavior of the & permits the same template
+"polymorphic" behavior of the & permits the same template
to be used for both save and load operations. This is very convenient in that it
saves a lot of typing and guarantees that the saving and loading of class
data members are always in sync. This is the key to the whole serialization
system.
Free Function
-Of course we're not restricted to using the default implemenation described
+Of course we're not restricted to using the default implementation described
above. We can override the default one with our own. Doing this will
permit us to implement serialization of a class without altering
the class definition itself. We call this non-intrusive
@@ -107,8 +107,8 @@ namespace serialization {
template<class Archive>
inline void serialize(
- Archive & ar,
- my_class & t,
+ Archive & ar,
+ my_class & t,
const unsigned long int file_version
){
...
@@ -145,7 +145,7 @@ should be serialized with the following
{
// invoke serialization of the base class
- ar & boost::serialization::base_object<base_class_of_T>(*this);
+ ar & boost::serialization::base_object<base_class_of_T>(*this);
// save/load class member variables
ar & member1;
ar & member2;
@@ -173,7 +173,7 @@ The current version of the class is assi
{
// invoke serialization of the base class
- ar & boost::serialization::base_object<base_class_of_T>(*this);
+ ar & boost::serialization::base_object<base_class_of_T>(*this);
// save/load class member variables
ar & member1;
ar & member2;
@@ -194,7 +194,7 @@ the header file
namespace boost { namespace serialization {
template<class Archive>
-void save(Archive & ar, const my_class & t, unsigned int version)
+void save(Archive & ar, const my_class & t, unsigned int version)
{
...
}
template<class Archive>
-void load(Archive & ar, my_class & t, unsigned int version)
+void load(Archive & ar, my_class & t, unsigned int version)
{
...
}
@@ -264,8 +264,8 @@ and override the free boost::shared_ptr<T> and for
+definition of serialization for boost::shared_ptr<T> and for
std::list<T>. If I have defined serialization for my own
class my_t, then serialization for
std::list< boost::shared_ptr< my_t> > is already available
@@ -503,9 +503,9 @@ serializable types. That is, if T is a s
is automatically available and will function as expected:
T t[4];
-ar << t;
+ar << t;
...
-ar >> t;
+ar >> t;
The facilities described above are sufficient to implement
serialization for all STL containers. In fact, this has been done
Index: libs/serialization/doc/traits.html
===================================================================
RCS file: /cvsroot/boost/boost/libs/serialization/doc/traits.html,v
retrieving revision 1.2
diff -u -p -b -B -r1.2 traits.html
--- libs/serialization/doc/traits.html 19 Jul 2004 07:00:00 -0000 1.2
+++ libs/serialization/doc/traits.html 20 Jul 2004 15:21:17 -0000
@@ -388,13 +388,13 @@ the same across all known platforms.
The signature for the traits template is:
-template<
+template<
class T,
int Level,
int Tracking,
unsigned int Version = 0,
class ETII = BOOST_SERIALIZATION_DEFAULT_TYPE_INFO(T)
->
+>
struct traits
and template parameters should be assigned according to the following table:
@@ -402,7 +402,7 @@ and template parameters should be assign
parameter description permitted values default value Ttarget class class name none Levelimplemenation level not_serializable
primitive_type
object_serializable
object_class_infonone Levelimplementation level not_serializable
primitive_type
object_serializable
object_class_infonone Trackingtracking level track_never
track_selectivly
track_alwaysnone Versionclass versionunsigned integer 0ETTItype_info implementationextended_type_info_typeid
extended_type_info_no_rttidefault type_info implementation
Index: libs/test/src/supplied_log_formatters.cpp
===================================================================
RCS file: /cvsroot/boost/boost/libs/test/src/supplied_log_formatters.cpp,v
retrieving revision 1.11
diff -u -p -b -B -r1.11 supplied_log_formatters.cpp
--- libs/test/src/supplied_log_formatters.cpp 19 Jul 2004 12:09:25 -0000 1.11
+++ libs/test/src/supplied_log_formatters.cpp 20 Jul 2004 15:21:18 -0000
@@ -9,7 +9,7 @@
//
// Version : $Revision: 1.11 $
//
-// Description : implemets Unit Test Log formatters
+// Description : implements Unit Test Log formatters
// ***************************************************************************
// Boost.Test
Index: libs/test/src/test_tools.cpp
===================================================================
RCS file: /cvsroot/boost/boost/libs/test/src/test_tools.cpp,v
retrieving revision 1.34
diff -u -p -b -B -r1.34 test_tools.cpp
--- libs/test/src/test_tools.cpp 19 Jul 2004 12:08:48 -0000 1.34
+++ libs/test/src/test_tools.cpp 20 Jul 2004 15:21:18 -0000
@@ -10,7 +10,7 @@
//
// Version : $Revision: 1.34 $
//
-// Description : supplies offline implemtation for the Test Tools
+// Description : supplies offline implementation for the Test Tools
// ***************************************************************************
// Boost.Test