note merlyn I'm not into debugging. I can't recall <b>ever</b> invoking the Perl debugger except to try out snippets of code at a prompt (for which I type <code>perl -dead</code> usually), or in class while I'm trying to teach the debugger (which I do poorly, since I don't "debug" my code with a debugger). But never for debugging. (Larry is also like this, I'm told.) <p> So the question is, what do I use to debug? <p> Well, the first answer (and most important answer) is that I don't have to debug what doesn't contain bugs. Don't put bugs in. That's easier than it sounds, if you code in small chunks, slowly adding code one understandable step at a time. Never type anything into a program if you can't completely run it in your head. <p> The second part of the answer is that I started programming long before we had all these fancy GUIs and drag-n-drool debuggers. So when I had code go off the deep end, all I could do is keep adding <tt>print</tt> statements until it worked. As I got better, the number of <tt>print</tt>s got smaller, and then eventually I could just code the whole thing without adding any debugging. <p> With Perl, I throw in a random "die", sometimes with the result of <tt>Data::Dumper::Dumper</tt> in its mouth, but that's usually only once every five or ten times as I extend the program. <p> So what's all this about a Perl debugger? Why do people use it? Have they not learned the more effective ways of never letting your code get ahead of you, and trying to reduce the problem to something a <tt>die</tt> can show you? I'm truly puzzled. <p>-- <a href="http://www.stonehenge.com/merlyn/">Randal L. Schwartz, Perl hacker</a></p> 48474 48495