Bob Rogers wrote: > Tom Metro wrote: >> ...'use criticism' imposes a lot of overhead and isn't recommend for >> use in production... > > But, at the risk of being obscure, you don't have to "use" it in order > to take advantage of it. The Parrot project has started employing > Perl::Critic from "make test"...
Sure. I don't think that's being obscure at all, and such usage was clearly pointed out in the man page. It's a perfectly logical way to employ it. I'm just pointing out that from what I've read, I'm guessing the group that finds Perl to be "unreadable" would consider that an insufficient solution. Perhaps fearing that it is too easy to skip the style enforcement step. Really it isn't any different from the way some projects might have incorporated processing through 'lint' into their build process. It seems like an adequate solution to me. > Then again, the real issue is probably groupthink, > which is usually impervious to any argument. Yup. -Tom -- Tom Metro Venture Logic, Newton, MA, USA "Enterprise solutions through open source." Professional Profile: http://tmetro.venturelogic.com/ _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
