If one can't read older archives, its the result of
an oversight on our part.
In order to help us discover where the oversight
occurred the following
would be helpful.
a) information as to whether the problem occurs
only with binary archives
or with all types of archives.
b) Information as to which new version of the
serialization library has
manifested the problem. It could be the 1.35
in the trunk or it could be
1.36 at www.rrsd.com. Upon reading your post, it
has occurred to me that
a made a change in 1.36 that could cause this
behavior so I plan to look into
this. But I would like to know if it occurs
with 1.35 as well
c) It would be if you could submit a small
test case, including file
generated with previous version.
Robert Ramey
On Jan 5, 2008 11:16 PM, Robert Ramey <
ramey@rrsd.com> wrote:
Format for binary archives has changed starting
in 1.35. My guess is that the changes should should be made
conditional on the library version. I didn't make these changes but
I'll see that its looked into.
I
am currently using boost 1.34.0, and am using binary archives. If we release
software now that generates binary archives, and at a later stage, if we
upgrade the
boost version, will we not be able to read back the old binary
archives? How do we
ensure that on upgrading boost we can still read back
old binary archives?
Thanks
Mahesh
_______________________________________________
Boost-users mailing
list
Boost-users@lists.boost.org
http://lists.boost.org/mailman/listinfo.cgi/boost-users