Changes between Version 4 and Version 5 of Documentation/Serialization

Timestamp:

Feb 4, 2010, 6:33:55 PM (15 years ago)

Author:

Christoph Mayer

Comment:

--

Documentation/Serialization

@@ -79 +79 @@
  * string and char* support, T( char* | std::string )
 
-It is always best to use types that have a specified length, e.g. {{{uint8_t}}}, {{{uint16_t}}}, ... etc. If you are serializing through a 
+It is always best to use types that have a specified length, e.g. {{{uint8_t}}}, {{{uint16_t}}}, ... etc. If you are serializing through a inherited type where the serialization is provided in the base class, use the {{{&}}} operator before. Such a case is e.g. the {{{NodeID}}} class:
+{{{
+#!cpp
+NodeID n;
+SpoVNetID s
+...
+sznBeginDefault( Classname, X ) {
+        X && &n && &s;
+} sznEnd();
+}}}
 
-
-In your {*.cpp} class you  require a further macro. In case of the !PingPong sample this is simply:
+In your {{{*.cpp}}} class you  require a further macro. In case of the !PingPong sample this is simply:
 {{{
 #!cpp
 vsznDefault(PingPongMessage);
 }}}
+
+
+
+
+if (X.isDeserializer())
 
 
@@ -99 +112 @@
 
 
+{{{
+#!comment
 
 Non-virtual inline serialization is reasonable on small or bit-sensitive objects (for example IP-Adresses, Ports etc.).
@@ -159 +174 @@
 == Message specification, serialization and deserialization ==
 
-
+}}}