perl::critic::policy::namingconventions::prohibitambiguousnames(3) [centos man page]
Perl::Critic::Policy::NamingConventions::ProhibitAmbiguoUsermContributed Perl DoPerl::Critic::Policy::NamingConventions::ProhibitAmbiguousNames(3)NAME
Perl::Critic::Policy::NamingConventions::ProhibitAmbiguousNames - Don't use vague variable or subroutine names like 'last' or 'record'.
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Conway lists a collection of English words which are highly ambiguous as variable or subroutine names. For example, $last can mean
previous or final.
This policy tests against a list of ambiguous words for variable names.
CONFIGURATION
The default list of forbidden words is:
abstract bases close contract last left no record right second set
This list can be changed by giving a value for "forbid" of a series of forbidden words separated by spaces.
For example, if you decide that "bases" is an OK name for variables (e.g. in bioinformatics), then put something like the following in
"$HOME/.perlcriticrc":
[NamingConventions::ProhibitAmbiguousNames]
forbid = last set left right no abstract contract record second close
BUGS
Currently this policy checks the entire variable and subroutine name, not parts of the name. For example, it catches $last but not
$last_record. Hopefully future versions will catch both cases.
Some variable statements will be false positives if they have assignments where the right hand side uses forbidden names. For example, in
this case the "last" incorrectly triggers a violation.
my $previous_record = $Foo::last;
AUTHOR
Chris Dolan <cdolan@cpan.org>
COPYRIGHT
Copyright (c) 2005-2011 Chris Dolan.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license
can be found in the LICENSE file included with this module.
perl v5.16.3 2014-06-09 Perl::Critic::Policy::NamingConventions::ProhibitAmbiguousNames(3)
Check Out this Related Man Page
Perl::Critic::Policy::Variables::RequireNegativeIndices(User Contributed Perl DocumentPerl::Critic::Policy::Variables::RequireNegativeIndices(3pm)NAME
Perl::Critic::Policy::Variables::RequireNegativeIndices - Negative array index should be used.
AFFILIATION
This Policy is part of the core Perl::Critic distribution.
DESCRIPTION
Conway points out that
$arr[$#arr];
$arr[$#arr-1];
$arr[@arr-1];
$arr[@arr-2];
are equivalent to
$arr[-1];
$arr[-2];
$arr[-1];
$arr[-2];
and the latter are more readable, performant and maintainable. The latter is because the programmer no longer needs to keep two variable
names matched.
This policy notices all of the simple forms of the above problem, but does not recognize any of these more complex examples:
$some->[$data_structure]->[$#{$some->[$data_structure]} -1];
my $ref = @arr;
$ref->[$#arr];
CONFIGURATION
This Policy is not configurable except for the standard options.
AUTHOR
Chris Dolan <cdolan@cpan.org>
COPYRIGHT
Copyright (c) 2006-2011 Chris Dolan.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.14.2 2012-06-07 Perl::Critic::Policy::Variables::RequireNegativeIndices(3pm)
Say
I have a variable set as following
A='IND,US,UK,AUS,NZ'
now i want to know how many words are present in this string ?
In above example,i can see 5 country names set to variable A.
How can i find out that variable A is set to a string containing 5 names(items...whatever) in it?
... (2 Replies)
I have a large database with English on the left hand side and Indic words on the left hand.
It so happens that since the Indic words have been entered by hand, there are duplicates in the entries.
The structure is as under:
English headword=Indic gloss,Indic gloss
A small sample will... (6 Replies)