Personally, I would have written your code as follows: (UNTESTED !!!)
#!/usr/local/bin/perl -w
use strict;

my $params=@ARGV;
my ($input,$output,$length);

if($params < 3){
  die "Not enough parameters";
}else{
  ($input,$output,$length)= @ARGV;
}

open(INFILE,"$input")||die "Can't open $input: $!\n";
open(OUTFILE,">$output")||die "Can't open $output: $!\n";

my $count=1;

while(<INFILE>){
  chomp;
  if(/>/){ ++$count; }
  if(length($_) >= $length){
    print "\>$count\n",$line,"\n\n";
    print OUTFILE "\>$count\n",$line,"\n\n";
  }
}

close INFILE;
close OUTFILE;

[download]


UPDATE:Changed code per Biker's suggestion. And what is really sad, is that I actually had it right the first time, and changed it. :-(

TStanley
--------
Never underestimate the power of very stupid people in large groups -- Anonymous

In reply to Re: confused by TStanley
in thread @ARGV / Command Line Arguments by Anonymous Monk

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.