Re: [patch] re-invoking default error handler

I'd be up for option (B) as well: returning explicit 'false'. > If those are the choices, I say (B). The reason for the !NULL && !true was > to maintain as much of PHP's boolean juggling as reasonable. NULL in this > case being "unreasonable" because functions returning nothing are returning > NULL and will get caught up in the defeault error handler if we leave > everything else alone. As you said, it does bear an awful lot of > "specialness" so perhaps the explicit (bool)flase is the better way to go. -Andrei "Music expresses that which can not be said and on which it is impossible to be silent." -Victor Hugo