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

List:       kde-bugs-dist
Subject:    [Bug 172622] Better cooperation with LLVM/clang community
From:       David Nolden <david.nolden.kdevelop () art-master ! de>
Date:       2008-10-12 10:56:00
Message-ID: 20081012105600.A5D72103D1 () immanuel ! kde ! org
[Download RAW message or body]

http://bugs.kde.org/show_bug.cgi?id=172622


David Nolden david nolden kdevelop art-master de changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |david.nolden.kdevelop@art-
                   |                            |master.de




--- Comment #1 from David Nolden <david nolden kdevelop art-master de>  2008-10-12 12:55:58 ---
The actual "parser" is the smaller problem. It has relatively few
bugs, and seems to implement nearly all of C++. The bigger problem is
what you do with the parsed data, eg. the "semantic" part. KDevelop
has the DUChain, a language-independent architecture to
store/manage/use exactly that data, and it's now being worked on for
years. That architecture is in no way useful for a compiler, rather
it's an abstraction optimized for persistence, generality, and
"updatability", which means that for example the data of included
headers is stored separately from the files that include it.

On the parser level, KDevelop4 does have a parser that implements
nearly all of C++, and has few known bugs. Those bugs are hard to fix,
because the author isn't active any more and the code is hard to
understand, but that effort is not comparable to switching the parser.

So it would be nice if some more efforts could be shared, but I don't
see a realistc way for it at this point.


-- 
Configure bugmail: http://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]