I though to myself, "hmmmm ... let's use TheDamian's Getopt::Declare" and proceded to RTFM. I had always wanted to learn this module, and now seemed like the time.

After about 40 minutes of racking my brain (:D) i finally came up with this:

#!/usr/bin/perl -w

use strict;
use LWP::UserAgent;
use Getopt::Declare;

# -h, -v, --help, --version are included
# and these are tabs - not spaces!
my $spec = q(
    -a    List all matches
    --all    [ditto]
);
my $args = Getopt::Declare->new($spec);
my $all  = $args->{'--all'} || $args->{'-a'};

for my $woord ($args->unused) {
   # insert for loop block innards from code above
}
[download]

P.S. i also have no quandaries about using regexes to parse HTML, just as long as the coder understands how to use the CPAN HTML parsers. Sometimes using regexes really is easier. Sometimes.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In the interest of tmtowtdi, here's an alternate Getopt::Declare scenario that sets up the $all and @words variables in action blocks. Here I decided to make the search words required (but without option description), and just allow for -a as an abbrev. of -all (instead of using the --all version):

  #!/usr/bin/perl -w
  use strict;
  use LWP::UserAgent;
  use Getopt::Declare;
  use vars qw/$all @words/;

  my $opts = Getopt::Declare->new(<<'EOS');

      -a[ll]           List all matches
                        {$all = 1}
      <terms:s>...     [required]
                        {@words = @terms}
  EOS

  for my $word (@words) {
      # insert fetch code ...
      # ...
      last unless $all;
  }
  __END__
[download]

When I use this code, there is no output...

This post is ten years old, the code was last updated nine years ago. It's likely the site in question has changed substantially in that time.

You are right, that was a stupid remark..