This should work for your ParseSub if you are using "cmd /b" as your listing command. 
 sub get_list {
    my @file_list;
    foreach my $ele (@_){
        my ($name);
        if(-d (getcwd."/$ele")){
          $name = 'IsDirectory';
        }else{
          $name = 'IsPlainFile';
        }
        my $filename = getcwd."/$ele";
        
        my ($dev,$ino,$mode,$nlink,$uid,$gid,$rdev,$size,
           $atime,$mtime,$ctime,$blksize,$blocks)
               = stat($filename);
        
        my @fields = ($mode,$nlink,$uid,$gid,$size,$mtime,$ele);
        push(@file_list,Net::FTP::Recursive::File->new(OriginalLine =>
+ $ele, Fields => \@fields, $name => 1));
    } 
    return @file_list;
}

[download]

- Tom

In reply to Re: Net::Ftp::Recursive ParseSub Help by tcf22
in thread Net::Ftp::Recursive ParseSub Help by bear0053

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.