Examples of errors detected by the V628 diagnostic.


V628. It's possible that the line was commented out improperly, thus altering the program's operation logics.


Trans-Proteomic Pipeline

V628 It's possible that the line was commented out improperly, thus altering the program's operation logics. interprophetmain.cxx 175


int main(int argc, char** argv) {
  ....
  if (getIsInteractiveMode())
    //p->writePepSHTML();
  //p->printResult();

  // regression test?
  if (testType!=NO_TEST) {
     TagListComparator("InterProphetParser",
                       testType,outfilename,testFileName);
  ....
}

Spring Engine

V628 It's possible that the line was commented out improperly, thus altering the program's operation logics. assimp colladaparser.cpp 2281


void ColladaParser::ReadSceneLibrary()
{
  ....
  else if( mReader->getNodeType() == irr::io::EXN_ELEMENT_END)
  {
    if( strcmp( mReader->getNodeName(), "....") == 0)
      //ThrowException( "Expected end of \"....\" element.");

    break;
  }
  ....
}

Inkscape

V628 It's possible that the line was commented out improperly, thus altering the program's operation logics. FontFactory.cpp 705


font_instance *font_factory::Face(....)
{
  ....
  if( features[0] != 0 ) // <=
    // std::cout << "          features: " << std::endl;

  for( unsigned k = 0; features[k] != 0; ++k ) {
  // dump_tag( &features[k], "            feature: ");
  ++(res->openTypeTables[ extract_tag(&features[k])]);
  }
  ....
}


Do you make errors in the code?

Check your code
with PVS-Studio

Static code analysis
for C, C++ and C#

goto PVS-Studio;