[Boost.Serialization] Questions about the New Release of Boost.Serialization 1.36
Hello, This mail is about Boost.Serialization and more specifically the new release of this library, tagged as 1.36, which can be found via the link: www.rrsd.com <http://www.rrsd.com/> ; I've found this link into a specific thread about Serialization and multi-threading. Last week, I've downloaded this new release and tested it in my environment - Windows XP and Visual C++ 7.1.6030; the compilation was done against Boost.1.34.1 trunk and was running with success but I've noticed that some, "not all", old binary archives generated w/ Boost.Serialization 1.34.1 can't be restored with this new version of Boost.Serialization. When I compare the binary files with a file binary comparison software utility it seems that the binary formats between these two versions are not comparables. I would like to know if this behaviour is "normal": i.e. the binary formats between 1.34.1 and 1.36 are not strictly equivalent and that an old binary archive can be declare "not compatible" w/ the 1.36 release. Is this right? Furthermore, is it possible to have the same behaviour w/ an XML or Text Archive format? Could we guarantee a sort of compatibility in the future? And more generally speaking, what is the policy for insuring compatibility between new releases of Boost.Serialization? Best regards, Marc VIALA
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. Text and XML archives shouldn't be affected. That is, archives created by any previous version of the serialization library should be readable by any subsequent version of the library. If this is not the case, please let us know. Thanks for testing this. Robert Ramey "Marc Viala Perso" <marc.viala@tele2.fr> wrote in message news:002101c84fae$ec9a5420$0201a8c0@acticm.com... Hello, This mail is about Boost.Serialization and more specifically the new release of this library, tagged as 1.36, which can be found via the link: www.rrsd.com; I've found this link into a specific thread about Serialization and multi-threading. Last week, I've downloaded this new release and tested it in my environment - Windows XP and Visual C++ 7.1.6030; the compilation was done against Boost.1.34.1 trunk and was running with success but I've noticed that some, "not all", old binary archives generated w/ Boost.Serialization 1.34.1 can't be restored with this new version of Boost.Serialization. When I compare the binary files with a file binary comparison software utility it seems that the binary formats between these two versions are not comparables. I would like to know if this behaviour is "normal": i.e. the binary formats between 1.34.1 and 1.36 are not strictly equivalent and that an old binary archive can be declare "not compatible" w/ the 1.36 release. Is this right? Furthermore, is it possible to have the same behaviour w/ an XML or Text Archive format? Could we guarantee a sort of compatibility in the future? And more generally speaking, what is the policy for insuring compatibility between new releases of Boost.Serialization? Best regards, Marc VIALA ------------------------------------------------------------------------------ _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
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.
Could you please elaborate on this a bit? 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
On 6 Jan 2008, at 05:37, Mahesh Venkitachalam wrote:
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.
Could you please elaborate on this a bit?
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?
Actually as far as I can see the format should not have changed. Could you please send examples that show a difference? Matthias
On Jan 6, 2008 7:45 PM, Matthias Troyer <troyer@phys.ethz.ch> wrote:
On 6 Jan 2008, at 05:37, Mahesh Venkitachalam wrote:
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.
Could you please elaborate on this a bit?
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?
Actually as far as I can see the format should not have changed. Could you please send examples that show a difference?
Matthias
I am yet to use anything but 1.34.0. The original poster of this thread, Marc Viala, is the one who noticed a change - perhaps he will post an example? Thanks Mahesh
I am yet to use anything but 1.34.0. The original poster of this thread, Marc Viala, is the one who noticed a change - perhaps he will post an example? [Marc Viala] Before any thing, thanks to all for tackling my problem and sorry for the delay of my reply but I was not able to have an Internet access during the last days. I can send some sample test to demonstrate the problem of serialization/deserialization with mixed versions of Boost.Serialization 1.34.1 vs 1.36 (from www.rrsd.com), but maybe this is not necessary thanks to the work of Richard on this thread: http://article.gmane.org/gmane.comp.lib.boost.user/32620 ? For Matthias: from my side, I didn't notice any trouble when using XML archives with Boost.Serialization 1.36
We're still trying to figure out if this is specific to binary archives or is common to all archives. robert ramey Marc Viala Perso wrote:
I am yet to use anything but 1.34.0. The original poster of this thread, Marc Viala, is the one who noticed a change - perhaps he will post an example?
[Marc Viala] Before any thing, thanks to all for tackling my problem and sorry for the delay of my reply but I was not able to have an Internet access during the last days. I can send some sample test to demonstrate the problem of serialization/deserialization with mixed versions of Boost.Serialization 1.34.1 vs 1.36 (from www.rrsd.com), but maybe this is not necessary thanks to the work of Richard on this thread: http://article.gmane.org/gmane.comp.lib.boost.user/32620 ? For Matthias: from my side, I didn't notice any trouble when using XML archives with Boost.Serialization 1.36
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
This should be fixed now. Can you try again? On 9 Jan 2008, at 22:02, Marc Viala Perso wrote:
I am yet to use anything but 1.34.0. The original poster of this thread, Marc Viala, is the one who noticed a change - perhaps he will post an example?
[Marc Viala] Before any thing, thanks to all for tackling my problem and sorry for the delay of my reply but I was not able to have an Internet access during the last days. I can send some sample test to demonstrate the problem of serialization/deserialization with mixed versions of Boost.Serialization 1.34.1 vs 1.36 (from www.rrsd.com), but maybe this is not necessary thanks to the work of Richard on this thread: http://article.gmane.org/gmane.comp.lib.boost.user/32620 ? For Matthias: from my side, I didn't notice any trouble when using XML archives with Boost.Serialization 1.36 <winmail.dat>_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
bounces@lists.boost.org] De la part de Matthias Troyer Envoyé : jeudi 10 janvier 2008 12:56
This should be fixed now. Can you try again?
On 9 Jan 2008, at 22:02, Marc Viala Perso wrote:
Thanks, But the patch is available for Boost.Serialization 1.36 (link www.rrsd.com) or for Boost.Serialization 1.35 on the current SVN Trunk? And where can we get the patch? Best regards, Marc VIALA
On 10 Jan 2008, at 14:01, Marc Viala Perso wrote:
bounces@lists.boost.org] De la part de Matthias Troyer Envoyé : jeudi 10 janvier 2008 12:56
This should be fixed now. Can you try again?
On 9 Jan 2008, at 22:02, Marc Viala Perso wrote:
Thanks,
But the patch is available for Boost.Serialization 1.36 (link www.rrsd.com ) or for Boost.Serialization 1.35 on the current SVN Trunk? And where can we get the patch?
It is on the trunk, the release branch and the serialization_next_release branch of the Boost subversion repository. Matthias
Marc Viala Perso wrote:
bounces@lists.boost.org] De la part de Matthias Troyer Envoyé : jeudi 10 janvier 2008 12:56
This should be fixed now. Can you try again?
On 9 Jan 2008, at 22:02, Marc Viala Perso wrote:
Thanks,
But the patch is available for Boost.Serialization 1.36 (link www.rrsd.com) or for Boost.Serialization 1.35 on the current SVN Trunk? And where can we get the patch?
I'll merge in the changes in the trunk to 1.36 and upload a new version. But this will take a few days. Robert Ramey
Best regards,
Marc VIALA
bounces@lists.boost.org] De la part de Robert Ramey Envoyé : vendredi 11 janvier 2008 02:45
Marc Viala Perso wrote:
bounces@lists.boost.org] De la part de Matthias Troyer Envoyi : jeudi 10 janvier 2008 12:56
This should be fixed now. Can you try again?
On 9 Jan 2008, at 22:02, Marc Viala Perso wrote:
Thanks,
But the patch is available for Boost.Serialization 1.36 (link www.rrsd.com) or for Boost.Serialization 1.35 on the current SVN Trunk? And where can we get the patch?
I'll merge in the changes in the trunk to 1.36 and upload a new version.
But this will take a few days.
[Marc Viala] Ok, I'll be waiting for an email notification from you before restarting some tests on the Boost 1.36. Thanks to all for handling this problem.
Thanks for the quick turnaround, Matthias! I downloaded and tested SVN Trunk (version 1.35): Looks like the problem has been resolved! As for XML serialization, we do use it in one place in our code, but development issues here have hindered me from actually testing it. Once I am able to, I'll post the result. Marc, I can't take credit for the test program. A co-worker of mine, Phil Hartmann, actually created it. He was also gracious enough to allow the zip file to be posted on his website. Thanks, Phil! Rich Turrin
On Thursday, January 10, 2008 6:56 AM, Matthias Troyer wrote:
This should be fixed now. Can you try again?
On 9 Jan 2008, at 22:02, Marc Viala Perso wrote:
I am yet to use anything but 1.34.0. The original poster of this thread, Marc Viala, is the one who noticed a change - perhaps he will post an example?
[Marc Viala] Before any thing, thanks to all for tackling my problem and sorry for the delay of my reply but I was not able to have an Internet access during the last days. I can send some sample test to demonstrate the problem of serialization/deserialization with mixed versions of Boost.Serialization 1.34.1 vs 1.36 (from www.rrsd.com), but maybe this is not necessary thanks to the work of Richard on this thread: http://article.gmane.org/gmane.comp.lib.boost.user/32620 ? For Matthias: from my side, I didn't notice any trouble when using XML archives with Boost.Serialization 1.36
_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users
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 "Mahesh Venkitachalam" <mkvenkit.vc@gmail.com> wrote in message news:6164abb70801052037t7f3cbf62pb8856e893ffa8204@mail.gmail.com... 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. Could you please elaborate on this a bit? 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
Hi, I might be able to offer something for (b) and (c) below. We're experiencing issues here in our development process, serializing in files using version 1.35 of Boost (retrieved on 18 December, 2007 @ 4:09 pm) that were serialized out with version 1.34.1. We ran a sample test program that crashed when attempting to serialize in from a sample file. There is a zip file containing this program and a sample data file created using version 1.34.1: http://www.toadsoftware.com/boost/TestBoostSerialize.zip. There is one caveat: In our development process, we are using Visual Studio 2008 with a two-byte alignment setting. We also manually built the Boost library from the SVN Trunk with modified abi prefix and suffix header files to use two-byte packing as well. Let me know if you need more information. Hope this is useful in some way. Rich Turrin On Jan 6, 2008 1:33 PM, Robert Ramey wrote:
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
"Mahesh Venkitachalam" <mkvenkit.vc@gmail.com> wrote in message news:6164abb70801052037t7f3cbf62pb8856e893ffa8204@mail.gmail.com...
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.
Could you please elaborate on this a bit?
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
Thanks. Do you have problems also when using XML or test archives or just when using binary archives? Matthias On 7 Jan 2008, at 22:46, Richard Turrin wrote:
Hi,
I might be able to offer something for (b) and (c) below. We're experiencing issues here in our development process, serializing in files using version 1.35 of Boost (retrieved on 18 December, 2007 @ 4:09 pm) that were serialized out with version 1.34.1. We ran a sample test program that crashed when attempting to serialize in from a sample file. There is a zip file containing this program and a sample data file created using version 1.34.1: http://www.toadsoftware.com/boost/TestBoostSerialize.zip .
There is one caveat: In our development process, we are using Visual Studio 2008 with a two-byte alignment setting. We also manually built the Boost library from the SVN Trunk with modified abi prefix and suffix header files to use two-byte packing as well.
Let me know if you need more information. Hope this is useful in some way.
Rich Turrin
On Jan 6, 2008 1:33 PM, Robert Ramey wrote:
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
"Mahesh Venkitachalam" <mkvenkit.vc@gmail.com> wrote in message news:6164abb70801052037t7f3cbf62pb8856e893ffa8204@mail.gmail.com ...
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.
Could you please elaborate on this a bit?
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
participants (1)
-
Mahesh Venkitachalam -
Marc Viala Perso -
Matthias Troyer -
Richard Turrin -
Robert Ramey