Exceptions
PHP has an exception model similar to that of other programming languages. An exception can be throw n, and caught (» catch ed») within PHP. Code may be surrounded in a try block, to facilitate the catching of potential exceptions. Each try must have at least one corresponding catch or finally block.
If an exception is thrown and its current function scope has no catch block, the exception will «bubble up» the call stack to the calling function until it finds a matching catch block. All finally blocks it encounters along the way will be executed. If the call stack is unwound all the way to the global scope without encountering a matching catch block, the program will terminate with a fatal error unless a global exception handler has been set.
The thrown object must be an instanceof Throwable . Trying to throw an object that is not will result in a PHP Fatal Error.
As of PHP 8.0.0, the throw keyword is an expression and may be used in any expression context. In prior versions it was a statement and was required to be on its own line.
catch
A catch block defines how to respond to a thrown exception. A catch block defines one or more types of exception or error it can handle, and optionally a variable to which to assign the exception. (The variable was required prior to PHP 8.0.0.) The first catch block a thrown exception or error encounters that matches the type of the thrown object will handle the object.
Multiple catch blocks can be used to catch different classes of exceptions. Normal execution (when no exception is thrown within the try block) will continue after that last catch block defined in sequence. Exceptions can be throw n (or re-thrown) within a catch block. If not, execution will continue after the catch block that was triggered.
When an exception is thrown, code following the statement will not be executed, and PHP will attempt to find the first matching catch block. If an exception is not caught, a PHP Fatal Error will be issued with an » Uncaught Exception . » message, unless a handler has been defined with set_exception_handler() .
As of PHP 7.1.0, a catch block may specify multiple exceptions using the pipe ( | ) character. This is useful for when different exceptions from different class hierarchies are handled the same.
As of PHP 8.0.0, the variable name for a caught exception is optional. If not specified, the catch block will still execute but will not have access to the thrown object.
finally
A finally block may also be specified after or instead of catch blocks. Code within the finally block will always be executed after the try and catch blocks, regardless of whether an exception has been thrown, and before normal execution resumes.
One notable interaction is between the finally block and a return statement. If a return statement is encountered inside either the try or the catch blocks, the finally block will still be executed. Moreover, the return statement is evaluated when encountered, but the result will be returned after the finally block is executed. Additionally, if the finally block also contains a return statement, the value from the finally block is returned.
Global exception handler
If an exception is allowed to bubble up to the global scope, it may be caught by a global exception handler if set. The set_exception_handler() function can set a function that will be called in place of a catch block if no other block is invoked. The effect is essentially the same as if the entire program were wrapped in a try — catch block with that function as the catch .
Notes
Note:
Internal PHP functions mainly use Error reporting, only modern Object-oriented extensions use exceptions. However, errors can be easily translated to exceptions with ErrorException. This technique only works with non-fatal errors, however.
Example #1 Converting error reporting to exceptions
function exceptions_error_handler ( $severity , $message , $filename , $lineno ) throw new ErrorException ( $message , 0 , $severity , $filename , $lineno );
>
Examples
Example #2 Throwing an Exception
function inverse ( $x ) if (! $x ) throw new Exception ( ‘Division by zero.’ );
>
return 1 / $x ;
>
try echo inverse ( 5 ) . «\n» ;
echo inverse ( 0 ) . «\n» ;
> catch ( Exception $e ) echo ‘Caught exception: ‘ , $e -> getMessage (), «\n» ;
>
// Continue execution
echo «Hello World\n» ;
?>
The above example will output:
0.2 Caught exception: Division by zero. Hello World
Example #3 Exception handling with a finally block
function inverse ( $x ) if (! $x ) throw new Exception ( ‘Division by zero.’ );
>
return 1 / $x ;
>
try echo inverse ( 5 ) . «\n» ;
> catch ( Exception $e ) echo ‘Caught exception: ‘ , $e -> getMessage (), «\n» ;
> finally echo «First finally.\n» ;
>
try echo inverse ( 0 ) . «\n» ;
> catch ( Exception $e ) echo ‘Caught exception: ‘ , $e -> getMessage (), «\n» ;
> finally echo «Second finally.\n» ;
>
// Continue execution
echo «Hello World\n» ;
?>
The above example will output:
0.2 First finally. Caught exception: Division by zero. Second finally. Hello World
Example #4 Interaction between the finally block and return
function test () try throw new Exception ( ‘foo’ );
> catch ( Exception $e ) return ‘catch’ ;
> finally return ‘finally’ ;
>
>
The above example will output:
Example #5 Nested Exception
class MyException extends Exception
class Test public function testing () try try throw new MyException ( ‘foo!’ );
> catch ( MyException $e ) // rethrow it
throw $e ;
>
> catch ( Exception $e ) var_dump ( $e -> getMessage ());
>
>
>
$foo = new Test ;
$foo -> testing ();
The above example will output:
Example #6 Multi catch exception handling
class MyException extends Exception
class MyOtherException extends Exception
class Test public function testing () try throw new MyException ();
> catch ( MyException | MyOtherException $e ) var_dump ( get_class ( $e ));
>
>
>
$foo = new Test ;
$foo -> testing ();
The above example will output:
Example #7 Omitting the caught variable
Only permitted in PHP 8.0.0 and later.
class SpecificException extends Exception <>
function test () throw new SpecificException ( ‘Oopsie’ );
>
try test ();
> catch ( SpecificException ) print «A SpecificException was thrown, but we don’t care about the details.» ;
>
?>
Example #8 Throw as an expression
Only permitted in PHP 8.0.0 and later.
function test () do_something_risky () or throw new Exception ( ‘It did not work’ );
>
try test ();
> catch ( Exception $e ) print $e -> getMessage ();
>
?>
User Contributed Notes 14 notes
If you intend on creating a lot of custom exceptions, you may find this code useful. I’ve created an interface and an abstract exception class that ensures that all parts of the built-in Exception class are preserved in child classes. It also properly pushes all information back to the parent constructor ensuring that nothing is lost. This allows you to quickly create new exceptions on the fly. It also overrides the default __toString method with a more thorough one.
interface IException
/* Protected methods inherited from Exception class */
public function getMessage (); // Exception message
public function getCode (); // User-defined Exception code
public function getFile (); // Source filename
public function getLine (); // Source line
public function getTrace (); // An array of the backtrace()
public function getTraceAsString (); // Formated string of trace
/* Overrideable methods inherited from Exception class */
public function __toString (); // formated string for display
public function __construct ( $message = null , $code = 0 );
>
abstract class CustomException extends Exception implements IException
protected $message = ‘Unknown exception’ ; // Exception message
private $string ; // Unknown
protected $code = 0 ; // User-defined exception code
protected $file ; // Source filename of exception
protected $line ; // Source line of exception
private $trace ; // Unknown
public function __construct ( $message = null , $code = 0 )
if (! $message ) throw new $this ( ‘Unknown ‘ . get_class ( $this ));
>
parent :: __construct ( $message , $code );
>
public function __toString ()
return get_class ( $this ) . » ‘ < $this ->message > ‘ in < $this ->file > ( < $this ->line > )\n»
. » < $this ->getTraceAsString ()> » ;
>
>
?>
Now you can create new exceptions in one line:
class TestException extends CustomException <>
?>
Here’s a test that shows that all information is properly preserved throughout the backtrace.
function exceptionTest ()
try throw new TestException ();
>
catch ( TestException $e ) echo «Caught TestException (‘ < $e ->getMessage ()> ‘)\n < $e >\n» ;
>
catch ( Exception $e ) echo «Caught Exception (‘ < $e ->getMessage ()> ‘)\n < $e >\n» ;
>
>
echo ‘
' . exceptionTest () . '
‘ ;
?>
Here’s a sample output:
Caught TestException (‘Unknown TestException’)
TestException ‘Unknown TestException’ in C:\xampp\htdocs\CustomException\CustomException.php(31)
#0 C:\xampp\htdocs\CustomException\ExceptionTest.php(19): CustomException->__construct()
#1 C:\xampp\htdocs\CustomException\ExceptionTest.php(43): exceptionTest()
#2
Примеры
Ниже представлен пример использования возможностей обработки ошибок в PHP. Мы определим функцию для обработки ошибок, которая будет записывать информацию об ошибках в файл (используя формат XML), а в случае возникновения критических ошибок, будем дополнительно отправлять разработчикам письмо с уведомлением.
Пример #1 Обработка ошибок в скрипте
// мы будем делать нашу собственную обработку ошибок
error_reporting ( 0 );
// пользовательская функция для обработки ошибок
function userErrorHandler ( $errno , $errmsg , $filename , $linenum , $vars )
// временная метка возникновения ошибки
$dt = date ( «Y-m-d H:i:s (T)» );
// определим ассоциативный массив соответствия всех
// констант уровней ошибок с их названиями, хотя
// в действительности мы будем рассматривать только
// следующие типы: E_WARNING, E_NOTICE, E_USER_ERROR,
// E_USER_WARNING и E_USER_NOTICE
$errortype = array (
E_ERROR => ‘Ошибка’ ,
E_WARNING => ‘Предупреждение’ ,
E_PARSE => ‘Ошибка разбора исходного кода’ ,
E_NOTICE => ‘Уведомление’ ,
E_CORE_ERROR => ‘Ошибка ядра’ ,
E_CORE_WARNING => ‘Предупреждение ядра’ ,
E_COMPILE_ERROR => ‘Ошибка на этапе компиляции’ ,
E_COMPILE_WARNING => ‘Предупреждение на этапе компиляции’ ,
E_USER_ERROR => ‘Пользовательская ошибка’ ,
E_USER_WARNING => ‘Пользовательское предупреждение’ ,
E_USER_NOTICE => ‘Пользовательское уведомление’ ,
E_STRICT => ‘Уведомление времени выполнения’ ,
E_RECOVERABLE_ERROR => ‘Отлавливаемая фатальная ошибка’
);
// определим набор типов ошибок, для которых будет сохранён стек переменных
$user_errors = array( E_USER_ERROR , E_USER_WARNING , E_USER_NOTICE );
if ( in_array ( $errno , $user_errors )) $err .= «\t
>
$err .= «\n\n» ;
// для тестирования
// echo $err;
// сохраняем в журнал ошибок, а если произошла пользовательская критическая ошибка, то отправляем письмо
error_log ( $err , 3 , «/usr/local/php4/error.log» );
if ( $errno == E_USER_ERROR ) mail ( «phpdev@example.com» , «Пользовательская критическая ошибка» , $err );
>
>
function distance ( $vect1 , $vect2 )
if (! is_array ( $vect1 ) || ! is_array ( $vect2 )) trigger_error ( «Некорректные параметры функции, ожидаются массивы в качестве параметров» , E_USER_ERROR );
return NULL ;
>
if ( count ( $vect1 ) != count ( $vect2 )) trigger_error ( «Векторы должны быть одинаковой размерности» , E_USER_ERROR );
return NULL ;
>
for ( $i = 0 ; $i < count ( $vect1 ); $i ++) $c1 = $vect1 [ $i ]; $c2 = $vect2 [ $i ];
$d = 0.0 ;
if (! is_numeric ( $c1 )) trigger_error ( «Координата $i в векторе 1 не является числом, будет использовать ноль» ,
E_USER_WARNING );
$c1 = 0.0 ;
>
if (! is_numeric ( $c2 )) trigger_error ( «Координата $i в векторе 2 не является числом, будет использовать ноль» ,
E_USER_WARNING );
$c2 = 0.0 ;
>
$d += $c2 * $c2 — $c1 * $c1 ;
>
return sqrt ( $d );
>
$old_error_handler = set_error_handler ( «userErrorHandler» );
// использование неопределённой константы, будет генерироваться предупреждение
$t = I_AM_NOT_DEFINED ;
// определим несколько «векторов»
$a = array( 2 , 3 , «foo» );
$b = array( 5.5 , 4.3 , — 1.6 );
$c = array( 1 , — 3 );
// генерируем пользовательскую ошибку
$t1 = distance ( $c , $b ) . «\n» ;
// генерируем ещё одну пользовательскую ошибку
$t2 = distance ( $b , «я не массив» ) . «\n» ;
// генерируем пользовательское предупреждение
$t3 = distance ( $a , $b ) . «\n» ;