Verify that string encoding change complies to TIDELog specification
|Target version:||Robotics Service Bus - rsb-0.10|
The publicly available version of the TIDELog specification is unclear regarding length fields for strings (in this case taken from the table specifying the CHAN block):
Name size 1 unsigned byte Length of the channel name. Name ``Name size`` characters Name of the channel, as a character string.
"``Name size`` characters" requires a string encoding to be specified. Alternative, "``Name size`` bytes" could be the intended meaning.
In both cases, clarification is needed.
Fixed length computation for strings in src/backend/tidelog/generator.lisp
This is a very unsatisfying change because the TIDELog specifications
explicitly states that length fields for strings specify the number of
characters. But since no encoding is specified, they probably meant
the number of bytes.
- src/backend/tidelog/generator.lisp (type-spec->serializer/buffer):
use number of bytes instead of number of characters as "length" of