Home/ Questions/Q 40667
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-10T15:03:34+00:00

This is written in PHP, but it’s really language agnostic. try { try {

  • 0

This is written in PHP, but it’s really language agnostic.

try {     try     {         $issue = new DM_Issue($core->db->escape_string($_GET['issue']));     }     catch(DM_Exception $e)     {         throw new Error_Page($tpl, ERR_NOT_FOUND, $e->getMessage());     } } catch(Error_Page $e) {     die($e); }

Is nested try, catch blocks a good practice to follow? It seems a little bulky just for an error page – however my Issue Datamanager throws an Exception if an error occurs and I consider that to be a good way of error detecting.

The Error_Page exception is simply an error page compiler.

I might just be pedantic, but do you think this is a good way to report errors and if so can you suggest a better way to write this?

Thanks

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. You’re using Exceptions for page logic, and I personally think that’s not a good thing. Exceptions should be used to signal when bad or unexpected things happen, not to control the output of an error page. If you want to generate an error page based on Exceptions, consider using set_exception_handler. Any uncaught exceptions are run through whatever callback method you specify. Keep in mind that this doesn’t stop the ‘fatalness’ of an Exception. After an exception is passed through your callback, execution will stop like normal after any uncaught exception.

    • 0