Re: Bogus bug??
| From: | Robert Cummings | Date: | Sun, 11 Dec 2005 22:55:05 +0000 |
| Subject: | Re: Bogus bug?? | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-21176@lists.php.net to get a copy of this message | ||
On Sun, 2005-12-11 at 17:26, Robert Cummings wrote:
> Could someone explain to my feeble mind how the bug reported at the
> following link is bogus? The added comment is pretty obtuse :(
>
> http://bugs.php.net/bug.php?id=35634&edit=2
I'd just like to add before a second person send me an RTFM type email,
that I HAVE read the documentation for set_error_handler() and I am
aware that it says that most E_STRICT errors can't be handled if they
occur in the same file as the set_error_handler() call. The E_STRICT I'm
attempting to catch however, is in another script. Maybe it's the same
thing because I include the code, or I guess more than likely because it
happens at parse time, but either way, I'm not nesting classes the
parser just thinks I am which I thus categorize as a parser bug. Also it
seems somewhat ironic that an attempt to catch an E_STRICT causes an
E_FATAL *lol*.
Thanks,
Rob.
--
.------------------------------------------------------------.
| InterJinn Application Framework - http://www.interjinn.com
|
:------------------------------------------------------------:
| An application and templating framework for PHP. Boasting |
| a powerful, scalable system for accessing system services |
| such as forms, properties, sessions, and caches. InterJinn |
| also provides an extremely flexible architecture for |
| creating re-usable components quickly and easily. |
`------------------------------------------------------------'