Perl::Critic::PPeorlli:c:yC:r:iIUtnsipecur:t:OCPuootnlptiurctiy:b::u:PtIrenodphuiPtbeOirutltBpaDurotec:wu:omPrerdnoFthiailtbeiiHotanBnadrleewso(r3d)FileHandles(3)



NNAAMMEE
       Perl::Critic::Policy::InputOutput::ProhibitBarewordFileHandles - Write
       "open my $fh, q{<}, $filename;" instead of "open FH, q{<}, $filename;".

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

DDEESSCCRRIIPPTTIIOONN
       Using bareword symbols to refer to file handles is particularly evil
       because they are global, and you have no idea if that symbol already
       points to some other file handle.  You can mitigate some of that risk
       by "local"izing the symbol first, but that's pretty ugly.  Since Perl
       5.6, you can use an undefined scalar variable as a lexical reference to
       an anonymous filehandle.  Alternatively, see the IO::Handle or IO::File
       or FileHandle modules for an object-oriented approach.

           open FH, '<', $some_file;           #not ok
           open my $fh, '<', $some_file;       #ok
           my $fh = IO::File->new($some_file); #ok

       There are three exceptions: STDIN, STDOUT and STDERR.  These three
       standard filehandles are always package variables.

CCOONNFFIIGGUURRAATTIIOONN
       This Policy is not configurable except for the standard options.

SSEEEE AALLSSOO
       IO::Handle

       IO::File

AAUUTTHHOORR
       Jeffrey Ryan Thalhammer <jeff@imaginative-software.com>

CCOOPPYYRRIIGGHHTT
       Copyright (c) 2005-2010 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.



perl v5.12.2 Perl::Critic::Policy:2:0I1n3p-u0t3O-u1t6put::ProhibitBarewordFileHandles(3)
