How to serialize User-Defined Structures in the libnop library?

[google]

How to serialize User-Defined Structures in the libnop library?

[eieio]

It's perfectly fine to ask questions here. :-)

First off, your structure definition looks correct. I don't think this is the problem.

I'm not sure how you got a payload of 13 bytes with double as a key and having a double in your element structure. A double always costs 9 bytes in serialized format, and since you have one for the map key and one in the element, the serializer should produce more than 18 bytes for this input, guaranteed.

Second, when I make a reproduction case that does not include file IO things seem to work fine. Take a look at this example: https://godbolt.org/z/6eYiXd

I suspect your data is getting truncated. You should make sure your file IO is correct in both directions.

The actual serialized data bytes should be: BB 01 89 00 00 00 00 00 00 04 40 B9 02 89 00 00 00 00 00 00 1A 40 01.

If you truncate to the first 14 bytes and then zero filled the rest it would look like this: BB 01 89 00 00 00 00 00 00 04 40 B9 02 89 00 00 00 00 00 00 00 00 00.

I'm not quite sure why this is happening, but it does seem to explain the result you got. Your file IO is probably the culprit here.

To make things simpler, you can build a nop::Serializer<nop::StreamWriter<std::ofstream>> and a nop::Deserializer<nop::StreamReader<std::ifstream>> directly and avoid the intermediate std::stringstream and std::string buffer. This might address the file IO issues you are having.

Lastly, you should avoid using double for the key of std::map. A small change in value due to limited accuracy/rounding during double precision floating point computations would result in the wrong element being indexed or std::map::find() failing to locate a previously inserted element. If you need to represent money values you should use a decimal type, which is usually based on an integer.

Best,
Corey