Codesmith
08-03-2003, 04:17 PM
Most of my experience is with fully compiled languages (C/C++) and I have found that with these languages, a walkthrough of each possible execution path with a good debugger to be an excellent tool for preventing errors.
When I was learning lingo programing (Macromedia Director's scripting language) I also found the debugger to be quite usefull. Especially since some feautures of the language contained undocumented bugs and quirks. Of course lingo debugger has an advantage since it is an entirely self contained environment.
I am not sure how a debugger is going to work with other interpreted languages, especially those involving multiple independent systems (browser, webserver, php, mysql).
I am now learning PHP and am wondering whether I should bother learn to use the build it debugger or any 3rd party debugger might be of service.
Am I better off just creating my own testing statements then latter commeting them out?
Any input would be appreciated. Currently I know nothing about php debuggers or whether I should use a tool them has one.
When I was learning lingo programing (Macromedia Director's scripting language) I also found the debugger to be quite usefull. Especially since some feautures of the language contained undocumented bugs and quirks. Of course lingo debugger has an advantage since it is an entirely self contained environment.
I am not sure how a debugger is going to work with other interpreted languages, especially those involving multiple independent systems (browser, webserver, php, mysql).
I am now learning PHP and am wondering whether I should bother learn to use the build it debugger or any 3rd party debugger might be of service.
Am I better off just creating my own testing statements then latter commeting them out?
Any input would be appreciated. Currently I know nothing about php debuggers or whether I should use a tool them has one.