https://bugs.kde.org/show_bug.cgi?id=338649
--- Comment #11 from Ralf Habacker <ralf.habac...@freenet.de> --- (In reply to Patric Schmitz from comment #10) > >> If this is a basic limitation to using clang, is this really the way the > >> project should go? > >> Maybe it is possible to separate only the parser parts without the whole > >> semantics and error checking from clang? > > I don' know yet; it need to be evaluated > > It seems that clang itself has no means of parsing incomplete code fragments > and will fail to produce a syntax tree at all if not all types and symbols > can be resolved. This is at least what I get out of this post from Clang > Developers: > > http://clang-developers.42468.n3.nabble.com/Lenient-lexing-parsing-of-code-snippets-td4042786.html > There is a GSoC 2014 project mentioned where someone has a similar > requirement (for syntax highlighting). Maybe we could look into that, it > seems a fuzzy parser has been developed for that project. here is the related git repo https://github.com/kapf/clang-highlight and a test case https://github.com/kapf/clang-highlight/blob/master/unittests/FuzzyParseTest.cpp -- You are receiving this mail because: You are watching all bug changes.
