my english is not perfect, right ... but let me unsderline something.

The subject:

 [Formaldehyde] The Most Basic Ajax ------> - <--------  *PHP* *Error* 

It's a PHP Error Debugger specially suited for Ajax interactions.

The set_error_handler is not enough, write it even upside down and most crucial 
error like these will not be managed:

Finally, this is the first code example in Formaldehyde page:

<?php // generates a Fatal Error

echo 'Hello', *iDoNotExist*(), ' ', 'World';

And the first result image:

Which clearly *is* about an unmanaged Fatal Error

Ajax responses are usually different, even if the called page is the same, and 
the reason could be an X-Request-With: XMLHttpHeader header, usually set by 
default with every library and for each Ajax interation.

I like to reply about a subject, after I understand what is the subject is 
about ... but you are right, my English is not perfect, but PHP developers 
should be more careful about what PHP debug is, what is possible to do with 
set_error_handler, and how Formaldehyde manage *any* *kind* of *php* *error*, 
something I cannot find in any other library or framework.


> Date: Sat, 12 Sep 2009 00:20:58 -0400
> From:
> To:
> Subject: Re: [PHP] RE: [Formaldehyde] The Most Basic Ajax - PHP Error Debugger
> On Sat, Sep 12, 2009 at 12:23:44AM +0200, Andrea Giammarchi wrote:
> > 
> > Exactly Ben, except when PHP fails, even with a Fatal Error, the page has 
> > status 200, we need to understand which call failed between hundreds of 
> > potential calls in the debugger, and errors could pass silently.
> > 
> > With Formaldehyde, accordingly with your predefined error_reporting level, 
> > above situation will never happen, and the entire process, without changing 
> > anything, will be much simpler, as Ben already described.
> > 
> > So yes Tedd, you did not even read what is Formaldehyde about ... please 
> > try to understand it before other comments, maybe you'll discover it's 
> > extremely simple, and hopefully useful.
> > 
> I suspect your English is getting in the way. You're calling this an
> AJAX debugger. Debugging in PHP is relatively straightforward, if you
> set the error level properly and build your own error handler, etc. So
> people on this list would probably think of a PHP debugger as an
> unimportant piece of software. Debugging in Javascript is more complex
> and difficult, and the responses you're getting on the list sound like
> people think Formaldehyde is for debugging Javascript (which PHP
> programmers often aren't very interested in). On the Google code page
> for Formaldehyde, you only emphasize PHP debugging, as that's the only
> type of error example you give.
> If the point of Formaldehyde is to debug PHP code, then you should call
> it a "PHP code debugger", not an "AJAX code debugger". Tedd's right--
> basic AJAX transactions are incredibly simple, and once the code is
> written (it can be copied from any number of books), it needs no further
> work. General Javascript is a different matter-- it can be quite complex
> and quite hard to debug. But AJAX is a very narrow application of
> Javascript.
> If Formaldehyde is really a debugger for AJAX code, then you should
> change the examples and text of your Google code page.
> If Formaldehyde is really a debugger for Javascript code, then you
> should change the examples on your Google code page to show Javascript
> errors, and call it a "Javascript debugger".
> If Formaldehyde is really a debugger for PHP code, then call it a "PHP
> code debugger". The examples on your Google code page fit this.
> Paul
> -- 
> Paul M. Foster
> -- 
> PHP General Mailing List (
> To unsubscribe, visit:

Drag n’ drop—Get easy photo sharing with Windows Live™ Photos.

Reply via email to