I have very similar logic in a number of my test scripts. I use an eval block and check that the message in $@ matches
what I was expecting. That won't work directly for you since your code uses 'carp' where mine uses 'croak'.
If one of your methods is passed an invalid argument, is there any point carrying on? Rather than carp and return 0, why not just croak?
Coming back to your original question though, you could capture warning messages like this:
our $last_warning = '';
$SIG{__WARN__} = sub { $last_warning = shift; }
... code that generates warning ...
... code that checks contents of $last_warning ...
-
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.
|
