Advertisement
Guest User

Untitled

a guest
Feb 8th, 2016
58
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.85 KB | None | 0 0
  1. "--verbose N | FORMAT"
  2. Sets the verbosity level or format for reporting violations. If given
  3. a number ("N"), "perlcritic" reports violations using one of the
  4. predefined formats described below. If given a string ("FORMAT"), it
  5. is interpreted to be an actual format specification. If the
  6. "--verbose" option is not specified, it defaults to either 4 or 5,
  7. depending on whether multiple files were given as arguments to
  8. "perlcritic". You can set the default value for this option in your
  9. .perlcriticrc file.
  10.  
  11. Verbosity Format Specification
  12. ----------- -------------------------------------------------------
  13. 1 "%f:%l:%c:%m\n",
  14. 2 "%f: (%l:%c) %m\n",
  15. 3 "%m at %f line %l\n",
  16. 4 "%m at line %l, column %c. %e. (Severity: %s)\n",
  17. 5 "%f: %m at line %l, column %c. %e. (Severity: %s)\n",
  18. 6 "%m at line %l, near '%r'. (Severity: %s)\n",
  19. 7 "%f: %m at line %l near '%r'. (Severity: %s)\n",
  20. 8 "[%p] %m at line %l, column %c. (Severity: %s)\n",
  21. 9 "[%p] %m at line %l, near '%r'. (Severity: %s)\n",
  22. 10 "%m at line %l, column %c.\n %p (Severity: %s)\n%d\n",
  23. 11 "%m at line %l, near '%r'.\n %p (Severity: %s)\n%d\n"
  24.  
  25. Formats are a combination of literal and escape characters similar to
  26. the way "sprintf" works. See String::Format for a full explanation of
  27. the formatting capabilities. Valid escape characters are:
  28.  
  29. Escape Meaning
  30. ------- ------------------------------------------------------------
  31. %c Column number where the violation occurred
  32. %d Full diagnostic discussion of the violation
  33. %e Explanation of violation or page numbers in PBP
  34. %F Just the name of the file where the violation occurred.
  35. %f Path to the file where the violation occurred.
  36. %l Line number where the violation occurred
  37. %m Brief description of the violation
  38. %P Full name of the Policy module that created the violation
  39. %p Name of the Policy without the Perl::Critic::Policy:: prefix
  40. %r The string of source code that caused the violation
  41. %C The class of the PPI::Element that caused the violation
  42. %s The severity level of the violation
  43.  
  44. The purpose of these formats is to provide some compatibility with
  45. text editors that have an interface for parsing certain kinds of
  46. input. See "EDITOR INTEGRATION" for more information about that.
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement