Boost C++ Libraries: Ticket #3593: [range] regresion test failures in VC10

attachment set

Fri, 06 Nov 2009 14:24:16 GMT

attachment → range.diff

summary, type, milestone changed

Sat, 03 Apr 2010 10:48:13 GMT

summary [range] regresion test failures in VC10 Beta 2 → [range] regresion test failures in VC10
type Bugs → Patches
milestone Boost 1.42.0 → Boost 1.43.0

Theres also a couple of failures due to conflicts between boost::next and std::next, which effect both VC10 and GCC 4.4 in c++0x mode. Additional patch attached.

attachment set

Sat, 03 Apr 2010 10:48:43 GMT

attachment → range2.diff

owner, status changed

Neil Groves — Sat, 03 Apr 2010 21:27:37 GMT

owner changed from Thorsten Ottosen to Neil Groves
status new → assigned

I've started fixing compiler compatibility issues with Boost.Range

status changed; resolution set

Neil Groves — Sat, 03 Apr 2010 21:28:42 GMT

status assigned → closed
resolution → fixed

These issues were fixed as part of debugging other compiler compatibility issues with the Boost.RangeEx merge into Boost.Range.

status changed; resolution deleted

Tue, 06 Apr 2010 08:49:57 GMT

status closed → reopened
resolution fixed

The iterator_range test is still failing (as of yesterday): http://tinyurl.com/yblef9g

status changed; resolution set

Neil Groves — Wed, 07 Apr 2010 23:44:35 GMT

status reopened → closed
resolution → fixed

Heck. I reproduced the problem on GCC with C++0x enabled and cleared the defects. I assumed this would also clear VC10. It does not due to a missing C++0x library function in the current GCC.

This time it really is fixed for VC10. Sorry for the previous confusion.