João Abecasis
John Maddock wrote:
Sigh... It's very compiler specific I'm afraid, we can STATIC_ASSERTION_FAILURE into the message but that's about it at present.
Actually I've implemented an alternative STATIC_ASSERT macro that let's one add two identifiers to better describe the error. One would be a title and the other a more descriptive message.
The original motivation for this was to diagnose a missing include file for Phoenix! One would get an error message containing
missing_include::boost_spirit_phoenix_comma_hpp
when trying to use the comma operator without the above include.
Have you considered using the MPL static assertion macros? They usually generate much better error messages than those you get from BOOST_STATIC_ASSERT. -- Dave Abrahams Boost Consulting www.boost-consulting.com