Properly use #include <> and #include ""

[Thiago Macieira]

Michael Olbrich wrote:
>To point is, having two versions of the same lib in the search path
>should always fail 

Break your sentence here. No "unless":

>unless the version you are using comes first. Using 
><> makes sure of that.

That means that if you add two libraries in the same path, you're doing 
something wrong. You deserve to get compilation errors, including 
heisenbugs.

That said, I'd prefer having < > for all installed headers.

-- 
  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/20070615/4fef717f/attachment.sig>