Well .. that'd work. I'd normally use something like this, though: 
my $StartDir = shift @ARGV or die "Usage: $0 <startdir>\n";

[download]
That way, it's immediately obvious to the user that you expect a single parameter, which is a directory to start in, and it's obvious to someone maintaining your code exactly what you expect and where it comes from. $0 simply echos the command used to run the script.

One small bug: shift shifts from @_ by default, not @ARGV - you'll need to explictly specify @ARGV to read command line parameters.

You won't need to chomp a parameter normally, no - the newline isn't passed into the script by the shell.

Hope that helps.

-- Foxcub
#include www.liquidfusion.org.uk

Update: Struck out an (obvious) mistake, now I think about it and it's been pointed out :) (thanks, fletcher_the_dog)

In reply to Re: Checking for data entry by Tanalis
in thread Checking for data entry 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.