Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re: RFC: Basic debugging checklist

by Your Mother (Chancellor)
on Feb 18, 2009 at 20:54 UTC ( #744881=note: print w/ replies, xml ) Need Help??


in reply to RFC: Basic debugging checklist

Regarding #4, it also seems there is a pretty wide consensus (someone will clobber me if I'm wrong) that Data::Dumper is at this point in time "considered harmful" and one should reach for Data::Dump (or even YAML or JSON) instead.


Comment on Re: RFC: Basic debugging checklist
Re^2: RFC: Basic debugging checklist
by JavaFan (Canon) on Feb 19, 2009 at 00:01 UTC
    Consider yourself clobbered. Now, I'm the first to admit that the output of Data::Dumper is harder to read that YAML, but considering that most of the time I see programmers reach for Data::Dumper instead of any of the alternatives, I'm not inclined to agree on the "pretty wide consensus".

      You hit me in the ear!

      Sorry, bad choice of words. I meant "growing consensus" and I meant it among those who don't cargo cult. I've never even used Data::Dump but I've seen Data::Dumper mentioned quite pejoratively in comparisons lately. Data::Dumper's defaults are terrible (::Terse and ::Indent are usually necessary/desired) and using eval to bring the code back to life is, using this chestnut again so soon, "considered harmful."

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://744881]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (7)
As of 2015-07-07 08:19 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...









    Results (87 votes), past polls