-
Notifications
You must be signed in to change notification settings - Fork 363
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on highlighting when: "import" used as a (member) variable name in class nested into a namespace #2197
Comments
Hi @MarcoWagner, thanks for the feedback. This seems to be related to #2192.
Please try with latest snapshot https://ci.appveyor.com/project/SonarOpenCommunity/sonar-cxx/branch/master/artifacts. This does not solve the problem but should continue after a problem as with 1.3. Regards, |
Hi @MarcoWagner, also here strange: parsing and syntax highlighting with SSLR toolkit is ok: Regards, |
Thanks, the updated version does not interrupt anymore. The parsing speedup of the new version is awesome. On the Project i am using sonar-cxx it had an impact from several hours to less than 10 minutes! |
Hi @MarcoWagner,
Thanks for the feedback... Regards |
Hi @MarcoWagner, Could you share some insights to the 10 minutes and performance please:
Just search for Regards, |
- import & module - close SonarOpenCommunity#2197 - close SonarOpenCommunity#2192
currently only using cppcheck and cobertura coverage reports. ~720k LoC INFO: Sensor CXX [cxx] (done) | time=460850ms |
Hi @MarcoWagner, thx! That helps to further optimize the plugin... |
i also have a wxWidgets based project with interesting stats. ~150k LoC INFO: Sensor CXX [cxx] (done) | time=5475497ms |
Describe the bug
After upgrading to sonar-cxx version 2.0.x the scanner is getting interrupted with the following message:
To Reproduce
Scan a file with this content:
Expected behavior
Ideally the variable gets recognized as such.
Alternatively not interrupting the scan, maybe skipping the file with a warning.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: