If you really wanted to do away with "bloat", you could condense chromatic's example further ...

  sub wanted { 
      print "$File::Find::dir/$hold\n" 
          if /\.(\w+)$/ and exists $exts{ lc $1 };
  }
[download]

... which reads a little more natural (at least to me :-)).

You might also consider adding a small snippet of code so directories with multiple matches are only printed once instead of once per match.

  my %already_seen;

  sub wanted { 
      print "$File::Find::dir/$hold\n" 
          if /\.(\w+)$/ and exists $exts{ lc $1 } 
          and not $already_seen{ $File::Find::dir }++;
  }
[download]

    --k.

@exts{@exts} = ();
[download]

It's a hash slice.

It fills the hash %exts with the contents of your @exts array. The keys are set to the values in @exts, and the values in the hash are set to undef. That's why you need to test for exists rather than "truth"; because the values aren't "true", but the keys do exist.

Ah, I see. So if I have this:

@exts = {'jpg','jpeg','gif');

%exts;
@exts{@exts} = ();
[download]

then we get an %exts array that is the same as this:

%exts = ('jpg'=>'','jpeg'=>'','gif'=>'');
[download]

Right? Why do you so @exts{@exts} and not %exts{@exts}?