I ended up with similar problems often enough, so I decided to write something targetted for that particular problem. Most of the solutions I found had a heavy Unix slant, and yet I don't remember a single time I wrote Perl that wasn't meant for Win32, although I never write it on Win32.

So, here it is, in the Code Catacombs.

It has a strong Lispic feel, since it lets you write the predicates that choose the arguments that will be classed. And ... hey, just read the POD.

I should change it to allow more than one argument as a value of the key arguments (something like -o file1 file2 (think GCC args), in which case '-o' will be associated with both 'file1' and 'file2', and enable GCC, to write multiple similar executables with those kinds of args). That's very easy to change, and you can add that in one sweep. My code, by the way, is very clear. I pride myself in that — nobody can take that away from me! :o). It's object-oriented, of course.

Tell I what you think.

(PS: I have it in Py and Clisp, as well, where it has the above-mentioned feature ;o)



print "Something's gone wrong with my head: $!";

In reply to Re: Using a 'getopt' in module code by revence27
in thread Using a 'getopt' in module code by throop

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.