Managing Exception

Jakz, Basically if an error is thrown you want to handle it gracefully. PHP has created ways to somewhat handle the errors. Rather than putting your code into an infinite loop or having your machine catch on fire, it politely displays stuff like the error number, a snippet of where the error is, and some other useful info to debug the error. So basically if you have someone using your website and something doesn't work like you intended when you wrote the code you don't want the user to see a bunch of gobbly glop that exposes your code as well as file names for you php files. Not only would it be bad for your customer that paid you money to write the application, it could be a security vulnerability. So what you are doing by managing exceptions is creating custom ways to handle those errors. Maybe if an error is thrown you want your application to skip over the next block of code because you know it won't work. Maybe you want to display a friendly message and apologize for the error. Whatever you want, you can do. You first try your code and then catch any exceptions that might be thrown. This lets your application flow nice and smoothly with no angry users or customers and with no calls to fire department because of burning computers.

does that help a little?

w3schools Exception handling. (typically more down to earth than php.net explanations)

how to handle errors in OOP