Further to exception handling being well supported on CPAN for many years (as pointed out by hippo above),
note that an officially endorsed Try-Catch Exception Handling notation
was released with core perl 5.34 as an experimental feature.
See also:
On CPAN:
Update
As mentioned at New built-in perl5.38 try/catch syntax:
- perl v5.34 added try/catch syntax based on CPAN module Syntax::Keyword::Try
- perl v5.36 added "finally" blocks to try/catch, also inspired by Syntax::Keyword::Try
- perl v5.36 added use feature 'defer', allowing you to create defer blocks that run at the time that execution leaves the block it's declared inside (which seems to be inspired by the classic RAII programming idiom)
- use v5.36 implies use strict and use warnings
- use v5.38 implies use feature 'try'
As noted at On Interfaces and APIs:
- Perl 5's "string eval" and "block eval" is an example of violation of the "principle of distinction", aka "different things should look different"
Updated: added more references
-
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.
|