comment on

open( FH , "+<" , $file )
  or die "Unable to open '".$file."' - $!\n";
[download]

Btw. you really should use lexical variables instead of barewords for your filehandles. Especially if you use something obvious like 'FH'.

open( my $fh , "+<" , $file )
  or die "Unable to open '".$file."' - $!\n";
[download]

(and with slightly improved style)

open my $fh, '+<', $file
  or die "Unable to open '$file': $!\n";
[download]

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 localizing 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.

In reply to Re: Bareword "SEEK_END" not allowed while "strict subs" in use by Monk::Thomas
in thread Bareword "SEEK_END" not allowed while "strict subs" in use by thanos1983

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks