https://svn.boost.org/trac10/ticket/11496 <p> The config test math_info contains: </p> <p> #ifdef INFINITY </p> <blockquote> <p> PRINT_EXPRESSION(INFINITY); </p> </blockquote> <p> #endif </p> <p> The test expects this program to compile/run cleanly. This may not be case. According to the standard: </p> <blockquote> <p> INFINITY </p> </blockquote> <blockquote> <p> expands to a constant expression of type float representing positive or unsigned infinity, if available; else to a positive constant of type float that overflows at translation time.192) </p> </blockquote> <p> So...it's perfectly valid for this test to fail at compile-time. </p> <p> Not sure how to easily fix this... </p> <p> Thanks, </p> <p> Ed </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/11496 Trac 1.4.3 John Maddock Mon, 10 Aug 2015 11:54:05 GMT https://svn.boost.org/trac10/ticket/11496#comment:1 https://svn.boost.org/trac10/ticket/11496#comment:1 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">wontfix</span> </li> </ul> <p> I understand that this may be a theoretical issue, but in practice, it seems to work fine. If there are particular compilers that have an issue with this, then we can add special cases for those. </p> Ticket