https://bugs.freedesktop.org/show_bug.cgi?id=68849
--- Comment #8 from Stephan Bergmann <sberg...@redhat.com> --- (In reply to comment #7) > 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. -- You are receiving this mail because: You are on the CC list for the bug.
_______________________________________________ LibreOffice mailing list LibreOffice@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/libreoffice
