Re: Built-in Debugging
| From: | Robert Cummings | Date: | Fri, 16 Oct 2009 13:20:13 +0000 |
| Subject: | Re: Built-in Debugging | ||
| References: | 1 2 3 4 5 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-298914@lists.php.net to get a copy of this message | ||
Al wrote:
Ashley Sheridan wrote:I find having a custom error handler that uses debug_backtrace() to produce a limited stack trace very useful for finding errors sometimes. Cheers, Rob. -- http://www.interjinn.com Application and Templating Framework for PHPOn Fri, 2009-10-16 at 09:04 -0400, Al wrote:I agree with you and that's why I said in my first message "Personally, I've found that turning on "error_reporting(E_ALL)", debug_backtrace() and debug_print_backtrace() quite adequate for most situations." In fact, I don't recall even using debug_backtrace() and debug_print_backtrace() in the last couple of years. I script very robust code and it catches damn near all errors itself.Bob McConnell wrote:Real coders don't use debugging tools, comments and output statements are all you need ;) Thanks, Ash http://www.ashleysheridan.co.ukFrom: Raymond IrvingphpEdit, a super IDE, has an extensive suite of integrated debug tools.Will be ever see built-in debugging features for PHP?I do not expect there would be. Debuggers are more likely to be provided by the IDE. For example, in MS-Windows, Visual Studio is the IDE and can include any of several compilers. It also includes the debugger, and uses the same front end for all languages. Of course, Microsoft has it much easier since they only support one hardware platform (x86) and one OS. Unlike the rest of the world where tools are more likely to be portable. For an IDE with debug capabilities, try NetBeans. I am sure there are others, but that is the only one I have actually looked at. Bob McConnell