coldguy was right, you cannot use a reference as a hash key. Also, I don't think you can use unlink on a filehandle ... just a filename. If you want to stay the same path, I would just expand your structure a bit:

#!/usr/local/bin/perl use strict; my $files = [ { name => 'file1.txt', fh => undef, unlink => 1 }, { name => 'file2.txt', fh => undef, unlink => 1 }, { name => 'file3.txt', fh => undef, unlink => 1 }, ]; foreach my $file ( @$files ) { open( $file->{fh}, '>', $file->{name} ) or quit( $files, "Cannot open $file->{name}: $!" ); } quit( $files, "CloseUnlinkTest.pl finished" ); sub quit { my( $files, $message ) = @_; foreach my $file ( @$files ) { close( $file->{fh} ) if $file->{fh}; unlink( $file->{name} ) if $file->{unlink}; } }

-derby

In reply to Re: Trouble Passing File Handles by derby
in thread Trouble Passing File Handles by Photius

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.