Ok, I came up with quite ugly solution (see on coliru http://coliru.stacked-crooked.com/a/ba39b5a242e5c69b). but it works, however it is ugly in the way that it is up to user to apply encode/decode on members. Moreover it is the only way to encode value. I was aiming to something broader, for example, in array or vector the size is stored in archive, it is size_t and it occupies 64 bit, in case of small data chunks it is complete waste of storage. Is there a way to force all primitive types of choice to use my serialization instead of standard one? I mean is there a way to encode this aforementioned size_t in array serialization without rewriting its implementation? -----Original Message----- From: Boost-users [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Bjorn Reese Sent: Sunday, November 22, 2015 5:14 PM To: boost-users@lists.boost.org Subject: Re: [Boost-users] Extend boost binary serialization with varints encoding On 11/22/2015 12:35 PM, Ernest Zaslavsky wrote:
Is it feasible to provide boost binary serialization with varint encoding capabilities?
Yes, see: http://www.boost.org/boost/multiprecision/cpp_int/serialize.hpp _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users