rfc:enhanced_error_handling
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
rfc:enhanced_error_handling [2011/04/06 10:59] – external edit 127.0.0.1 | rfc:enhanced_error_handling [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 3: | Line 3: | ||
* Date: 2010-01-10 | * Date: 2010-01-10 | ||
* Author: | * Author: | ||
- | * Status: | + | * Status: |
* First Published at: http:// | * First Published at: http:// | ||
===== Introduction ===== | ===== Introduction ===== | ||
- | php_error(), | + | php_error(), |
I think that error behaviour has to be in the hands of the user (php coder). Different users have different preferences - and prefer different behaviour in different situations. | I think that error behaviour has to be in the hands of the user (php coder). Different users have different preferences - and prefer different behaviour in different situations. | ||
Line 93: | Line 93: | ||
A lower hierarchy level could enforce the use of a specific exception class, e.g. PersonalIntlExceptionClass() for all of intl.so. While forcing such a common class does ease catching, some information a more specific class could provide is lost. | A lower hierarchy level could enforce the use of a specific exception class, e.g. PersonalIntlExceptionClass() for all of intl.so. While forcing such a common class does ease catching, some information a more specific class could provide is lost. | ||
- | As of PHP 5.3, the concept of exception chaining has been introduced, whereas a " | + | As of PHP 5.3, the concept of exception chaining has been introduced, whereas a " |
==== Notices ==== | ==== Notices ==== |
rfc/enhanced_error_handling.1302087566.txt.gz · Last modified: 2017/09/22 13:28 (external edit)