Hi,

MooseX::GetOpt just translates options to following call to Getopt::Long::Descriptive 

use Getopt::Long::Descriptive;

my ($opt, $usage) = describe_options(
    'usage: mxgotest.pl [-?] [long options...]',
    [   'help|usage|?!' => 'Prints this usage information.' ],
    [   'name=s'        => 'Sets the name', { required => 1 } ],
);

[download]

The message is caused by required parameter. From the GLD docs:

If an option is required, failure to provide the option will result in describe_options printing the usage message and exiting.

I would remove the required from the name attribute and implemented the functionality after new_with_options call.

-- Roman

In reply to Re: MooseX::Getopt help without nagging by bobr
in thread MooseX::Getopt help without nagging by Boldra

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.