w.r.t the warning redirect, I've been preferring a local clobber of the __WARN__ handler recently. It's less intimidating to the unwashed, and expires naturally.
use strict;
use warnings;
my $log = parse_regex( q#(\\.|["']|x)# );
print $log;
sub parse_regex {
my ($regex) = @_;
# Catch and stash warnings
my $parselog = '';
local $SIG{__WARN__} = sub {
$parselog .= $_ for @_;
};
# --- compile regex
eval q{
use re 'debug';
qr/$regex/;
};
return $parselog;
}
Best of luck; strikes me as an interesting challenge. Is use re 'debug'; output stable enough for automated parsing?
Update: Huh, the debug actually bypasses the warning handler and prints directly to STDERR. Now starting penance.
#11929 First ask yourself `How would I do this without a computer?' Then have the computer do it the same way.
-
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.
|