Are you just trying to make sure that errors in the
plugin don't cause your code to die? Which eval is great
for. Or are you trying to restrict the plugin to only be
able to perform a (very) limited amount of actions? Which
Safe.pm should be great for.
If all you're trying to do is keep the plugin's errors from
aborting your code, but still want it to be able to do anything
that the rest of the codebase does, then eval is probably the
best choice. Just log $@ after the eval so the plugin authors
have a way of tracking down their errors.
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>
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
Want more info? How to link or
or How to display code and escape characters
are good places to start.