Re: Updated PHP 5 ToDo
| From: | (Marcus B�rger) | Date: | Sun, 20 Jul 2003 18:35:00 +0000 |
| Subject: | Re: Updated PHP 5 ToDo | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-3530@lists.php.net to get a copy of this message | ||
Hello Zeev,
Sunday, July 20, 2003, 8:09:31 PM, you wrote:
>>- Complete work on exceptions and find a solution on when to throw exceptions
>> and when to use errors.
>>
>> I still do not see any BC problems with making try/catch blocks to convert
>> E_WARING, E_NOTICE & E_ERROR to exceptions (assumed the problemntaic E_ERRORS
>> are changed to E_CORE or such). Why no BC? Simply becuase using try/catch
>> with old libs and relying on error capturing is an antilogy in itself.
>> Especially when thinking about the very limited capabilities in handling
>> errors the old way.
>>
>> Add an opcode to be able to see whether a try/catch is active. This could
>> possibly also allow to check which exceptions will get catched. Having this
>> we could finally convert uncaught exceptions to errors.
ZS> As I mentioned before, I don't really see a good solution here (for
ZS> anything other than E_ERROR, at least). Since I don't think there's a
ZS> solution in existence, it's low priority in my book (as in, I can live with
ZS> seeing this remaining the way it is now).
Probably we do autoconversion for E_ERROR then only for now. Collect some
expirience with it and later *maybe* add the other types?
--
Best regards,
Marcus mailto:helly@php.net