|
Boost : |
From: Boris Gubenko (Boris.Gubenko_at_[hidden])
Date: 2007-03-01 17:02:54
John Maddock wrote:
> [...] try:
>
> # ifndef BOOST_TR1_NO_RECURSION
> # define BOOST_TR1_NO_RECURSION
> # define BOOST_CONFIG_NO_ITERATOR_RECURSION
> # endif
>
> # include <iterator>
>
> # ifdef BOOST_CONFIG_NO_ITERATOR_RECURSION
> # undef BOOST_TR1_NO_RECURSION
> # undef BOOST_CONFIG_NO_ITERATOR_RECURSION
> # endif
>
It does not help. I did not run the full tests, just tr1 library tests.
They failed as before.
> In any case this is too late for 1.34 now whatever.
Indeed. For 1.34, the tests affected by this RW bug should be made known
failures. It may happen automatically during Volodya's cleanup for 1.34,
assuming that he does it for all the platforms, not just release platforms
(this is something I'm not sure about).
Boris Gubenko wrote:
> I think, we have 3 options:
>
> 1) put your fix in some regex library header which includes <iterator>
> anyway.
>
> 2) put my original fix which does not require any headers in roguewave.hpp
>
> 3) do nothing: mark tests affected by this RW bug expected failures and
> wait for the compiler kit with the fix (for the reference, this RW bug
> is tracked internally as CR JAGag33243).
>
> I'm running the tests with 2) now, to verify that it indeed is a viable
> solution.
2) fixes the problem without introducing any regression. The results are
not on the web yet, I just checked.
Do you have any suggestion on how to proceed with this issue beyond 1.34?
Thanks for your help,
Boris
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk