G'day kp2a,

You may find one or more of these to be useful (some you may already know about):

• The 'refs' stricture of the strict pragma. (The other strictures generate compile-time errors.)
• Promote warnings to fatal errors.
• Use eval to trap errors.
• Use Carp routines to produce more verbose warning and error messages, including stack traces.
• Use caller to get varying amounts of information from just the caller's package to a complete stack trace.
• Write $SIG{__WARN__} and $SIG{__DIE__} handlers (see %SIG in perlvar).
• Take a look at the information provided by the $!, $?, $@ and $^E Error Variables.
• Use autodie to trap errors from specific functions.
• CPAN modules such as TryCatch and Try::Tiny. Take a look at their SEE ALSO sections for similar modules.
• A CPAN search for 'exception' may prove fruitful.

---

---

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.