https://bugs.kde.org/show_bug.cgi?id=356327
Milian Wolff <m...@milianw.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit| |http://commits.kde.org/kdev
| |elop/81011039d34d2e715135f0
| |24a67b68cdf5ee913b
Resolution|--- |FIXED
Status|CONFIRMED |RESOLVED
--- Comment #3 from Milian Wolff <m...@milianw.de> ---
Git commit 81011039d34d2e715135f024a67b68cdf5ee913b by Milian Wolff.
Committed on 23/01/2016 at 18:42.
Pushed by mwolff into branch '5.0'.
Always update the DUChain for the translation unit file.
This is required to properly update .cpp files to reflect changes
in header files. This patch is just a quick fix for the common case,
we might still run into issues for header files that depend on other
header files which got updated.
Also note that we need to introduce a central "DUChain::updateReady"
signal or similar, together with a mechanism to trigger that from
within the clang parse job. This is the reason why often the problem
view is not updating itself, leading to outdated highlighting of those.
Thing is: The problem view only listens to the background parser's
update signals, which do not get emitted for .cpp files when the .h
file is changed e.g. This is due to the different way the clang
lang plugin runs (single job can update multiple files), compared
to the oldcpp lang plugin (single job for single file).
M +7 -1 languages/clang/duchain/clanghelpers.cpp
http://commits.kde.org/kdevelop/81011039d34d2e715135f024a67b68cdf5ee913b
--
You are receiving this mail because:
You are watching all bug changes.
