<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><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#c17">Comment # 17</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 <span class="vcard"><a class="email" href="mailto:nthiebaud@gmail.com" title="Norbert Thiebaud <nthiebaud@gmail.com>"> <span class="fn">Norbert Thiebaud</span></a>
</span></b>
<pre>
I would favor that the whole source tree be cleaned-up to whatever 'norm' is
agreed upon.
There are 3 proposed scheme, as I read it:
1/ use "" systematically (well except for <stdio> <assert> and other true
system include I suspect....
2/ use <> systematically
3/ use "" for 'local' include, i.e in the same directory than the cxx and <>
for the rest
4/ use "" for include private to the module you are in and <> for include that
are 'public' header (iow system from the point of view of other module)
I favor 4/ because a/ that does solve the original pch problem b/ that convey a
useful semantic content to the reader of the code: where is the include in
question supposed to be.
iow in 'standard speak' considering $(SRCDIR)/include as a system include path</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>