This is a very labor-intensive solution to the arguments problem, but here goes.

Edit each of the scripts to respond to a set input. For instance "mytool -h" might return a specification of the arguments that the tool accepts and perhaps a description of their effects that you could parse automatically. Perhaps you could use xml. You would want to look out for optional inputs, required inputs, modes, etc.

Since it sounds like you have a lot of existing scripts, you might want to just write a quick perl wrapper for each of the existing tools that could return this description if called with no arguments, or runs the intended tool with whatever arguments are supplied. New scripts that you write could then support this self-specification protocol and do away with the wrapper. Just point your program at the directory of wrappers and it would be able to automatically determine what sort of arguments each tool needs.

Using this method, you wouldn't need some sort of database that would need to be maintained seperately, the tool itself (or its wrapper) would advertise its interface.

In reply to Re: Need feedback on a wrapper script design. by griff
in thread Need feedback on a wrapper script design. by selk

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.