get the best and fastest answer
|
|
|
|
Clear questions and runnable code get the best and fastest answer |
|
| PerlMonks |
Re^3: Using the Perl Debugger (-d)by osunderdog (Deacon) |
| on Jan 25, 2007 at 11:05 UTC ( [id://596528]=note: print w/replies, xml ) | Need Help?? |
This is an archived low-energy page for bots and other anonmyous visitors. Please sign up if you are a human and want to interact.
Ok, let me see if I can explain myself without digging a hole. Sure! debugging and logging are the Yin and Yang of software diagnosis. I guess I was distinguishing the two using interactivity as criteria. In terms of interactivity, I would consider debugging and logging as separate. Debugging allows a developer to interrogate and modify variables during runtime. Logging, on the other hand, is the passive collection of what has happened during runtime. I once had a Tool Vendor argue with me that logging was inappropriate for software development. His argument was that it was never introduced as a topic of discussion in college. Hazah! I'm Employed!
In Section
Seekers of Perl Wisdom
|
|
||||||||||||||||||||||||