NAME

Perl::Critic::Policy::ValuesAndExpressions::ProhibitInterpolationOfLiterals

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\n";   #ok
print qq/$foobar/;  #ok
print qq/foobar\n/; #ok

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

CONSTRUCTOR

This Policy accepts an additional key-value pair in the constructor, The key is 'allow' and the value is a string of quote styles that are exempt from this policy. Valid styles are qq{}, qq(), qq[], and qq//. Multiple styles should be separated by whitespace. 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[]

SEE ALSO

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

AUTHOR

Jeffrey Ryan Thalhammer <thaljef@cpan.org>

COPYRIGHT

Copyright (c) 2005-2006 Jeffrey Ryan Thalhammer. 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.