Ok.. your use of @_ is just plain wrong, which is your main problem... we'll forgive it since you are learning :)

You use strict and warnings, that is good.
You use @_ so strict doesn't complain when you don't declare a variable, that is bad.

@_ is a special variable that Perl uses to provide you with the arguments that were passed to a subroutine. (which is why strict ignores it). What is happening is that you set @_ to two values, you then call handle_fix. Perl then silently replaces the values in @_ with that arguments passed to the subroutine (empty array), and runs the sub. On return Perl restores the old values of @_ and merrily continues along, making you angry :)

I would change the code to something more like...

se strict;
use warnings;

#why negate, reverse the operations. Also, specifying STDIN is more se
+lf documenting.
my $infile  = @ARGV ? shift(@ARGV) : <STDIN>;
my $outfile = @ARGV ? shift(@ARGV) : <STDIN>;

handlefix($infile,$outfile);

open(INFILE, '<', $infile) or die "\nCan't open $infile: $!\n";
open(OUTFILE, '>', $outfile) or die "\nCan't open $outfile: $!\n";

print OUTFILE 
               map { my $s=$_; $s=~s/\s*#.*$//; $s } 
              (grep { !/^\s*#/ } <INFILE>), "\n"   ; 

#close INFILE && close OUTFILE; close returns a value... if the first 
+close fails Perl will ignore second close

close INFILE;
close OUTFILE; 

sub handlefix {
    for(@_){
        chomp($_);
        $_=~s/"//g;
        $_=~s/\//\\/g;
    }
}
[download]

Now... keep in mind iterating through @_ and changing $_ directly WILL change the arguments passed to your sub, but is generally not the best practice. It is not obvious that the args are being changed and later that can bite you or someone else maintaining the code... a better way might be...

sub handlefix {
    my @return;
    for(@_){
        my $val = $_; #decouple the value from the argument variable
        chomp($val);
        $val =~ s/"//g;
        $val =~ s/\//\\/g;
    }
    return @return;
}
($infile,$outfile) = handlefix($infile,$outfile); #more obvious what i
+s happening
[download]

Hope that helps

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.