open doesn't normally die on errors, so actually, your exception handling kind of is working ;-)

Looks to me like you might be using a combination of diagnostics and autodie:

#!/usr/bin/env perl
use warnings;
use strict;
use diagnostics -traceonly;
use autodie;
open FOO, '<', '/tmp/foo/' or die "ACK! $!";
__END__
Uncaught exception from user code:
  Can't open '/tmp/foo/' for reading: 'No such file or directory' at -
+ line 6
  main::__ANON__("FOO", "<", "/tmp/foo/") called at - line 6
[download]

If you don't want open to die and you want to handle the error yourself, you can lexically disable autodie, as shown in its synopsis:

{
  no autodie qw(open);          # open failures won't die
  open(my $fh, "<", $filename); # Could fail silently!
  # ^^^ add your "or die" to this open
}
[download]

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.