Ed Avis

Hi, I believe I came across this while investigating another issue in perlcritic. I was making a minimal test case and I used the filename 0 for my initial program,...

As this bug was originally filed against an older perl version, I checked it with a somewhat newer one. Using 5.26.3 I can still reproduce the same behaviour: ``` %...

Just to 'me too' and to give an example input: ``` use 5.026; use warnings; use strict; package A; our $x = 1; package B; our $x = 2; package...

Since more time has passed since the release of perl 5.26 (on May 30 2017), could I ask you to reconsider in principle adding this as a core policy? If...

A minimal input to perlcritic is OK? Or do you need a purely PPI-based test program?

```` % echo 'sub x {' | perlcritic --brutal - Use of uninitialized value $word in pattern match (m//) at /usr/share/perl5/vendor_perl/PPI/Tokenizer.pm line 836. ... % perlcritic --version 1.126 % perl...

You can reproduce it?

Here's the test case I have so far: ```` use Perl::Critic::Utils; use Module::Pluggable; if ( not @site_policy_names ) { import Module::Pluggable(search_path => $POLICY_NAMESPACE, require => 1); plugins(); } my $s...

Actually I didn't realize it was a fatal error, I thought it was just warning and continuing.

I just mean I didn't notice.