question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

bug report: continuous warning of "incompatible with c++98"

See original GitHub issue

I have installed clang and cppcheck as checkers. I have already set "c-cpp-flylint.clang.standard": ["c++11", "c++14", "c++17"] and "c-cpp-flylint.cppcheck.standard": ["c++11"] in my settings.json file. But every time I save a file I get a warning notification like below. There is no problem in building the project. It only appears in the static analysis. I am using Ubuntu 18.04 with VS Code 1.25.1.


vscode-c-cpp-flylint: ‘Line could not be parsed: warning: ‘auto’ type specifier is incompatible with C++98 [Semantic Issue]’ while validating: /home/<xxxx>/Code/XXXX/src/runner/Master_handler.cpp. Please analyze the ‘C/C++ FlyLint’ Output console. Stacktrace: Error: Line could not be parsed: warning: ‘auto’ type specifier is incompatible with C++98 [Semantic Issue] at lines.forEach.line (/home/<xxxx>/.vscode/extensions/jbenden.c-cpp-flylint-1.1.1/server/linters/linter.js:221:31) at Array.forEach (native) at Clang.parseLines (/home/<xxxx>/.vscode/extensions/jbenden.c-cpp-flylint-1.1.1/server/linters/linter.js:205:15) at Clang.lint (/home/<xxxx>/.vscode/extensions/jbenden.c-cpp-flylint-1.1.1/server/linters/linter.js:195:21) at lintersCopy.forEach.linter (/home/<xxxx>/.vscode/extensions/jbenden.c-cpp-flylint-1.1.1/server/server.js:242:43) at Array.forEach (native) at /home/<xxxx>/.vscode/extensions/jbenden.c-cpp-flylint-1.1.1/server/server.js:239:21 at Generat…

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:1
  • Comments:10 (2 by maintainers)

github_iconTop GitHub Comments

9reactions
linonetwocommented, May 31, 2019

Try "c-cpp-flylint.clang.extraArgs": ["-Wno-c++98-compat"],

5reactions
Todd-Fultoncommented, Oct 17, 2019

also try "no-c++98-compat-pedantic" https://clang.llvm.org/docs/DiagnosticsReference.html#id120

with -Weverything you need to “black-list” warnings that don’t apply (too noisy), instead of “white-listing” the warnings you want. I believe the default is ["all", "extra", "everything"] prolly why you get c98 compat warnings in c++17 mode.

Read more comments on GitHub >

github_iconTop Results From Across the Web

54702 – [4.8 Regression] lto1: internal compiler error
That of course makes things more inconsistent even from the middle-end side, but the asm hash forcefully computes assembler names (suspect for ...
Read more >
PHP :: Bug #57600 :: sdm
Thank you for taking the time to report a problem with the package. Unfortunately you are not using a current version of the...
Read more >
MATLAB Support Package for Raspberry Pi Hardware
Packages wont install. I am trying to do this from a MAC M1 and I am continuously getting this error. The hardware pings...
Read more >
Capture and read bug reports - Android Developers
A bug report contains device logs, stack traces, and other diagnostic information to help you find and fix bugs in your app.
Read more >
Diagnostic flags in Clang - LLVM releases
warning: checker plugin 'A' is not compatible with this version of the analyzer ... warning: initialization of pointer of type A to null...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found