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

List:       kdevelop-bugs
Subject:    [Bug 200216] New: Parser does not handle #include_next correctly
From:       Armin Berres <trigger () space-based ! de>
Date:       2009-07-14 18:42:32
Message-ID: bug-200216-40295 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=200216

           Summary: Parser does not handle #include_next correctly
           Product: kdevelop
           Version: unspecified
          Platform: Compiled Sources
        OS/Version: unspecified
            Status: NEW
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs@kdevelop.org
        ReportedBy: trigger@space-based.de


Version:            (using KDE 4.2.96)
Installed from:    Compiled From Sources

When using the boost tr1 headers kdevelop complains about a lot of headers
which include itself. this is actually wrong --  they do not include
themselves, but "#include_next" a header with their own name.
E.g. the boost map uses "#include_next <map>" to include the stl map.

One can very easily reproduce this, by creating a header with a random name,
and the content "#include_next <HEADER_NAME>".
Kdevelop will complain that HEADER_NAME includes itself, the compiler will tell
you, if your name was non-generic enough, that HEADER_NAME does not exist,
because it can be only found once in the include path.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs
[prev in list] [next in list] [prev in thread] [next in thread]