CakeFest 2024: The Official CakePHP Conference

Exception::__construct

(PHP 5, PHP 7, PHP 8)

Exception::__constructConstructor de la excepción

Descripción

public Exception::__construct(string $message = "", int $code = 0, ?Throwable $previous = null)

Construye el objeto Exception.

Parámetros

message

Mensaje de la excepción a lanzar.

code

El código de la excepción.

previous

La excepción previa utilizada por la serie de excepciones.

Nota: Llamar al constructor de la clase Exception de una subclase ignora los argumentos por omisión, si las propiedades $code y $message ya están establecidas.

Notas

Nota:

message NO es seguro binariamente.

add a note

User Contributed Notes 3 notes

up
43
talksonweb at gmail dot com
10 years ago
For those that haven't done exception chaining. Here's an example.

This allows you to add the previous exception to the next one and give yourself detailed information in the end as to what happened. This is useful in larger applications.

<?php
function theDatabaseObj(){
if(
database_object ){
return
database_object;
}
else{
throw new
DatabaseException("Could not connect to the database");
}
}

function
updateProfile( $userInfo ){
try{
$db = theDatabaseObj();
$db->updateProfile();
}
catch(
DatabaseException $e ){
$message = "The user :" . $userInfo->username . " could not update his profile information";
/* notice the '$e'. I'm adding the previous exception to this exception. I can later get a detailed view of
where the problem began. Lastly, the number '12' is an exception code. I can use this for categorizing my
exceptions or don't use it at all. */
throw new MemberSettingsException($message,12,$e);
}
}

try{
updateProfile( $userInfo );
}
catch(
MemberSettingsException $e ){
// this will give all information we have collected above.
echo $e->getTraceAsString();
}
?>
up
2
mattsch at gmail dot com
11 years ago
Be aware that while $previous is quite useful in providing exception chaining and better traceability, none of the internal php exceptions (e.g. PDOException, ReflectionException, etc) are called internally within php with $previous in mind.

So if your code throws an exception, recovers from it, then catches one of these internal php exceptions, recovers from it and throws another exception, you will not know the first exception that was thrown when calling getPrevious.

See: https://bugs.php.net/bug.php?id=63873
up
-7
ryan dot jentzsch at gmail dot com
7 years ago
Note that the code parameter is not the same as exit($code).
Also, the code argument in PHP 7 (possibly earlier versions) is cast to an int including negative values. The code below is completely valid:

<?php
try
{
throw new
\Exception('Testing', -12.12);
}
catch (
\Exception $exception)
{
$code = $exception->getCode();
if (
$code < 0)
{
exit(
abs($code));
}
}
To Top