Seriialzation library draft # 18 uploaded to files section
Fellow boosters, I just uploaded version #18 of the proposed boost serialization library to the files section. It can also be downloaded at www.rrsd.com It contains improvements in code/file/namespace organization, better documentation on how its implemented, and a number of arcane bug fixes. This is the version I will refer to during the upcoming review. Robert Ramey
On Sun, 11 Apr 2004 13:44:58 -0700, Robert Ramey wrote
I just uploaded version #18 of the proposed boost serialization library to the files section. It can also be downloaded at www.rrsd.com
It contains improvements in code/file/namespace organization, better documentation on how its implemented, and a number of arcane bug fixes.
This is the version I will refer to during the upcoming review.
A couple notes on this version: I had to comment out line 23 in boost/pfto.hpp: #include <boost/type_traits.hpp> to get the library to compile on Mandrake 9.2 g++ 3.3.1. Also, I'm having problems with building the tests -- can't find -lstdc++. I'm sure this is a Jamfile problem, but haven't been able to figure it out yet. Just looking at the Jamfile from the previous version, it hasn't changed much. And it has just dawned on me that I didn't compile the tests on the last version, only the examples... Jeff
Robert Ramey <ramey <at> rrsd.com> writes:
Fellow boosters,
I just uploaded version #18 of the proposed boost serialization library to the files section. It can also be downloaded at www.rrsd.com
It contains improvements in code/file/namespace organization, better documentation on how its implemented, and a number of arcane bug fixes.
I think I detected a minor bug in collections_load_imp.hpp. The operator() code for archive_input_seq reads: inline void operator()(Archive &ar, Container &s) { typedef BOOST_DEDUCED_TYPENAME Container::value_type type; stack_allocate<type> t; load_construct_data(ar, t.address(), 0U); ar >> make_nvp("item", t.reference()); s.push_back(t.reference()); t.address()->~type(); // undo load_construct_data above } This is AFAICS not exception-safe: if say s.push_back() throws, the dtor for the stack-allocated variable t won't be called. The same problem in similar code snippets through this file. Apologies if my perception is wrong. Joaquín M López Muñoz Telefónica, Investigación y Desarrollo
Robert Ramey wrote:
Fellow boosters,
I just uploaded version #18 of the proposed boost serialization library to the files section. It can also be downloaded at www.rrsd.com
It contains improvements in code/file/namespace organization, better documentation on how its implemented, and a number of arcane bug fixes.
This is the version I will refer to during the upcoming review.
Thanks. One thing though, I unzipped into my current boost_1_31_0, and at the top did: PYTHON_ROOT=/usr PYTHON_VERSION=2.3 bjam -sTOOLS=gcc stage ...found 5258 targets... [nothing] Doesn't build serialization. I went to libs/serialization/build, and then PYTHON_ROOT=/usr PYTHON_VERSION=2.3 bjam -sTOOLS=gcc will build, but doesn't do "stage".
"Neal D. Becker" <ndbecker2@verizon.net> writes:
Robert Ramey wrote:
Fellow boosters,
I just uploaded version #18 of the proposed boost serialization library to the files section. It can also be downloaded at www.rrsd.com
It contains improvements in code/file/namespace organization, better documentation on how its implemented, and a number of arcane bug fixes.
This is the version I will refer to during the upcoming review.
Thanks.
One thing though, I unzipped into my current boost_1_31_0, and at the top did: PYTHON_ROOT=/usr PYTHON_VERSION=2.3 bjam -sTOOLS=gcc stage ...found 5258 targets... [nothing]
Doesn't build serialization.
You shouldn't expect it to, IMO. A not-yet-accepted library submission shouldn't replace the top-level Jamfile. -- Dave Abrahams Boost Consulting www.boost-consulting.com
participants (1)
-
David Abrahams -
Jeff Garland -
Joaquin M Lopez Munoz -
Neal D. Becker -
Robert Ramey