Re: [boost] [serialization] string serialization

Subject: Re: [boost] [serialization] string serialization
From: Nikolay Mladenov (nikolay.mladenov_at_[hidden])
Date: 2009-03-04 15:58:52

On Wed, Mar 4, 2009 at 3:03 PM, Robert Ramey <ramey_at_[hidden]> wrote:
> 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.

Yes, but all optimizations are disabled.
And since I don need to handle endianness, this seems too costly.
I have taken care not have mismatched integer sizes in the objects I
am serializing,
But the binary_i(o)_archives are still forcing the size_t on me.

That is all.

I understand though, that changing the binary_i(o)_archive string
serialization to use
collection_size_type will break all existing 64 binary archives...

Nikolay Mladeonv

>
> 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
>
>
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
>