#22901 [Com]: Error message for uncaught exception not very informative
| From: | thekid at thekid dot de | Date: | Sat, 19 Apr 2003 17:05:47 +0000 |
| Subject: | #22901 [Com]: Error message for uncaught exception not very informative | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-37907@lists.php.net to get a copy of this message | ||
ID: 22901
Comment by: thekid at thekid dot de
Reported By: mfischer@php.net
Status: Open
Bug Type: Zend Engine 2 problem
Operating System: Linux
PHP Version: 5CVS-2003-03-26 (dev)
New Comment:
thekid@friebes:~ > cat | php5
<?php
class dummy_exception {
}
throw new dummy_exception;
?>
^D
Fatal error: Uncaught exception 'dummy_exception'! in Unknown on line
0
At least we've gotten a bit farther:)
Previous Comments:
------------------------------------------------------------------------
[2003-03-26 19:14:48] mfischer@php.net
Another small note:
No idea why it hast to be called "Uncaught exception!" with a trailing
bang but reading it in a message like
Fatal error: Uncaught exception! in Unknown on line 0
doesn't fit well.
Any plans to remove this?
------------------------------------------------------------------------
[2003-03-26 08:29:51] mfischer@php.net
The error message for uncaught exceptions is not very informative.
-------------8<----------------
Example:
$ cat exception.php
<?php
class dummy_exception {
}
throw new dummy_exception;
?>
$ php exception.php
Fatal error: Uncaught exception! in Unknown on line 0
Unknown(0) : Fatal error - Uncaught exception!
-------------8<----------------
It doesn't matter whether the throw statement is in a function/class or
not.
A few things which should be considered worth improving this message:
- in which file is it thrown ("Unknown" ?)
- on which line is it thrown ("0" ?)
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=22901&edit=1