Me... I still use 'print' statements in my code for debugging purposes. I know it's old, and please don't tell me that i'm nuts for doing it, it's an old dog, new tricks issue.

I still use 'print' statements in my code for debugging purposes. I know it's old, and please don't tell me that i'm nuts for doing it . . .

You're not. Larry Wall once said he prefers prints over debuggers, too. I've heard similar things from other programmers over the years whose opinion I respect. Of course, there are a significant number of great programmers out there that use debuggers, too, so this isn't a clear-cut issue.

The only time I've actually used a debugger is in the very little VB I've done, and only then because getting something printed in a language that is heavily tied to a GUI is really annoying.

----
I wanted to explore how Perl's closures can be manipulated, and ended up creating an object system by accident.
-- Schemer

: () { :|:& };:

Note: All code is untested, unless otherwise stated