<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Other: Add header guards to all include files" href="https://bugs.freedesktop.org/show_bug.cgi?id=68849#c8">Comment # 8</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Other: Add header guards to all include files" href="https://bugs.freedesktop.org/show_bug.cgi?id=68849">bug 68849</a> from <a class="email" href="mailto:sbergman@redhat.com" title="Stephan Bergmann <sbergman@redhat.com>"> Stephan Bergmann</a> <pre>(In reply to <a href="show_bug.cgi?id=68849#c7">comment #7</a>) > I'll use the following scheme for all new or changed header guards: > > All uppercase: INCLUDED_%modulename_%filename_%extension > > Examples: > > basic/source/runtime/rtlproto.hxx -> INCLUDED_BASIC_RTLPROTO_HXX > embeddedobj/source/inc/closepreventer.hxx -> > INCLUDED_EMBEDDEDOBJ_CLOSEPREVENTER_HXX > sd/source/ui/inc/dlgass.hxx -> INCLUDED_SD_DLGASS_HXX > > With this INCLUDED prefix we will always be able to identify this as include > guard. This will be an advantage for future scripting efforts. FYI, the convention that I use is to use INCLUDED_FOO_BAR_HXX for a global header include/foo/bar.hxx under include/ and the longer INCLUDED_FOO_SOURCE_BAR_BAZ_HXX for anything else like foo/source/bar/baz.hxx, in an attempt to minimize the chance of clashes.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>