Skip to content

Commit

Permalink
Maruku needs two spaces to indend sublists properly (see bhollis/maru…
Browse files Browse the repository at this point in the history
  • Loading branch information
esteve committed Dec 12, 2013
1 parent 2f113c6 commit a907426
Showing 1 changed file with 9 additions and 9 deletions.
18 changes: 9 additions & 9 deletions articles/serialization.md
Expand Up @@ -141,17 +141,17 @@ As the results of produce_consume_method and produce_consume_backend_plain show
Different serialization libraries specify different field type when e.g. generating C++ code for the messages. The major problem is the mapping between those types in an efficient manner. From a performance point of view the message interface should expose const references (especially to “big” fields). But those can only be mapped to the specific API of the serialization library if the types are exchangeable.
But for example a byte array is represented differently in C++ in the various serialization libraries:
- Protobuf:
- dyn. array<T>: RepeatedField<T> (STL-like interface)
- fix. array<T>: ---
- binary/string: std::string
- dyn. array<T>: RepeatedField<T> (STL-like interface)
- fix. array<T>: ---
- binary/string: std::string
- Thrift:
- dyn. array<T>: std::vector<T>
- fix. array<T>: ---
- binary/string: std::string
- dyn. array<T>: std::vector<T>
- fix. array<T>: ---
- binary/string: std::string
- ROS:
- array<T>: std::vector<T>
- fix. array<T, N>: boost::array<T, N>
- string: std::string
- array<T>: std::vector<T>
- fix. array<T, N>: boost::array<T, N>
- string: std::string

Furthermore the serialization library specific message API might not expose mutable access which could therefore not be provided by RO either when using pipeline C.

Expand Down

0 comments on commit a907426

Please sign in to comment.