On 9/5/06, John Buckman <[EMAIL PROTECTED]> wrote:
As to "why a debugger for aolserver"? Any large web-based application shares many of the same complexity problems of traditional applications, and from my C++ days, I learned that I should never leave code in that I hadn't stepped through at least once. Lots of the bugs on BookMooch (22,000 lines of Tcl procs at launch) have been logic errors, and in the beta and first month of launching BookMooch, my bug database reports 414 separate bugs fixed. That's a lot of code, and a proper debugger is nice. One nice thing tclhttpd has is a debug mode that gives you a stack track, and a few other introspection features when a Tcl error occurs. Might be worth borrowing the concept.
I rely on automated tests to catch this kind of stuff (Now totally off topic!) Feel free to start another discussion if you are interested in how we use automated testing in OpenACS. Dave -- Dave Bauer [EMAIL PROTECTED] http://www.thedesignexperience.org/ -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
