Debugging Techniques
----------------------------
1) Give up...it doesn't work and it can't be fixed
2) Change line X where X is a random number between 1 and EOF
3) Change the last part that was edited...despite the fact that all previous parts were not tested when they were written.
4) Change the part that seemed most difficult to write...
5) Throw in 164978964790 echos to see every value everywhere in the program, but still not be able to locat ethe problem.
6) Throw in many echos but actually know what you're looking for and fix it.
7) Examine what went wrong...think about how the program works as a whole...deduce which area is not working...fix that part...usually through examination or a scaled-down version of (6).
8) Divine intervention (aka: the guy who has seen every error ever for language X so can tell you exactly what code mistake was made)
-- ----------------------------------------------- Ross Day
ITS Web Integration VP, Truman ACM/IEEE
660.785.5218 660.785.4414
[EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
----------------------------------------------------------------- To get off this list, send email to [EMAIL PROTECTED] with Subject: unsubscribe -----------------------------------------------------------------
