comment on

Sure, sometimes Data::Dumper or similar is enough...

It's for things like this that a just-a-dumper dumper is valuable. The last thing you want is for the dumper to arrive at arbitrary decisions about whether the substructure under key A is a duplicate of that under key D on one pass and vice versa on another, because that's the keys came out of the hash in different orders.

You'd probably have to apply a sort option to get comparible output from a hash anyway, but for this kind of thing you want to see what's there in detail, not an abbreviated reminder that this bit at the bottom is the same as that bit way back up near the top. Especially in heavily self-referencial structures.

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^2: When Test Suites Attack (text; diff) by BrowserUk
in thread When Test Suites Attack by Ovid

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.


Your skill will accomplish what the force of many cannot
	PerlMonks