I'm usually don't even want to supress the error (this usually means the input data is wrong and I need to deal with it)
If it's undefs in a Perl data structure that you seek...
sub seek_undef {
my ($ref,$path) = (@_,"");
if (ref $ref eq 'HASH')
{ seek_undef($ref->{$_}, $path."{$_}") for keys %$ref }
elsif (ref $ref eq 'ARRAY')
{ seek_undef($ref->[$_], $path."[$_]") for 0..$#$ref }
else { defined $ref or warn "undef at $path\n" }
}
seek_undef( {
foo => { quz=>{ abc=>"def", ghi=>undef } },
bar => { baz=>[ "jkl", undef, { ooo=>undef } ],
blah=>undef }, uuu => undef,
} );
__END__
undef at {foo}{quz}{ghi}
undef at {bar}{baz}[1]
undef at {bar}{baz}[2]{ooo}
undef at {bar}{blah}
undef at {uuu}
-
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.
|