Getopt-Long-Descriptive
view release on metacpan or search on metacpan
lib/Getopt/Long/Descriptive.pm view on Meta::CPAN
#pod hidden => 1
#pod
#pod This option will not show up in the usage text.
#pod
#pod You can achieve the same behavior by using the string "hidden" for the option's
#pod description.
#pod
#pod =item one_of
#pod
#pod one_of => \@subopt_specs
#pod
#pod This is useful for a group of options that are related. Each option
#pod spec is added to the list for normal parsing and validation.
#pod
#pod Your option name will end up with a value of the name of the
#pod option that was chosen. For example, given the following spec:
#pod
#pod [ "mode" => hidden => { one_of => [
#pod [ "get|g" => "get the value" ],
#pod [ "set|s" => "set the value" ],
#pod [ "delete" => "delete it" ],
#pod ] } ],
#pod
#pod No usage text for 'mode' will be displayed, but text for get, set, and delete
#pod will be displayed.
#pod
#pod If more than one of get, set, or delete is given, an error will be thrown.
#pod
#pod So, given the C<@opt_spec> above, and an C<@ARGV> of C<('--get')>, the
#pod following would be true:
#pod
#pod $opt->get == 1;
#pod
#pod $opt->mode eq 'get';
#pod
#pod B<Note>: C<get> would not be set if C<mode> defaulted to 'get' and no arguments
#pod were passed in.
#pod
#pod Even though the option sub-specs for C<one_of> are meant to be 'first
#pod class' specs, some options don't make sense with them, e.g. C<required>.
#pod
#pod As a further shorthand, you may specify C<one_of> options using this form:
#pod
#pod [ mode => \@option_specs, \%constraints ]
#pod
#pod
#pod =item shortcircuit
#pod
#pod shortcircuit => 1
#pod
#pod If this option is present no other options will be returned. Other
#pod options present will be checked for proper types, but I<not> for
#pod constraints. This provides a way of specifying C<--help> style options.
#pod
#pod =item Params::Validate
#pod
#pod In addition, any constraint understood by Params::Validate may be used.
#pod
#pod For example, to accept positive integers:
#pod
#pod [ 'max-iterations=i', "maximum number of iterations",
#pod { callbacks => { positive => sub { shift() > 0 } } } ],
#pod
#pod (Internally, all constraints are translated into Params::Validate options or
#pod callbacks.)
#pod
#pod =back
#pod
#pod =head3 %arg
#pod
#pod The C<%arg> to C<describe_options> is optional. If the last parameter is a
#pod hashref, it contains extra arguments to modify the way C<describe_options>
#pod works. Valid arguments are:
#pod
#pod getopt_conf - an arrayref of strings, passed to Getopt::Long::Configure
#pod show_defaults - a boolean which controls whether an option's default
#pod value (if applicable) is shown as part of the usage message
#pod (for backward compatibility this defaults to false)
#pod
#pod =head2 prog_name
#pod
#pod This routine, exported on demand, returns the basename of C<$0>, grabbed at
#pod compile-time. You can override this guess by calling C<prog_name($string)>
#pod yourself.
#pod
#pod =head1 OTHER EXPORTS
#pod
#pod =head2 C<-types>
#pod
#pod Any of the Params::Validate type constants (C<SCALAR>, etc.) can be imported as
#pod well. You can get all of them at once by importing C<-types>.
#pod
#pod =head2 C<-all>
#pod
#pod This import group will import C<-type>, C<describe_options>, and C<prog_name>.
#pod
#pod =cut
my $prog_name;
sub prog_name { @_ ? ($prog_name = shift) : $prog_name }
BEGIN {
# grab this before someone decides to change it
prog_name(File::Basename::basename($0));
}
use Sub::Exporter::Util ();
use Sub::Exporter 0.972 -setup => {
exports => [
describe_options => \'_build_describe_options',
q(prog_name),
@{ $Params::Validate::EXPORT_TAGS{types} }
],
groups => [
default => [ qw(describe_options) ],
types => $Params::Validate::EXPORT_TAGS{types},
],
};
my %CONSTRAINT = (
implies => \&_mk_implies,
lib/Getopt/Long/Descriptive.pm view on Meta::CPAN
hidden => 1
This option will not show up in the usage text.
You can achieve the same behavior by using the string "hidden" for the option's
description.
=item one_of
one_of => \@subopt_specs
This is useful for a group of options that are related. Each option
spec is added to the list for normal parsing and validation.
Your option name will end up with a value of the name of the
option that was chosen. For example, given the following spec:
[ "mode" => hidden => { one_of => [
[ "get|g" => "get the value" ],
[ "set|s" => "set the value" ],
[ "delete" => "delete it" ],
] } ],
No usage text for 'mode' will be displayed, but text for get, set, and delete
will be displayed.
If more than one of get, set, or delete is given, an error will be thrown.
So, given the C<@opt_spec> above, and an C<@ARGV> of C<('--get')>, the
following would be true:
$opt->get == 1;
$opt->mode eq 'get';
B<Note>: C<get> would not be set if C<mode> defaulted to 'get' and no arguments
were passed in.
Even though the option sub-specs for C<one_of> are meant to be 'first
class' specs, some options don't make sense with them, e.g. C<required>.
As a further shorthand, you may specify C<one_of> options using this form:
[ mode => \@option_specs, \%constraints ]
=item shortcircuit
shortcircuit => 1
If this option is present no other options will be returned. Other
options present will be checked for proper types, but I<not> for
constraints. This provides a way of specifying C<--help> style options.
=item Params::Validate
In addition, any constraint understood by Params::Validate may be used.
For example, to accept positive integers:
[ 'max-iterations=i', "maximum number of iterations",
{ callbacks => { positive => sub { shift() > 0 } } } ],
(Internally, all constraints are translated into Params::Validate options or
callbacks.)
=back
=head3 %arg
The C<%arg> to C<describe_options> is optional. If the last parameter is a
hashref, it contains extra arguments to modify the way C<describe_options>
works. Valid arguments are:
getopt_conf - an arrayref of strings, passed to Getopt::Long::Configure
show_defaults - a boolean which controls whether an option's default
value (if applicable) is shown as part of the usage message
(for backward compatibility this defaults to false)
=head2 prog_name
This routine, exported on demand, returns the basename of C<$0>, grabbed at
compile-time. You can override this guess by calling C<prog_name($string)>
yourself.
=head1 OTHER EXPORTS
=head2 C<-types>
Any of the Params::Validate type constants (C<SCALAR>, etc.) can be imported as
well. You can get all of them at once by importing C<-types>.
=head2 C<-all>
This import group will import C<-type>, C<describe_options>, and C<prog_name>.
=head1 CUSTOMIZING
Getopt::Long::Descriptive uses L<Sub::Exporter|Sub::Exporter> to build and
export the C<describe_options> routine. By writing a new class that extends
Getopt::Long::Descriptive, the behavior of the constructed C<describe_options>
routine can be changed.
The following methods can be overridden:
=head2 usage_class
my $class = Getopt::Long::Descriptive->usage_class;
This returns the class to be used for constructing a Usage object, and defaults
to Getopt::Long::Descriptive::Usage.
=head1 SEE ALSO
=over 4
=item *
L<Getopt::Long>
=item *
( run in 0.517 second using v1.01-cache-2.11-cpan-71847e10f99 )