<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - Clean-up header includes (global/local)" href="https://bugs.freedesktop.org/show_bug.cgi?id=65108#c19">Comment # 19</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - Clean-up header includes (global/local)" href="https://bugs.freedesktop.org/show_bug.cgi?id=65108">bug 65108</a> from <a class="email" href="mailto:michael.meeks@collabora.com" title="Michael Meeks <michael.meeks@collabora.com>"> Michael Meeks</a> <pre>The ESC resolution was: Header includes <> vs "" etc. (Tml/Sberg) + easy-hack closure: + <a class="bz_bug_link bz_status_NEW " title="NEW --- - Clean-up header includes (global/local)" href="show_bug.cgi?id=65108">https://bugs.freedesktop.org/show_bug.cgi?id=65108</a> + situation reasonably clear, MS compiler has a very odd use of "" + if we want to do a global cleanup, and be reasonably sane we should only use <> (Sberg) + problems with own vs. system version (Norbert) + concern with local includes vs. public ones + local includes have no directory path anyway (Stephan) + in places we do relative includes "../foo/baa.h" (Kohei) + helps to cleanup pre-compiled headers (Sberg) + we should use <> everywhere without a relative path. + but it's fine to continue using "" for whatever corner cases make sense, identify and restore these post-facto (Kohei) I guess scripting this is the way to go & do it in one big commit :-)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>