open my $fh, "<foo.txt";
[download]

Andrew.

Yes. Additionally you can use the FileHandle module:

use FileHandle;
sub Whatever 
{
    my $filehandle = new FileHandle;
    open $filehandle, $file or die "Failed to open $file, $!";
    # do stuff.
    close $filehandle or die "Failed to close $file, $!";
}
[download]

But that wasn't my point.

I was going to add "which only goes to show that by posting here you find out several other ways to do the same thing", but it seems I forgot.

Andrew.

sub foo {
    my ($file, $info) = @_;
    local *FH;
    open (FH, ">" . $file) or die "$!\n";
    print FH $info;
    close FH;
    }
[download]

Interesting. I'll have to watch for that. Although I suspect that it had more to do with perl threads not being fully stable and less to with different threads writing to the same filehandle, since they shouldn't be able to see each other's local typeglobs (they should be out of scope).

The way my boss explained it to me was that local copies the global typeglob, grabs it for local use, and replaces it with a copy of what it grabbed. Thus, any read/write is done on the global FH, even though it is being used in a local scope. The next thread does the same thing, although it copies the typeglob that's being locally used by the first thread (it _is_ still the global one, it's just not being treated as such by the thread). So when the second thread grabs local *FH, it's not grabbing a clean undef typeglob. It's actually grabbing a copy of the typeglob that thread 1 is currently working with, with whatever I/O garbage thread one had in the FH at that particular time. Which is why local sucks in general, and why my rocks my world.

Disclaimer:At least this is what i think he said.Most people that can detail the changes that occured in the low level file handling structure of perl when 3.0 was released tend to explain things in depths that this PH can't always understand:-)

BlueLines