Re:[boost] [1.32 release] TODO list synchronization
Aleksey Gurtovoy wrote:
As we are coming closer to the branch-for-release date, I'd like to inquire developers working towards the release about the current status of their corresponding TODO items below. Simply replying to this message and saying "Done", "Not done, will be done by date X", "Abandoned" or whatever you wish to say on each of the items would be more than fine.
Serialization /////////////
Robert Ramey writes:
a) post version compatible with 1.31 next week.
Done
b) build and test against the CVS tree on my computer.
Done
c) check in
Done I've tested against the latest CVS on my own machine with satisfactory results. The compilers I've tested are: 1) MSVC 7.1 2) MSVC 6.0 3) Borland 5.51 4) Borland 5.60 5) gcc 3.3 under cygwin 6) gcc 3.4 on linux (draft #20) has been tested on linux with good results I haven't seen any test results from boost test servers for the serialization library - I expect to see some soon. If past experience is any guide - any platform NOT on the above list will have at least a few issues. d)? marking platforms to skip. I expect to mark Commeau as not useable due to a problem I have pending. I might revisit it if I have time. I would also expect to mark gcc 2.95 as not worth the effort as 3.3+ is a free upgrade. I'm still undecided about this - I'm a little burned out on this sort of stuff after addressing MSVC 6.0 and Borland. As to whether or not you want to include it in the branch, I would withhold judgment pending outcome of the first rounds of "official" test. The you can decide whether or not it should be included. There are no new features to add or document for this release. Anything not in there now would be slated for a subsequent release. This includes autolib, boost.book among other things. Robert Ramey
On Tue, Jul 13, 2004 at 09:52:59AM -0700, Robert Ramey wrote:
Aleksey Gurtovoy wrote:
As we are coming closer to the branch-for-release date, I'd like to inquire developers working towards the release about the current status of their corresponding TODO items below. Simply replying to this message and saying "Done", "Not done, will be done by date X", "Abandoned" or whatever you wish to say on each of the items would be more than fine.
Serialization ///////////// [...]
I've tested against the latest CVS on my own machine with satisfactory results. The compilers I've tested are:
1) MSVC 7.1 2) MSVC 6.0 3) Borland 5.51 4) Borland 5.60 5) gcc 3.3 under cygwin 6) gcc 3.4 on linux (draft #20) has been tested on linux with good results
I'd like to add that the tests with gcc 3.4 passed only if the compiler was on the latest patch level (3.4.1). The serialization library can't be build with gcc 3.4.0 (on linux, at least) ecxept you accept very ungly workarounds. (E.g., the input iterator concept check in libstdc++v3 was broken.) Regards Christoph -- http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/cludwig.html LiDIA: http://www.informatik.tu-darmstadt.de/TI/LiDIA/Welcome.html
Robert Ramey writes:
Aleksey Gurtovoy wrote:
As we are coming closer to the branch-for-release date, I'd like to inquire developers working towards the release about the current status of their corresponding TODO items below. Simply replying to this message and saying "Done", "Not done, will be done by date X", "Abandoned" or whatever you wish to say on each of the items would be more than fine.
Serialization /////////////
Robert Ramey writes:
a) post version compatible with 1.31 next week.
Done
b) build and test against the CVS tree on my computer.
Done
c) check in
Done
I've tested against the latest CVS on my own machine with satisfactory results. The compilers I've tested are:
1) MSVC 7.1 2) MSVC 6.0 3) Borland 5.51 4) Borland 5.60 5) gcc 3.3 under cygwin 6) gcc 3.4 on linux (draft #20) has been tested on linux with good results
Wonderful!
I haven't seen any test results from boost test servers for the serialization library - I expect to see some soon. If past experience is any guide - any platform NOT on the above list will have at least a few issues.
d)? marking platforms to skip.
I expect to mark Commeau as not useable due to a problem I have pending. I might revisit it if I have time. I would also expect to mark gcc 2.95 as not worth the effort as 3.3+ is a free upgrade. I'm still undecided about this - I'm a little burned out on this sort of stuff after addressing MSVC 6.0 and Borland.
Understandably.
As to whether or not you want to include it in the branch, I would withhold judgment pending outcome of the first rounds of "official" test. The you can decide whether or not it should be included.
There are no new features to add or document for this release. Anything not in there now would be slated for a subsequent release. This includes autolib, boost.book among other things.
OK. Thank you for the update, -- Aleksey Gurtovoy MetaCommunications Engineering
Sorry for not directly replying to the original message, I erased it by mistake. Le mer 14/07/2004 à 10:48, Aleksey Gurtovoy a écrit :
Robert Ramey writes:
Serialization /////////////
I've tested against the latest CVS on my own machine with satisfactory results. The compilers I've tested are:
1) MSVC 7.1 2) MSVC 6.0 3) Borland 5.51 4) Borland 5.60 5) gcc 3.3 under cygwin 6) gcc 3.4 on linux (draft #20) has been tested on linux with good results
Wonderful!
I haven't seen any test results from boost test servers for the serialization library - I expect to see some soon. If past experience is any guide - any platform NOT on the above list will have at least a few issues.
I can't achieve these good results on Linux with GCC 3.4.0. Is draft #20 the version currently in CVS? If so, only three tests are passing, the 206 other ones are failing because of a failure during the build of the static libraries: /boost/boost/noncopyable.hpp: In copy constructor `boost::archive::class_name_type::class_name_type(const boost::archive::class_name_type&)': /boost/boost/noncopyable.hpp:27: error: `boost::noncopyable::noncopyable(const boost::noncopyable&)' is private /boost/libs/serialization/build/../src/basic_oarchive.cpp:333: error: within this context The serialization library seems to work better with GCC 3.3.4: only six failures. There are around 40 failures with Intel 8.0.58. Regards, Guillaume PS: I'm impressed by the number of tests: 209. That's quite huge.
On Wed, Jul 14, 2004 at 04:36:36PM +0200, Guillaume Melquiond wrote:
Le mer 14/07/2004 à 10:48, Aleksey Gurtovoy a écrit :
Robert Ramey writes:
Serialization /////////////
I've tested against the latest CVS on my own machine with satisfactory results. The compilers I've tested are:
1) MSVC 7.1 2) MSVC 6.0 3) Borland 5.51 4) Borland 5.60 5) gcc 3.3 under cygwin 6) gcc 3.4 on linux (draft #20) has been tested on linux with good results
Wonderful!
I haven't seen any test results from boost test servers for the serialization library - I expect to see some soon. If past experience is any guide - any platform NOT on the above list will have at least a few issues.
I can't achieve these good results on Linux with GCC 3.4.0. Is draft #20 the version currently in CVS? If so, only three tests are passing, the 206 other ones are failing because of a failure during the build of the static libraries:
gcc 3.4.1 fixed several bugs that broke the serialization library.
/boost/boost/noncopyable.hpp: In copy constructor `boost::archive::class_name_type::class_name_type(const boost::archive::class_name_type&)': /boost/boost/noncopyable.hpp:27: error: `boost::noncopyable::noncopyable(const boost::noncopyable&)' is private /boost/libs/serialization/build/../src/basic_oarchive.cpp:333: error: within this context
It's easy to work around this particular problem in a way that should not hurt on other platforms: make the temporary explicit (i.e., construct a local variable and then pass this variable). I don't see a just as easy workaround for gcc 3.4.0 PR #16154 (broken input iterator concept check), though, unless you accept to write your own version of std::copy. After hacking around this issue I got many discouraging compiler failures in the cwchar header... But by then gcc 3.4.1 was released, Robert put serialization#20 on his website, and this combination passed the serialization tests on my machine. Thus I didn't pursue the problems with gcc 3.4.0 any further. Regards Christoph -- http://www.informatik.tu-darmstadt.de/TI/Mitarbeiter/cludwig.html LiDIA: http://www.informatik.tu-darmstadt.de/TI/LiDIA/Welcome.html
participants (4)
-
Aleksey Gurtovoy -
Christoph Ludwig -
Guillaume Melquiond -
Robert Ramey