RSS | Module Info | Add a review of Getopt-Long-Descriptive
Getopt-Long-Descriptive (0.093)
Getopt::Long::Descriptive claims to be similar to Getopt::Long but with the addition of an automatically-generated usage message. However, for example, whereas with Getopt::Long, I can do something like
GetOptions ("verbose" => \my $verbose)
and have my program use -v as an option:
./script -v
with Getopt::Long::Descriptive, the short options don't occur unless I specify them. This may be a good thing or a bad thing, but either way it isn't the same thing as Getopt::Long, or even an extension of the same thing. Also, it is quite handy in short scripts to be able to send a reference like the \my $verbose above, which Getopt::Long::Descriptive doesn't support.
It would be great to have an automatic way to generate usage messages which was also compatible with Getopt::Long, but this isn't it. After evaluating this module I decided to stick with using Getopt::Long and here-documents for usage messages.
Ben Bullock - 2012-12-11T18:11:33 (permalink)
Was this review helpful to you?
Yes
No
Getopt-Long-Descriptive
(0.085)
Once you got the idea and usage of this module, its very simple to use and a real time-saver.
The documentation has been improved recently. As far as I have seen, it is now clear, how to start using this module.
Thanks a lot!
Ingo Lantschner - 2010-03-15T03:05:11 (permalink)
2 out of 2 found this review helpful.
Was this review helpful to you?
Yes
No
Getopt-Long-Descriptive
(0.02)
After using Getopt::Long::Descriptive, Getopt::Long is like using a very complicated set of s/// expressions to replace printf. GLD is the new hotness.
Ricardo Signes - 2005-11-10T13:48:23 (permalink)
4 out of 4 found this review helpful.
Was this review helpful to you?
Yes
No
