Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • by sigzero (5768) on 2006.08.17 12:44 (#49422) Journal
    I use P::C all the time.
    • Great! Have any features you'd like added? Any additional policies you'd like to see enforced?

      Our TODO.pod is big already, but I'd love to add more good ideas to it.
      • I have a minor nit/suggestion. In the pod/docs for each policy, it would be nice if it mentioned the default severity level for each policy module.

        I found myself viewing source on every module trying to fine out which severity level it applied to.

        In the end, I ended up setting my test file to severity = 1, and then making a policy for each dist that customized or disabled the policies that didn't jive w/ the dist. Kind of a All On By Default thing. Then when new policies come out, I'll automaticaly catch th
        • I recommend "bin/perlcritic -list" which lists all of the policies by package name and severity.

          On the developer mail list, we're discussing transforming the severity system into a more generic tagging system. My hope is that we'll implement that for v1.0 within the next month.
      • Also, I think Variables::ProhibitPunctuationVars should be tweakable imho.

        I agree with most of it, but I'd like ti be able to tell it to except $@ as well.
        • Your wish is my command. :-)

          I just committed a patch to SVN that implements the following example:

              [Variables::ProhibitPunctuationVars]
              allow = $@ $!

          This feature will be present in the forthcoming v0.19.