$ perldoc Data::Dumper |grep eval
printing and "eval"
eval Data::Dumper->Dump([$foo, $bar], [qw(foo *ary)]);
eval $d->Dump;
The return value can be "eval"ed to get back an identical copy of
+the
The default output of self-referential structures can be "eval"ed,
+ but
fill in these references. Moreover, if "eval"ed when strictures ar
+e in
Controls the degree to which the output can be "eval"ed to rec
+reate
output may not always be parseable by "eval".
$bar = eval(Dumper($boo));
$Data::Dumper::Purity = 1; # fill in the holes for eva
+l
$d = eval $c;
if "Purity" is set. You can "eval" the result, but bear in mind th
+at the
$Data::Dumper::Purity = 1; makes it write
$VAR1 = {
'test1' => [
{
'temp' => '123'
}
],
'test2' => [
{}
]
};
$VAR1->{'test2'}[0] = $VAR1->{'test1'}[0];
You could use YAML
-
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.
|