So, what to do about it?

The most bare-bones way to deal with it would be

eval {
  weather_subroutine();
} or do {
  warn $@;
};  # <-- Note trailing semicolon; it *does* matter
[download]

eval {
  weather_subroutine();
}
warn $@ if $@;
[download]

If you want something more robust and/or with more familiar spellings, take a look at TryCatch or Try::Tiny. (The Try::Tiny synopsis shows how to use it to turn an exception into a warning, so you could even lift that example straight out of the docs.)

Thanks - the bare bones method looks nice and seems to do exactly what I need.

OK. I just uncovered an "unintended" side effect when I tried to apply this technique in a converse fashion *another* script where instead of trying to prevent the script from exiting on "die", I only want to prepend an action to occur before exiting. Since this case in a sense the converse of the case in this thread, to avoid confusion, I am asking the full question in a new thread id=//811358.

Better:

sub whether_subroutine()
{
    my @results;
    if(  ! eval { @results= weather_subroutine(@_); 1 }  ) {
        warn $@;
        return;
    }
    return @results;
}
[download]

Perhaps someone more knowledgeable could clarify, but perlmod seems to indicate that you can set the %SIG hash as a package variable, so you could do something like this:

use Weather::Com;
$Weather::Com::SIG{__DIE__} = sub { warn(@_) };
[download]

I think that would cover every call to die() from within the Weather::Com package. Inspection of @_ within your new handler could let it die if something was really a big problem.

@_=qw;
Just another Perl hacker,;
;$_=q=print
"@_"= and eval;
[download]

That works nicely!

Though I still have to wrap each function call with an eval...

I still hope that a seasoned "monk" could verify that other than changing the behavior of die, the addition of the 'eval' command won't change the behavior of anything else. Or if it does, then help me understand what other side effects adding 'eval' could have

I think what you need is similar to this. Here I get a clear return value that says "It didn't work". Maybe you get something more indefinate like "I wanna die". If that is true, then use eval{} and plug the success or fail value into the "redo" code.

my $max_retry =3;
RETRY: while (my $n_attempt=0, $parameter=<>)
{
   my $req = POST 'http:/...blah..../',
                   [ 
                     action   => '/db/',
                     param    => "$parameter",
                     type     => 'submit', 
                     value    => 'Search',
                   ];

   my $res = $ua->request($req);
   
   # idea is to concentrate the "it didn't work" code to
   # right here
   unless ($res->is_success) ##1 of 5,000 case##
   {
      $n_attempt++;
      print STDERR "attempt # $n_attempt for $parameter\n";
      print STDERR "$parameter ERROR: Try# $n_attempt of $max_retry: "
+.
                   $res->status_line . "\n";
      sleep(1);
      redo RETRY if $n_attempt <= $max_retry;
      print STDERR "$parameter ERROR: Try# $n_attempt of ".
                    "$max_retry FAILED: ".
                    $res->status_line . "\n";                 
      next; #we "Give up" at this point! And read next 
            #parameter from <>
   }
   
### this is the "good machine case..."
   print $res->as_string if DEBUG_RAW;
   ......or whatever....
}
[download]