xdg,

Thanks for writing Getopt::Lucid. It has always been my module of choice for parsing command line options. It is easy to use for simple and complex cases too. I have a few questions.

Counter()
I'm guessing that each occurence of this command line arg increments the counter.
CSV()
Wouldnt this be a neat option to have? You supply a comma-separated series of values and it appears as a list when you access it: 
./script.pl --csv_arg=a,b,c 

my @arg = $opt->get_csv_arg;

[download]
It wouldnt have to parse all the CSV syntax, just simple CSV. It is more convenient to specify things that way than repeatedly supplying the argument you want to cobble into a list.

In reply to Getopt::Lucid - awesome module, a few questions by metaperl

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.