Bill, We can exclude specific "policies" in the code with specially formatted comments. The "M" in this (RTFM) case is here:
http://search.cpan.org/~elliotjs/Perl-Critic-1.096/lib/Perl/Critic.pm#BENDIN G_THE_RULES The specific policies aren't properly linked, but Google knows all: http://search.cpan.org/~elliotjs/Perl-Critic-1.082/lib/Perl/Critic/PolicySum mary.pod I haven't actually figured out which policy to exclude yet though. Roger -----Original Message----- From: Bill Ward [mailto:b...@wards.net] Sent: Wednesday, February 18, 2009 11:11 AM To: raha...@ualr.edu Subject: Re: ARGH! (was FW: Perl Critic and (honest) hash references) What was the solution? On Wed, Feb 18, 2009 at 8:53 AM, Roger Hall <raha...@ualr.edu> wrote: > RTFM is always pretty good advice, eh? :} > > -----Original Message----- > From: Roger Hall [mailto:raha...@ualr.edu] > Sent: Wednesday, February 18, 2009 10:05 AM > To: module-authors@perl.org > Subject: Perl Critic and (honest) hash references > > > $config->{query} > > > Perlcritic complains that "Private Member Data shouldn't be accessed > directly" because "Accessing an objects data directly breaks encapsulation > and should be avoided". I get that. Only problem: it's not an object. It's > just a hashref.
