That looked totally wrong. (and your end-tags miss a / (/code instead of just code).

sub usage { my $err = shift and select STDERR; print "usage: $0 ...\n"; exit $err; } # usage use Getopt::Long qw(:config bundling); my $be_consistent = 0; my $sum = 0; my $threshold = 0.0; my @junk_files; GetOptions ( "h|help" => sub { usage (0) }, "c|consistent!" => \$be_consistent, "s|sum!" => \$sum, "threshold:f" => \$threshold, "junk_files=s" => \@junk_files, ) or usage (1);

As suggested, you should read the manual.

As a side note, I have no idea what --no-help would do :)


Enjoy, Have FUN! H.Merijn

In reply to Re: {,} in GetOptions produces error by Tux
in thread {,} in GetOptions produces error by pestcat

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.