Personally, I try to organize in a way that makes sense and is relatively easy to read. To me, that would mean putting the simple options in some order (either by type or, more likely for me, in alphabetical order), then putting more complex items (such as your "all" option) lower (also ordered), with the "help" option (if present) at the end. (I would also probably have the help() sub close by, so it would be easy to remember to update if an option were added/removed/changed.) I might also consider storing those configuration options in a hash, so as to make passing them easier.

Hope that helps, and I look forward to the responses you get on this thread for the possibility of ideas to consider as well.

In reply to Re: GetOpt Organization by atcroft
in thread GetOpt Organization by KurtSchwind

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.