Home >  Krazy Code Checker >  kde-4.x >  kdeutils >  kgpg

krazy2 Analysis

Checkers Run = 51
Files Processed = 170
Total Issues = 3 ...as of February 08 2010 05:51:38 CET

• For File Type c++
  1. Check for TRUE and FALSE macros [captruefalse]...okay!
  2. Check for methods that return 'const' refs in public classes [constref]...okay!
  3. Check for an acceptable copyright [copyright]...okay!
  4. Check for cpp macros and usage [cpp]...okay!
  5. Check for code that should be considered crashy. [crashy]...okay!
  6. Check single-char QString operations for efficiency [doublequote_chars]...okay!
  7. Check public classes with private members or d-pointer issues [dpointer]...okay!
  8. Check for QString compares to "" [emptystrcompare]...okay!
  9. Check that file ends with a newline [endswithnewline]...okay!
  10. Check for C++ ctors that should be declared 'explicit' [explicit]...okay!
  11. Check for foreach loop issues [foreach]...okay!
  12. Check validity of i18n calls [i18ncheckarg]...okay!
  13. Check for invalid icon names [iconnames]...okay!
  14. Check for proper include directives [includes]...okay!
  15. Check for inline methods in public classes [inline]...okay!
  16. Check for an acceptable license [license]...okay!
  17. Check for assignments to QString::null [nullstrassign]...okay!
  18. Check for compares to QString::null or QString() [nullstrcompare]...okay!
  19. Check for C++ operators that should be 'const' [operators]...okay!
  20. Check for inappropriate pass-by-value function args [passbyvalue]...okay!
  21. Check for postfix usage of ++ and -- [postfixop]...OOPS! 3 issues found!
      • transactions/kgpgimport.cpp: line# 268 (1)
      • kgpginterface.cpp: line# 730,738 (2)

      You should use ++ and -- as prefix whenever possible as these are more efficient than postfix operators. Prefix increments first and then uses the variable, postfix uses the actual; the variable is incremented as well. Because of this, the prefix operators are inherently more efficient. WARNING Make sure that you don't introduce off-by-one errors when changing i++ to ++i.

  22. Check for dangerous or inefficient QByteArray usage [qbytearray]...okay!
  23. Check for Qt classes that should not be used [qclasses]...okay!
  24. Check for Qt methods that should be avoided [qmethods]...okay!
  25. Check for QMIN and QMAX macros [qminmax]...okay!
  26. Check for classes that should use the 'Q_OBJECT' macro [qobject]...okay!
  27. Check for signals: and slots: [sigsandslots]...okay!
  28. Check for spelling errors [spelling]...okay!
  29. Check for strings used improperly or should be i18n. [strings]...okay!
  30. Check for system calls to replace by KDE or Qt equivalents [syscalls]...okay!
  31. Check for typedefs that should be replaced by Qt typedefs [typedefs]...okay!
• For File Type kpartgui
  1. Check that file ends with a newline [endswithnewline]...okay!
  2. Check validity of i18n calls [i18ncheckarg]...okay!
  3. Check for spelling errors [spelling]...okay!
  4. Validates kpartgui files using 'xmllint' [validate]...okay!
• For File Type tips
  1. Check that file ends with a newline [endswithnewline]...okay!
  2. Check for spelling errors [spelling]...okay!
• For File Type desktop
  1. Check that file ends with a newline [endswithnewline]...okay!
  2. Check for invalid icon names [iconnames]...okay!
  3. Check for spelling errors [spelling]...okay!
  4. Validates desktop files using 'desktop-file-validate' [validate]...okay!
• For File Type designer
  1. Check that file ends with a newline [endswithnewline]...okay!
  2. Check for files that need to be fixed by 'fixuifiles' [fixuifiles]...okay!
  3. Check validity of i18n calls [i18ncheckarg]...okay!
  4. Check for Qt classes that should not be used [qclasses]...okay!
  5. Check for spelling errors [spelling]...okay!
• For File Type kconfigxt
  1. Check that file ends with a newline [endswithnewline]...okay!
  2. Check validity of i18n calls [i18ncheckarg]...okay!
  3. Check for spelling errors [spelling]...okay!
  4. Validates KConfigXT files using 'xmllint' [validate]...okay!
• For File Type messages
  1. Check for appending to rc.cpp [rcappend]...okay!