There's a possibility you're taking the wrong approach.

Consider:

  1. Breaking up your cli into smaller pieces

    I.E. If your 'bin/cli' will clean the car if you pass it the --clean-car flag, consider moving that functionality to 'bin/clicleancar'

  2. Using a data file as input

    If this is a complex procedure, would it be useful to accept as input a YAML config file as option paramaters?

Ultimately you're the judge of this.

You may be in a situation a-la imagemagick, or mplayer .. these projects have already broken up their functionality into mplayer/mencoder/etc.. and convert/mogrify/etc. But the nature of the beast is such- that their cli is a monster.

In reply to Re: Processing Complicated Command Line Options using Getopt by leocharre
in thread Processing Complicated Command Line Options using Getopt by ganeshts

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.