the version i'm using is not available on the list, im using 4.7.1 extra defines used in the code (but not defined in the code) do not get parsed correctly with the background parser, but do get parsed correctly with the full reparse of closing and reopening kdevelop. these defines are being defined in the define section of the project manager. a define example would be something like: #if(THIS_IS_DEFINED==1) #endif where THIS_IS_DEFINED is defined as some number in the project manager define. this DOES work correctly with a full reparse, but not just updating the code. Reproducible: Always Steps to Reproduce: 1. add a variable inside one of the if defines inside a header file 2. go to a file that uses the variable inside of the define from that header file 3. start typing the name of the variable or one of the methods that the class of the variable has Actual Results: the code completion will not show the correct class type, and will tell you the variable doesnt exist(sometimes) Expected Results: reparsing the code should have shown the correct type in the code completion
Yes, that's a known bug in the oldcpp ParsingEnvironment. To work-around it there is a check button in includes/defines manager: "Reparse project". Also you could try to use the kdev-clang plugin, this bug's been fixed there.
well, i do use the reparse project... but im currently in the process of changing a ton of code and i really cant wait for the hour and a half it takes to parse the code. Any idea when the clang plugin will make it into the main build? i cannot seem to get the source code for the plugin... or a precompiled binary for it. attempting to clone the git for it just sits there and does nothing.
got the source code finally... but it wont seem to compile.. says it is missing some file ECM.
You need to install ECM from extra-cmake-modules.git -- But please continue on the mailing list or IRC if you have further problems -- it's not related to this bug report.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.