id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
3616	Boost.Test Xcode formatter not working in Xcode 3.2	Sean P. DeNigris <sean@…>	Gennadiy Rozental	"The build result format has changed to:
[file path]:[line]: {warning|error}: [whatever]
e.g. /path/to/source.cpp:42: error: something bad happened!

Right now, the formatter outputs [file path]:[line]: [whatever]

The ""warning: "" or ""error: "" is missing, so the issue is not properly displayed in Xcode

Possible solution:
1. move Apple-specific code to log_entry_start e.g.:
void log_entry_start( std::ostream& output, boost::unit_test::log_entry_data const& entry_data, log_entry_types let )
{
    switch( let ) {
...
			case BOOST_UTL_ET_WARNING:
#ifdef __APPLE_CC__
				output << file << ':' << line << "": warning: "";
#endif
				print_prefix( output, entry_data.m_file_name, entry_data.m_line_num );
				output << ""warning in \"""" << boost::unit_test::framework::current_test_case().p_name << ""\"": "";
				break;
			case BOOST_UTL_ET_ERROR:
#ifdef __APPLE_CC__
				output << file << ':' << line << "": error: "";
#endif
				print_prefix( output, entry_data.m_file_name, entry_data.m_line_num );
				output << ""error in \"""" << boost::unit_test::framework::current_test_case().p_name << ""\"": "";
				break;
...

I don't know what to do about ""info"" and ""fatal error,"" because I don't know if there are corresponding levels in Xcode, but I'm posting the question to the Xcode users list."	Bugs	closed	Boost 1.41.0	test	Boost 1.40.0	Problem	invalid