# predeclare subroutines so subs; can be called before being declared
# and without ()

[download]
subroutines don't have to be declared before you can use them in your code. The don't even have to be declared at compile time. If you are using AUTOLOAD the don't even have to defined when the are executed at runtime.
Also, learning the power of regular expressions will make your code more tighty. The following one line could replace your code that follows 
# one line to make sure there is one and only one "/"
$target_dir=~s<^/*></>;

[download]
Could replace all this: 
#get first character in target_dir
 my $first_char = substr( $target_dir, 0, 1 );

 writeLog( "debug - first character in target_dir $target_dir = $first
+_char" ) if ( $debug );

 if ( $first_char ne '/' ) {
  writeLog( "debug - adding / to beginning of target_dir $target_dir" 
+) if ( $debug );
  #add "/" to beginning of filepath
  $target_dir = '/'.$target_dir;
 }
 else {
  writeLog( "debug - / already exists at beginning. target_dir remains
+ $target_dir" ) if ( $debug );
 }

 #beginning has already been checked for "/" so check for addl
  # "/"s at position 1 ( ///IN/CF/ becomes /IN/CF/ )
 #if position 1 is "/" chop it out and continue until position
  #1 is not a "/"
 writeLog( "debug - checking for multiple '/'s at beginning of target 
+dir $target_dir" ) if ( $debug );
 my $second_char = substr( $target_dir, 1, 1);
 writeLog( "debug - initial second character in target_dir $target_dir
+ = $second_char" ) if ( $debug );
 while ( substr( $target_dir, 1, 1) eq '/' ) {
  writeLog( "debug - removing / from second character in target_dir $t
+arget_dir" ) if ( $debug );
  chop( substr( $target_dir, 1, 1 ) );
  writeLog( "debug - target_dir = $target_dir" ) if ( $debug );
 }

[download]
Also your code has some many comments it makes it hard to read. 
#verify that file exists
 checkFileExists() if ( ! $interactive );

[download]
If your function name is almost exactly the same as your comment, you probably don't need the comment

In reply to Re: Seek Critique of SFTP program, format, structure, overall "Perl"ness by fletcher_the_dog
in thread Seek Critique of SFTP program, format, structure, overall "Perl"ness by mikedshelton

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.