Re: Exception::fillException() proposal
| From: | Antony Dovgal | Date: | Tue, 10 Jan 2006 22:14:18 +0000 |
| Subject: | Re: Exception::fillException() proposal | ||
| References: | 1 2 3 4 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-21468@lists.php.net to get a copy of this message | ||
On 11.01.2006 01:00, Marcus Boerger wrote:
Hello Antony, Tuesday, January 10, 2006, 10:56:21 PM, you wrote:Except for __destruct() I don't see any other ways for it to be executed during shutdown. And we know that exceptions work fine in __destruct().On 11.01.2006 00:41, Marcus Boerger wrote:Hello Antony, in general modifying exception data is vey dangerous because first it leads to confusion on the usage part and second it might lead to sever problems in the engine facilities that deal with them. That this in a few cases worked does not mean it works in all cases it mybe be used.Actually, the code doesn't modify any data there, but copies it instead. That is: create new object, copy data from the old one, update few properties.And you are sure there is no way this can be executed during shutdown sequence?
Huh? -- Wbr, Antony DovgalTo prevent us from adding all the stuff Java invented to deal more gracefull with exceptions starting with the ability to handle more than one exception at a time i would like to stay with the KISS approach and have them as easy as possible.I realize that it's relatively easy to implement this in PHP, but in the same time I don't see in what way adding this function violates the KISS approach. Could you plz elaborate?You are turining Exceptions into Normalities.