Yes, I have to admit I also occasionally had hand-hacked parsing for those one or two options. In the meantime, I've learned from those mistakes, i.e. I use Getopt::Long as soon as the first option idea pops up in my mind... because I know it won't be the last. Not only is it less work, it's also so much more flexible and DWIM.

On the other hand, I'd say it's never too late. And, as any option parsing is typically done in some central place anyway (rather than being scattered all over the program), replacing it with Getopt::Long has usually been a matter of less than five minutes — unless you postpone that decision until your tool has as many options as gcc...

In reply to Re: Use Getopt::Long even if you don't think you need to by almut
in thread Use Getopt::Long even if you don't think you need to by ysth

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.