[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Properly use #include <> and #include ""
From:       Matthias Kretz <kretz () kde ! org>
Date:       2007-06-15 13:13:22
Message-ID: 200706151513.26042.kretz () kde ! org
[Download RAW message or body]


On Friday 15 June 2007, Andreas Pakulat wrote:
> If I understood correctly a public header in the shell library should
> use #include "foobar.h" for any header that is also inside the shell
> library. However it should use #include <barfoo.h> for any system-header
> and also headers from other libraries of the kdevplatform module. Is
> that correct? If not, whats the correct way here?

Just a small correction: You don't have to draw the line between every single 
library. If two or more libs ship together (e.g. kdecore, kdeui, kio, ...) 
they should prefer "" to <> to include headers from the other lib because the 
relative position of the header (when installed) is known. Only when the 
relative position is not known (e.g. Qt headers and system headers) should 
you include headers with <>.

But I've heared different opinions on this, though no arguments to convince 
me, yet.

-- 
________________________________________________________
Matthias Kretz (Germany)                            <><
http://Vir.homelinux.org/
MatthiasKretz@gmx.net, kretz@kde.org,
Matthias.Kretz@urz.uni-heidelberg.de

[Attachment #3 (application/pgp-signature)]

[prev in list] [next in list] [prev in thread] [next in thread]