regression test tools ported to vacpp
The regression test tools are finally ported to vacpp version 6 and the regression test status will again be updated every day at 6am CET (unless new changes break the compilation again). Please don't hesitate to contact me when you want some help porting your boost library to the IBM/VisualAge platform. toon
Toon Knapen wrote:
The regression test tools are finally ported to vacpp version 6 and the regression test status will again be updated every day at 6am CET (unless new changes break the compilation again).
Please don't hesitate to contact me when you want some help porting your boost library to the IBM/VisualAge platform.
Ok, first comments. There's a lot of errors like: "/home/tk/boost_regression/boost/boost/bind.hpp", line 138.50: 1540-0403 (S) "template <class R, class T> boost::_bi::unwrap(R T::* const *, int)" is already defined. "/home/tk/boost_regression/boost/boost/bind.hpp", line 133.50: 1540-0425 (I) "unwrap" is defined on line 133 of "/home/tk/boost_regression/boost/boost/bind.hpp". in particular, the program_options library fails with this error. And of course, "bind_test" fails too. I wonder what can be done. Thanks, Volodya
Vladimir Prus wrote:
Ok, first comments. There's a lot of errors like:
"/home/tk/boost_regression/boost/boost/bind.hpp", line 138.50: 1540-0403 (S) "template <class R, class T> boost::_bi::unwrap(R T::* const *, int)" is already defined. "/home/tk/boost_regression/boost/boost/bind.hpp", line 133.50: 1540-0425 (I) "unwrap" is defined on line 133 of "/home/tk/boost_regression/boost/boost/bind.hpp".
in particular, the program_options library fails with this error. And of course, "bind_test" fails too. I wonder what can be done.
in concertation with Peter Dimov I just commented out the overload and this seems to work. Peter predicted that bind_const_test would not work anymore due to this change but it seems to me that it does work. Well anyway, I have to regenerate the status pages to be sure (I'll launch the update shortly)
Toon Knapen wrote:
in concertation with Peter Dimov I just commented out the overload and this seems to work.
Peter predicted that bind_const_test would not work anymore due to this change but it seems to me that it does work. Well anyway, I have to regenerate the status pages to be sure (I'll launch the update shortly)
The results I see now show that only two program_options tests fail, which is quite nice. I have a question about the remaining failures. The error message is: "../libs/program_options/test/variable_map_test.cpp", line 59.35: 1540-0157 (S) The text ">" is unexpected. It may be that this token was intended as a template argument list terminator but the name is not known to be a template. The line in question is: BOOST_TEST(vm["foo"].as<string>() == "'12'"); That line should access variables_map instance and get an instances of 'variable_value' class (defined in boost/program_options/variables_map.hpp). Finally, template function 'as' is called. Apparently, vacpp does not believe 'as' to be a template. Do you have any ideas? I don't expect that a workaround is possible, so this part of library will be unsuable, but maybe you can at least bug compiler developers. - Volodya
"Toon Knapen" <toon.knapen@fft.be> wrote in message news:40BF16BA.8080009@fft.be...
The regression test tools are finally ported to vacpp version 6 and the regression test status will again be updated every day at 6am CET (unless new changes break the compilation again).
Please don't hesitate to contact me when you want some help porting your boost library to the IBM/VisualAge platform.
toon
I just spend half an hour to clean my code after this port. I do understand that you just wanted to make it work on your compiler. But lets in a future first discuss it here on a list before you commit this kind of modifications. Regards, Gennadiy.
Gennadiy Rozental wrote:
"Toon Knapen" <toon.knapen@fft.be> wrote in message news:40BF16BA.8080009@fft.be...
The regression test tools are finally ported to vacpp version 6 and the
I just spend half an hour to clean my code after this port. I do understand that you just wanted to make it work on your compiler. But lets in a future first discuss it here on a list before you commit this kind of modifications.
There was a discussion about all these issues for about a week now with clearly marked in the header that it was about the test library. Since you only responded to the last of the series of mails, I thought you were OK with the other modifications. Generally I always contact the developer personally before commiting a change. However, I already have tried to contact you privately but I never got a reply. Anyway, in the future I will again try to contact you before committing soth. May I also ask to elaborate on what you found not to be clean about the port and how and why you changed these changes. This might be interesting information for future ports.
participants (3)
-
Gennadiy Rozental -
Toon Knapen -
Vladimir Prus