You're absolutely right. You've pointed out more clearly, however, something that I'd already noticed when reading the root node: that the response did not, indeed, actually indicate any possible introduction of bugs. These are problems, but not opportunities for more bugs to be introduced. Rather, they come across as characteristics of a bug. That's not to say that hand-rolled option parsing isn't prone to introducing bugs: it is, as indicated by Fletch. This just means that no indications that it is prone to bugs were clarified in the OP's reply.

In other words, hand-rolled option parsing such as is described here is itself a bug. It introduces its own problems at runtime. It should be fixed as a bug. Luckily, it's a bug with a known, relatively easy solution.

On the other hand, I think that the OP's "positive" approach was more diplomatic than the "negative" approach taken in your rephrasing, andyford. What you posted is excellent for illustration purposes in answering the original question, but is not how I'd address the questions of a coworker (if I was thinking properly at the time) because it might be perceived as accusatory.

print substr("Just another Perl hacker", 0, -2);
 - apotheon
CopyWrite Chad Perrin

In reply to Re^2: Parsing the command line: manual or module? by apotheon
in thread Parsing the command line: manual or module? by bobf

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.