The current portable_binary_archive handles mismatched sizeof all types of integers. If the loading platform can't render the integer saved, an exception is thrown at runtime. Nikolay Mladenov wrote:
If you buy that, then you still need to construct a portable_binary_archive and handle container_size_type consistently across architectures (e.g. convert to uint64_t before/after storing/loading, checking for overflow on platforms where the in-memory container_size_type is smaller than the on-disk container_size_type). Then the difference is only that one currently requires an extra override for std::string.
As far as I can tell this is already done by the binary_archives.
Nikolay _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost