Re^2: Large File Parsing

Please don't read the previous posting as "using strict and warnings is nonsense", the opposite is true: Always use strict and warnings (except in rare situations like Perl golf). The use of Data::Dumper is nonsense here, and it really looks like cargo cult.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

Comment on Re^2: Large File Parsing Download Code

Replies are listed 'Best First'.
Re^3: Large File Parsing by Jenda (Abbot) on Jan 03, 2010 at 11:32 UTC
You always add in `use Data::Dumper;` whenever you want to debugprint a datastructure and remove it as soon as you remove all debug prints that need it? Really? I quite often leave it there knowing that sooner or later I'll need it again. Sometimes the holly war against cargo culting is a bit cargo cultish. Jenda Enoch was right! Enjoy the last years of Rome.	[reply] [d/l]
Re^4: Large File Parsing by RobertCraven (Sexton) on Jan 03, 2010 at 23:24 UTC
That is indeed the same reason I use it. I am open to other, better solutions. At least I learned now about cargo cult... I solved my problem by using Tie::File, but thank you for all your answers! Cheers, Thomas	[reply]
Re^4: Large File Parsing by educated_foo (Vicar) on Jan 03, 2010 at 18:21 UTC
You always remove your debug prints? `"2>/dev/null"` is the new `#define NDEBUG`! Seriously, it bugs me a bit when someone posts blatantly broken code prefaced by a bunch of monk-placating boilerplate. It shows that the OP has learned the wrong things from reading the site.	[reply] [d/l] [select]
Re^5: Large File Parsing by Jenda (Abbot) on Jan 03, 2010 at 21:15 UTC
That removes way too much. If they were things I though I might need again I'd use `print whatever_I_need if DEBUG;`. Redirecting STDERR will hide not just expected debug prints but also unexpected warnings. Jenda Enoch was right! Enjoy the last years of Rome.	[reply] [d/l]