A New Krazy Checker for #include

[Andras Mantia]

Hi,

On Sunday 08 April 2007, Allen Winter wrote:
> Other ideas that I may implement one day (or maybe someone will do
> me): - if including an installed header, always use #include <foo.h>,
> not "foo.h" - foo.cpp should always include its own header foo.h
> first

This is wrong, you shouldn't do it. If a module has a library, you will 
have a wrong build if you don't install first the library from the 
module and then build the rest, otherwise an already installed old 
version will be picked up. And this is quite common (at least it was in 
3.5), think about libkonq, libkdepim, kdevelop. At least in case of 
KDevelop, this will still be the case in KDE4. 
Same problem is for checking this kind of inclusion in the installed 
headers, sometimes the right thing is to use " ".

Andras

-- 
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070409/f03454dc/attachment.sig>