PHP nangani errors kanthi exceptions sing ditangkep via try/catch/finally. Nangani exceptions sing bener terus nangkep tipe-tipe specifik, nggawe custom exceptions sing meaningful, resourse cleanup, lan ora nglontarake internal details menyang users.
{
= ();
} ( ) {
(->());
} (DatabaseException ) {
();
} ( ) {
();
;
} {
();
}
Tangkep tipe specific exception (sing paling specifik dhisik), gunakake Throwable minangka catch-all final (nutupi Error lan Exception), lan gunakake finally kanggo cleanup sing kudu laku tansaya.
// throwing
if ($amount < 0) {
throw new InvalidArgumentException("Amount must be positive, got $amount");
}
// a custom exception for your domain
class InsufficientFundsException extends Exception {
public function __construct(private float $shortfall) {
parent::__construct("Short by $shortfall");
}
public function getShortfall(): float { return $this->shortfall; }
}
throw new InsufficientFundsException(50.0);
Custom exception classes nggawe error handling expressive lan ngijini callers nangkep domain errors sing specific.
try {
$db->query(...);
} catch (PDOException $e) {
// wrap with context, preserving the original as the "previous" exception
throw new RepositoryException("Failed to load user", 0, $e);
}
Argumen ketiga constructor nge-chain exception original ($e->getPrevious()), njaga full cause kanggo debugging.
✓ Catch SPECIFIC exceptions, not a blanket Throwable (unless intentionally last)
✓ Don't swallow exceptions silently (empty catch) — log or re-throw
✓ Use finally / proper cleanup for resources (files, connections)
✓ Create meaningful custom exceptions for domain errors
✓ SECURITY: log details internally; show users a generic message (don't leak
stack traces / internal info — display_errors off in production)
Nangani exceptions sing bener iku essential kanggo nggawe aplikasi PHP sing robust, reliable, lan secure.
Mangerteni struktur try/catch/finally, nangkep tipe specific exception (kanggo nangani targeted) kanthi Throwable minangka catch-all final (nutupi Error lan Exception ing PHP modern), lan nggunakake finally kanggo cleanup sing guaranteed iku fundamental everyday knowledge.
Puwastos mekanika, best practices penting: nggawe meaningful custom exceptions kanggo domain errors nggawe code expressive lan ngijini callers nangani failures sing specific; exception chaining njaga root cause kanggo debugging; lan kruwis, ora ngentheng exceptions kanthi tenang (logging utawa re-throwing sanadyan) nyegah failures sing ading.
Sugal sing paling important iku security: exceptions lan errors kudu dicatat internally nanging ora kadalumkake menyang users (stack traces lan internal details nglontarake informasi sensitif lan bantu attackers — mula display_errors mati ing production).
Mangerteni kepiye cara nangani exceptions kanthi bener — specific catches, custom exceptions, cleanup, chaining, lan secure logging tinimbang exposure — mbedakake robust, professional PHP saka fragile code sing gawe error ungracefully utawa nglontarake informasi, nggawe penting knowledge kanggo nggawe aplikasi reliable lan secure.