Is there any estimate when c++17 will be supported? I know this is a lot to ask for.
In the meantime, would it be possible to optionally just ignore statements containing c++17 code, so that cppcheck works for majority of the code base not using c++17 features? The tool is very usefull and i dont want to work without it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
if you need a trac account, send me your htpasswd hash and I will create an account for you. A simple method to generate the htpasswd hash is to use this webpage: http://www.htaccesstools.com/htpasswd-generator/
Last edit: Daniel Marjamäki 2017-11-11
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
running the following code in the online demo with 1.81 returns syntax error
Is there any estimate when c++17 will be supported? I know this is a lot to ask for.
In the meantime, would it be possible to optionally just ignore statements containing c++17 code, so that cppcheck works for majority of the code base not using c++17 features? The tool is very usefull and i dont want to work without it.
Sorry I have no estimate. I would like to somehow ignore these until we handle it fully so it will be possible to analyze c++17 code asap.
could you open some tickets for c++17 features that we need to add?
http://trac.cppcheck.net
if you need a trac account, send me your htpasswd hash and I will create an account for you. A simple method to generate the htpasswd hash is to use this webpage: http://www.htaccesstools.com/htpasswd-generator/
Last edit: Daniel Marjamäki 2017-11-11