First of all it is not a "Getopt problem". The error message comes from cp ins your system() calls. The logical Problem of $xmllocation and $xsllocation never being empty strings is another.

GetOptions( "u|updated:s" => \my $update, "x|XMLFile:s" => \my $xmllocation, "e|XLSFile:s" => \my $xlsfile, ); $update or die "..."; $xmllocation or print "blabla"; $xlslocation or print "blablabla"; #And in your routine system(qq(sjdks $xmlfile)) if $xmlfile; #dito for $xlsfile

I prefer the non-global method, in this case it saves variables. Consider using File::Copy for copying your files, it's better.

--
http://fruiture.de

In reply to Re: Getopt problem by fruiture
in thread Getopt problem by Sara

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.