If you are a pioneer for Perl6 or P5EE, then i can see the benefits of encapsulating error conditions into those glorified goto's known as exceptions. But otherwise, this just isn't needed in most day to day Perl scripts.

I have no reservations about using another language that actually has those keywords, like Python, Ruby (my new favorite leisure language) or even, ick, Java. And if Perl6 includes 'real' exceptions, then I will use them, but I try to stay true to the spirit of the language, and try-catch in Perl5 is about as useful to me as a switch block. But don't let me stop your quest, it is a noble one.

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
F--F--F--F--F--F--F--F--
(the triplet paradiddle)

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.