Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

perl::critic::policy::valuesandexpressions::prohibitcommaseparat(3pm) [debian man page]

Perl::Critic::Policy::ValuesAndExpressions::ProhibitCommUseraContPerl::Critic::Policy::ValuesAndExpressions::ProhibitCommaSeparatedStatements(3pm)

NAME
Perl::Critic::Policy::ValuesAndExpressions::ProhibitCommaSeparatedStatements - Don't use the comma operator as a statement separator. AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
Perl's comma statement separator has really low precedence, which leads to code that looks like it's using the comma list element separator not actually doing so. Conway suggests that the statement separator not be used in order to prevent this situation. The confusion that the statement separator causes is primarily due to the assignment operators having higher precedence. For example, trying to combine two arrays into another like this won't work: @x = @y, @z; because it is equivalent to @x = @y; @z; Conversely, there are the built-in functions, like "print", that normally force the rest of the statement into list context, but don't when called like a subroutine. This is not likely to produce what is intended: print join q{, }, 2, 3, 5, 7, ": the single-digit primes. "; The obvious fix is to add parentheses. Placing them like print join( q{, }, 2, 3, 5, 7 ), ": the single-digit primes. "; will work, but print ( join q{, }, 2, 3, 5, 7 ), ": the single-digit primes. "; will not, because it is equivalent to print( join q{, }, 2, 3, 5, 7 ); ": the single-digit primes. "; CONFIGURATION
This policy can be configured to allow the last statement in a "map" or "grep" block to be comma separated. This is done via the "allow_last_statement_to_be_comma_separated_in_map_and_grep" option like so: [ValuesAndExpressions::ProhibitCommaSeparatedStatements] allow_last_statement_to_be_comma_separated_in_map_and_grep = 1 With this option off (the default), the following code violates this policy. %hash = map {$_, 1} @list; With this option on, this statement is allowed. Even if this option is off, using a fat comma "=>" works, but that forces stringification on the first value, which may not be what you want. BUGS
Needs to check for "scalar( something, something )". AUTHOR
Elliot Shank "<perl@galumph.com>" COPYRIGHT
Copyright (c) 2007-2011 Elliot Shank. 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.14.2 Perl::Critic::Policy::ValuesAndExpressions::ProhibitCommaSeparatedStatements(3pm)

Check Out this Related Man Page

Perl::Critic::Policy::ValuesAndExpressions::RequireInterUsertContribPerl::Critic::Policy::ValuesAndExpressions::RequireInterpolationOfMetachars(3)

NAME
Perl::Critic::Policy::ValuesAndExpressions::RequireInterpolationOfMetachars - Warns that you might have used single quotes when you really wanted double-quotes. AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
This policy warns you if you use single-quotes or "q//" with a string that has unescaped metacharacters that may need interpolation. Its hard to know for sure if a string really should be interpolated without looking into the symbol table. This policy just makes an educated guess by looking for metacharacters and sigils which usually indicate that the string should be interpolated. Exceptions o Variable names to "use vars": use vars '$x'; # ok use vars ('$y', '$z'); # ok use vars qw< $a $b >; # ok o Things that look like e-mail addresses: print 'john@foo.com'; # ok $address = 'suzy.bar@baz.net'; # ok CONFIGURATION
The "rcs_keywords" option allows you to stop this policy from complaining about things that look like RCS variables, for example, in deriving values for $VERSION variables. For example, if you've got code like our ($VERSION) = (q<$Revision: 4126 $> =~ m/(d+)/mx); You can specify [ValuesAndExpressions::RequireInterpolationOfMetachars] rcs_keywords = Revision in your .perlcriticrc to provide an exemption. NOTES
Perl's own "warnings" pragma also warns you about this. SEE ALSO
Perl::Critic::Policy::ValuesAndExpressions::ProhibitInterpolationOfLiterals AUTHOR
Jeffrey Ryan Thalhammer <jeff@imaginative-software.com> COPYRIGHT
Copyright (c) 2005-2011 Imaginative Software Systems. All rights reserved. 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 Perl::Critic::Policy::ValuesAndExpressions::RequireInterpolationOfMetachars(3)
Man Page