Yep. I was thinking that there might be a set of functions that many/most debug trainer scripts might want. Hopefully it would then be possible to do include it, set up a data structure or two and a few print statements or something. I was thinking it would be nice if you'd run a script, and it would start out telling you what it was going to show you, do a little setup and then present the debug prompt. (Perhaps using the @DB::typeahead buffer to get the program running before the user had to guess what to do.)
Of course, I may be over-thinking it, too. It might just be as simple as a few print statements containing instructions and a CPAN bundle and/or namespace to put 'em.
I don't use the debugger much, and when I do, it's just for a few simple things. I don't know everything it's capable of. I used to use Microsoft's CodeView, and learned a lot about it. It was surprisingly capable. It will be interesting to see what techniques might get published.
When your only tool is a hammer, all problems look like your thumb.
|Comment on Re^3: RFC: debugger_trainer|