Hey all, I'm trying to port a script to win32 from a unix box. I'm running into trouble with a "bad file descrtiptor" when trying to close a file handle. Here is my code:

sub parse_mail {
    my $mail = $_[0];
    print $mail;
    open (MAIL,$mail) || die "Cannot open $mail, $!";
        @mailf = <MAIL>;
        chomp (@mailf);
        my $line;
        foreach $line (@mailf) {
                print $line;
                }
        print @mailf;
    close (MAIL) || die "Cannot close $mail, $!";

    return @mailf;    
}
[download]

When the script gets to the  close (MAIL) I get an error stating

Cannot close C:/windows/desktop/tmp/test.f2mail,
Bad file descriptor
[download]

The file stated in the error is correct and is what I'm looking for. I'm using forward slashes in the pathname... I've also used single quotes and "\\" to try and get the script to work, but no luck. The print $mail statement, I put in to watch the variable, displays the correct file and path name. I'm using ActiveState and Perl Builder. I would greatly appreciate any help anybody can offer. Thanks in advance for any help anyone can provide. Bradley

Where ever there is confusion to be had... I'll be there.
[download]

---

---

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