https://svn.boost.org/trac10/ticket/4287 <p> there are different styles of encoding filenames in use in include protection the most common style is BOOST_&lt;capitalized filename&gt;_HPP </p> <p> examples for deviations from that pattern are </p> <p> any.hpp: </p> <blockquote> <p> #ifndef BOOST_ANY_INCLUDED </p> </blockquote> <p> thread.hpp: </p> <blockquote> <p> #if !defined(BOOST_THREAD_WEK01082003_HPP) </p> </blockquote> <p> concept_check.hpp: uses a pluralized filename </p> <blockquote> <p> #ifndef BOOST_CONCEPT_CHECKS_HPP </p> </blockquote> <p> throw_exception.hpp: </p> <blockquote> <p> #ifndef BOOST_THROW_EXCEPTION_HPP_INCLUDED </p> </blockquote> <p> wave.hpp: </p> <blockquote> <p> #if !defined(WAVE_HPP_DCA0EA51_EF5B_4BF1_88A8_461DBC5F292B_INCLUDED) </p> </blockquote> <p> the motivation for harmonizing include protection is to be able to conclude from the filename the guarding definition; that might be useful for checking whether certain files have been included. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/4287 Trac 1.4.3 Jeremiah Willcock Thu, 03 Jun 2010 18:06:39 GMT https://svn.boost.org/trac10/ticket/4287#comment:1 https://svn.boost.org/trac10/ticket/4287#comment:1 <ul> <li><strong>owner</strong> changed from <span class="trac-author">Jeremiah Willcock</span> to <span class="trac-author">No-Maintainer</span> </li> </ul> Ticket Steven Watanabe Fri, 04 Jun 2010 22:49:33 GMT https://svn.boost.org/trac10/ticket/4287#comment:2 https://svn.boost.org/trac10/ticket/4287#comment:2 <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> Might be useful?? </p> <p> As far as I am concerned, #include guards are the library author's business, as long as they are sufficiently mangled to be unique. </p> Ticket