each() is vulnerable. Like it or not, your re-written version is the standard idiom for looping through a hash's key-value pairs when *anything* outside your control could interfere with an each() call.

foreach my $key ( keys %hash ) {
  my $val = $hash{$key};
  ...
}
[download]

For related info, see the thread Spot the bug, especially the replies by merlyn and ysth.

To improve readability with your long package names, you might do some combination of these refactorings:

• Move the scope of $val back inside the loop.
• Align the long parts of the first two lines:

  foreach my $key ( keys %some::very::long::named::module::foo ) {
    my $val =            $some::very::long::named::module::foo{$key};
  [download]

• Change the if block to next, or pre-filter the keys through grep().
• Use scoped aliases via globs:

  {
    local *foo  = *some::very::long::named::module::foo;
    local *draw = *some::very::long::named::module::drawSomethingPretty;
    foreach my $key ( grep { testconditions($_) } keys %foo ) {
      drawSomethingPretty( $foo{$key} );
    }
  }
  [download]

• Import the identifiers. If such importing is not supported by the module, then submit a request or a patch to the module author.

  use some::very::long::named::module qw( foo drawSomethingPretty );
  foreach my $key ( keys %foo ) {
    next if not testconditions($key);
    drawSomethingPretty( $foo{$key} );
  }
  [download]

  This is the most "correct" way to handle the issue; it is exactly this issue that Exporter is designed to resolve. Work with the author to nail down this part of the module's API. If direct access to %foo is truely part of the API, then it should definitely be available for import. Otherwise, some accessor method should be provided, or the module docs should make clear a proper path to meet the same needs.