I'm curious how many use.perl.org readers are using Perl::Critic, a static source code analyzer. So, here's a very unscientific poll. Please respond by commenting below. You may select more than one response.
1) Using Perl:Critic
o I am unfamiliar with Perl::Critic
o I've been meaning to try Perl::Critic
o I've tried Perl::Critic, but it's too hard
o I've tried Perl::Critic, but it's too strict
o I use Perl::Critic on some of my code
o I use Perl::Critic on all of my code
2) Perl::Critic policies
o I use a small subset of the Perl::Critic policies
o I use most of the Perl::Critic policies
o I use all of the Perl::Critic policies
o I use 3rd party policies from CPAN
o I use home-grown policies
3) Configuration
o I use the defaults
o I use bin/perlcritic cmdline options
o I use a global $HOME/.perlcriticrc
o I use a per-module perlcriticrc
o I configure Perl::Critic programmatically
4) Wrapper modules
o I use Test::Perl::Critic
o I use criticism.pm
o I use perlcritic.com
o None of the above
Thanks! This is just for my curiosity, but if there's enough of a response to get a consensus, I'll try to use this to drive future development.
1) Using Perl::Critic
o I'm familiar with Perl::Critic but haven't felt the need to try it
Sorry -- I think it's an amazing tool, but in the midst of other things, it hasn't made it onto my list of things to try out in the spare bits of time I have.
Re:informal response
ChrisDolan on 2006-09-18T01:18:37
No apologies needed. I haven't yet tried vanilla or strawberry perl.:-)
I try to recommend it and use it at clients as well but in most cases just including 'use strict' would do wonders to their code. In such cases Perl::Critic is an overkill.
1) Using Perl::Critic
o) I'm familiar with Perl::Critic and don't see a reason to use it.
Re:__
ChrisDolan on 2006-09-22T14:06:27
Fair enough! I should have added that option in the original poll. I guess my bias was showing through.:-)