Re: Code Reviews -- List Identifiers

[arkturuz]

There are many options. If you would like to script something of your own, you could use PPI for custom source code analysis. There's also Perl::Critic which is mostly used for this kind of things with its set of predefined rules.

[tobyink]

Here's a quick PPI example:

use v5.12;
use PPI;

my $perl = PPI::Document::->new(do { local $/ = <DATA>; \$/ });

say $_ for @{ $perl->find('PPI::Token::Symbol') };

__DATA__
# Some sample code to analyse

my $foo = 1;
my @bar = (2, 3);
say $bar[0];

The output includes a variable called $bar which doesn't really exist :-( But that shouldn't be a problem for the OP's use case.

[Anonymous Monk]

Specifically look at
Perl::Critic::Policy::Variables::ProhibitReusedNames - Do not reuse a variable name in a lexical scope
Perl::Critic::Policy::Variables::ProhibitUnusedVariables - Don't ask for storage you don't need.

And Perl::Critic::Policy is xpaths