perl::critic::policy::valuesandexpressions::prohibitinterpolatio(3) [centos man page]

Perl::Critic::Policy::ValuesAndExpressions::ProhibitInteUseraContribPerl::Critic::Policy::ValuesAndExpressions::ProhibitInterpolationOfLiterals(3)

NAME

       Perl::Critic::Policy::ValuesAndExpressions::ProhibitInterpolationOfLiterals - Always use single quotes for literal strings.

AFFILIATION

       This Policy is part of the core Perl::Critic distribution.

DESCRIPTION

       Don't use double-quotes or "qq//" if your string doesn't require interpolation.	This saves the interpreter a bit of work and it lets the
       reader know that you really did intend the string to be literal.

	   print "foobar";     #not ok
	   print 'foobar';     #ok
	   print qq/foobar/;   #not ok
	   print q/foobar/;    #ok

	   print "$foobar";    #ok
	   print "foobar
";   #ok
	   print qq/$foobar/;  #ok
	   print qq/foobar
/; #ok

	   print qq{$foobar};  #preferred
	   print qq{foobar
}; #preferred

       Use of double-quotes might be reasonable if the string contains single quote (') characters:

	   print "it's me";    # ok, if configuration flag set

CONFIGURATION

       The types of quoting styles to exempt from this policy can be configured via the "allow" option.  This must be a whitespace-delimited
       combination of some or all of the following styles: "qq{}", "qq()", "qq[]", and "qq//".

       This is useful because some folks have configured their editor to apply special syntax highlighting within certain styles of quotes.  For
       example, you can tweak "vim" to use SQL highlighting for everything that appears within "qq{}" or "qq[]" quotes.  But if those strings are
       literal, Perl::Critic will complain.  To prevent this, put the following in your .perlcriticrc file:

	   [ValuesAndExpressions::ProhibitInterpolationOfLiterals]
	   allow = qq{} qq[]

       The flag "allow_if_string_contains_single_quote" permits double-quoted strings if the string contains a single quote (') character.  It
       defaults to off; to turn it on put the following in your .perlcriticrc file:

	   [ValuesAndExpressions::ProhibitInterpolationOfLiterals]
	   allow_if_string_contains_single_quote = 1

SEE ALSO

       Perl::Critic::Policy::ValuesAndExpressions::RequireInterpolationOfMetachars

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::ProhibitInterpolationOfLiterals(3)

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)