This is based on the <https://svn.boost.org/trac/boost/ticket/2059> ticket I entered a couple months ago. I just tried out the actual change needed and attached it to the ticket. (I just made a project that compiles all the mandatory Boost source code, like the unit-test framework, into various static libraries I can include in my other projects without repeating the compilation instructions [or wasting disk space]. Centralization is fun.) I still don't know if my __APPLE_CC__ preprocessor test is the official way to check for Xcode, or any compatible, setup. I heard that the current code is supposedly formatted for Visual C++'s error message handling. If so, and the class I changed is _not_ where the per-compiler-product changes are supposed to go, then move the code as needed. (I guess there would be parallel visual-c++ and xcode default formatting classes.) -- Daryle Walker Mac, Internet, and Video Game Junkie darylew AT hotmail DOT com