Subject: Re: [Boost-bugs] [Boost C++ Libraries] #4660: Error read binary archive, created by old boost version
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2013-03-04 16:24:39
#4660: Error read binary archive, created by old boost version
---------------------------------------+------------------------------------
Reporter: serge-voropaev@⦠| Owner: ramey
Type: Bugs | Status: reopened
Milestone: Boost 1.45.0 | Component: serialization
Version: Boost 1.45.0 | Severity: Problem
Resolution: | Keywords:
---------------------------------------+------------------------------------
Comment (by Joao Geada <joao@â¦>):
I'm stunned incredulous by the attitude displayed here Markus.
I've contributed a testcase that shows that there is still a problem with
the current version of boost serializer to read binary archives produced
by an older version. This testcase was requested by Ramey, which I've
spent time minimizing and clearing with my company to be allowed to share
it with this team. In virtually every other open source project I'd be
thanked for this and other people more expert with the code would dive in
and diagnose what the real problem is etc etc.
Instead here you '''complain''' for my having provided you a testcase???
And once again, let me be clear as to what exactly this testcase shows:
1) binary serialization written by 1.34.1 cannot be read by 1.53
2) binary serialization written by 1.34.1 can be read by 1.34.1; likewise
binary written by 1.53 can be read back by 1.53. I'd have thought it
obvious that this should work, but as you'll see later, such an assumption
is not legitimate in all cases.
3) text serialization written by 1.34.1 can be read by 1.34.1 and 1.53.
Text archive written by 1.53 can also be read back by 1.53.
4) xml serialization written by 1.34.1 cannot be read by 1.53, but can be
read back by 1.34.1.
5) xml serialization written 1.53 cannot be read back by 1.53!!! There
goes that assumption that read/write within the same version and same
backend format works.
6) the serialization code all lives in a single piece of code, runs in
Linux 64bit; the problem here does not appear in any way related to bug
5579. But I'm not deeply familiar with the boost serializer code so I
could be wrong about that.
Note that I work for a closed source company and cannot under any
circumstances reveal any of the our code.
Echoing similar sentiments elsewhere, I'm seriously starting to wonder if
my team has made a major mistake in using and relying on this component.
-- Ticket URL: <https://svn.boost.org/trac/boost/ticket/4660#comment:64> Boost C++ Libraries <http://www.boost.org/> Boost provides free peer-reviewed portable C++ source libraries.
This archive was generated by hypermail 2.1.7 : 2017-02-16 18:50:12 UTC