Re: [Boost-users] serialization of vectors somehow odd

From: Matthias Troyer (troyer_at_[hidden])
Date: 2008-08-01 12:15:57

Hi Sebastian,

Indeed, the item version appeared in 1.34 even for primitive types,  
and as you point out correctly, not as a BOOST_STRONG_TYPEDEF. At the  
same time I optimized the array serialization, and with the two  
developments going in parallel I missed this small change in 1.34, so  
that while 1.35 and 1.34 are both compatible with all versions prior  
to 1.33, they are not mutually compatible. For 1.36 it was decided to  
have compatibility to 1.34 and earlier, and have the workaround for  
1.35. It was too late to do any major change like you suggest, but my  
plan for 1.37  is indeed to make this a BOOST_STRONG_TYPEDEF so that  
it can be filtered, and actually to skip it for all non-versioned types.

I would recommend you to use the vector_135.hpp header for now.

Matthias

On 1 Aug 2008, at 06:21, Sebastian Weber wrote:

> Hi!
>
> I just switched to the new 1.36.0 beta release and was very confused  
> by
> the  new scheme how optimized arrays are handled within archives as I
> have implemented an HDF5 archive by myself. After a while I found out
> how to fix it by browsing SVN changesets - is there some documentation
> about it I overlooked? Well, now I even see that I have to include
> serialization/vector_135.hpp to avoid this strange item_version tag to
> appear which distracts my archives. This is fine, but this is a
> meta-information, wouldn't it be possible to use some
> BOOST_STRONG_TYPEDEF to inject this item_version variable as some
> specific meta-type which I can then filter in my archive?
>
> Greetings,
>
> Sebastian
>
> _______________________________________________
> Boost-users mailing list
> Boost-users_at_[hidden]
> http://lists.boost.org/mailman/listinfo.cgi/boost-users