Opened 8 years ago
Closed 7 years ago
#9965 closed Bugs (invalid)
execution_monitor.ipp causes compilation failure
Reported by: | Owned by: | Gennadiy Rozental | |
---|---|---|---|
Milestone: | To Be Determined | Component: | test |
Version: | Boost 1.54.0 | Severity: | Problem |
Keywords: | Cc: |
Description (last modified by )
test\impl\execution_monitor.ipp causes compilation failures from MSVC 10.0 because of this function:
int BOOST_TEST_CALL_DECL assert_reporting_function( int reportType, char* userMessage, int* ) { switch( reportType ) { case BOOST_TEST_CRT_ASSERT: detail::report_error( execution_exception::user_error, userMessage ); return 1; // return value and retVal are not important since we never reach this line case BOOST_TEST_CRT_ERROR: detail::report_error( execution_exception::system_error, userMessage ); return 1; // return value and retVal are not important since we never reach this line default: return 0; // use usual reporting method } } // assert_reporting_function
The MSVC compiler gives a warning that there is unreachable code (the lines that say "return 1;") and then because it has been told to treat warnings as errors, the compilation fails.
Change History (3)
comment:1 by , 8 years ago
Component: | None → test |
---|---|
Description: | modified (diff) |
Owner: | set to |
comment:2 by , 8 years ago
comment:3 by , 7 years ago
Resolution: | → invalid |
---|---|
Status: | new → closed |
Note:
See TracTickets
for help on using tickets.
Hi,
Why would MSVC treat warnings as errors?