Question

In some libraries it is common practice to make custom Exception classes for every error condition, like:

class FileNotFound_Exception extends Exception {}

You can handle certain type of Exception, however you cannot read all source code of all libraries to remember each Exception class, and cannot take full advantage of using custom Exceptions. Most of time I just catching them with base Exception class:

catch (Exception $e)
{
    // log and display friendly error
}

Is there other ways to have benefit of custom Exception classes, without writing long list of catch blocks?
I like Exceptions, but don’t know how to use them properly. Thank you.

Answer 1

The benefit of having your own Exception class is that you, as the author of the library, can catch it and handle it.

try {
   if(somethingBadHappens) {
     throw MyCustomException('msg',0)
   }
} catch (MyCustomException $e) {
  if(IcanHandleIt) {
    handleMyCustomException($e);
  } else {
    //InvalidArgumentException is used here as an example of 'common' exception
    throw new InvalidArgumentException('I couldnt handle this!',1,$e);
  }
}