in reply to
What is the best way to dump data structures to logfiles?
Currently, the code uses Data::Dumper as dumping tool, for logging purposes. I see this as a bad thing and would like to remove this from the code: Data::Dumper is supposed to be used for debugging purposes, not for day-by-day operations, I think.
Why do you see this as a 'bad thing'?
I have one service on a Production server logging at the DEBUG level (using Log::Log4perl). This creates huge log files, but it also gives me the ability to immediately diagnose problems on a busy server. It's not pretty, but it means I can do support quickly and efficiently; disk space is cheap, so why not?
I have in the past used the debugger to step through my code (15 years ago I did the same thing with C code that I wrote); this lets me confirm that the code is doing *exactly* what I think it does. If there's a mis-match between intent and reality, at the very least I need to be aware of that fact. Better than being aware is to just fix the code.
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds