Opened 13 years ago
Closed 13 years ago
#3593 closed Patches (fixed)
[range] regresion test failures in VC10
| Reported by: | Owned by: | Neil Groves | |
|---|---|---|---|
| Milestone: | Boost 1.43.0 | Component: | range |
| Version: | Boost Development Trunk | Severity: | Problem |
| Keywords: | Cc: |
Description
The range regresion tests have a number of failures on VC10 Beta 2 due to ambiguities between boost::begin/end and std::begin/end. e.g
These failures can be avoid by explicitly qualifying calls to begin/end in the tests with boost:: .
Attachments (2)
Change History (7)
by , 13 years ago
| Attachment: | range.diff added |
|---|
comment:1 by , 13 years ago
| Milestone: | Boost 1.42.0 → Boost 1.43.0 |
|---|---|
| Summary: | [range] regresion test failures in VC10 Beta 2 → [range] regresion test failures in VC10 |
| Type: | Bugs → Patches |
by , 13 years ago
| Attachment: | range2.diff added |
|---|
comment:2 by , 13 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
I've started fixing compiler compatibility issues with Boost.Range
comment:3 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
These issues were fixed as part of debugging other compiler compatibility issues with the Boost.RangeEx merge into Boost.Range.
comment:4 by , 13 years ago
| Resolution: | fixed |
|---|---|
| Status: | closed → reopened |
The iterator_range test is still failing (as of yesterday): http://tinyurl.com/yblef9g
comment:5 by , 13 years ago
| Resolution: | → fixed |
|---|---|
| Status: | reopened → closed |
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.
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.