It seems to me we need to redesign the Tokenizer::setVarId(). As far as I see it is not possible to fix these tickets with some minor tweaks:
http://trac.cppcheck.net/ticket/7443 http://trac.cppcheck.net/ticket/7495
Better handling of scopes is needed.
I feel that handling of scopes should only be done in SymbolDatabase. We should not do that in Tokenizer.
Maybe if we add a SymbolDatabase::createScopes() method we could call that before Tokenizer::setVarId() and Tokenizer::simplifyTypedef().
http://trac.cppcheck.net/query?status=!closed&keywords=~varid has more examples, e.g. #4412
That is responsible for some ugly positives in my codebase (see http://trac.cppcheck.net/ticket/7443). Are there any plans to attack this?
Are there any plans to attack this?
I had some plans to do it now... but I think this will be a too big task for me right now.
Log in to post a comment.
It seems to me we need to redesign the Tokenizer::setVarId(). As far as I see it is not possible to fix these tickets with some minor tweaks:
http://trac.cppcheck.net/ticket/7443
http://trac.cppcheck.net/ticket/7495
Better handling of scopes is needed.
I feel that handling of scopes should only be done in SymbolDatabase. We should not do that in Tokenizer.
Maybe if we add a SymbolDatabase::createScopes() method we could call that before Tokenizer::setVarId() and Tokenizer::simplifyTypedef().
Last edit: Daniel Marjamäki 2016-05-14
http://trac.cppcheck.net/query?status=!closed&keywords=~varid has more examples, e.g. #4412
That is responsible for some ugly positives in my codebase (see http://trac.cppcheck.net/ticket/7443). Are there any plans to attack this?
I had some plans to do it now... but I think this will be a too big task for me right now.