What is your concern? Is the problem that you might have an option "readonly", and another option "runonly", and you are worried that "--r" will be ambiguous from within the application? Or are you concerned that people might grow accustomed to using --r only to later find things break once you've added runonly? If the concern is the former, you needn't worry; Getopt::Long's POD has this to say:

Without additional configuration, GetOptions() will ignore the case of option names, and allow the options to be abbreviated to uniqueness.

GetOptions ('length|height=f' => \$length, "head" => \$head);

[download]

This call will allow --l and --L for the length option, but requires a least --hea and --hei for the head and height options.

So the first possible issue is unfounded, and documented in the module's POD (which the author spent time writing with the hope that you, the user, would read).

The second possible issue is a social one; the concern that people will get in the habit of using the abbreviations, only to have them become invalidated by the addition of options that push uniqueness further along in the option's string. And for that, the POD is also helpful, by documenting the auto_abbrev configuration setting.


Dave

In reply to Re: how to get the exact option string in Getopt::Long module by davido
in thread how to get the exact option string in Getopt::Long module by chidori

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.