Thats some good thinking there :)

I hope that people will think more on the "or die" and when they are implementing it. It serves a purpose, but it's not always the best way to handle an exception.

:) it is the best way, because otherwise it isn't an exception, die is for exceptions :D

sub MyApiCall { open ... or die ... }
sub UserInterface {
   Beginning() or die "nothing to do ";
   while( NextPiece() ){
       eval { MyApiCall (...) ; 1 }
          or warn "Whooops, trying next one";
   }
}
[download]

Thats the difference, use die for everything important, for all show stoppers, but trap the exception when its merely a hiccup ... always sugar coat stuff for the end user