Properly use #include <> and #include ""

[Thiago Macieira]

Michael Olbrich wrote:
>Many libraries use the same method to generate the include guards. This
>means there is a high probability that /usr/include/libzyx/foo.h and
>/usr/include/anotherlib/foo.h have the same guard.

If that happens, using "" or < > isn't going to help very much. It'll only 
delay the problem.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- 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/20070617/20e1292e/attachment.sig>