Welcome to the final part of the four-part series “Subclassing exceptions in PHP 5.” By means of a hands-on approach, this series walks you through using inheritance to build finely-tuned exception subclasses. These subclasses can be used to handle, via multiple “try-catch” blocks, several failures that might occur during the execution of a given web application.
If you’re a PHP developer who wants to learn the basics of implementing customized exceptions in PHP 5, then look no further, because you’ve come to the right place. This is the third part of a four-part series entitled “Subclassing exceptions in PHP 5.” It teaches you how to extend the native exception mechanism bundled with PHP 5 by using inheritance, and complements the corresponding theory with copious, illustrative hands-on examples.
Welcome to the second part of a four-part series on sub classing exceptions in PHP 5. In the first part of this series, you learned how to build a basic processing class which could throw customized exceptions to client code. What you haven't yet learned, however, is how to build the code to catch these exceptions. That is the topic of this article.
If you do any serious programming, whether it's in PHP 5 or some other language, you've needed to know how to handle run time errors and other "exceptional" conditions. You can do this by making your program throw generic exceptions. Or you can unlock the potential of PHP 5 and learn how to create custom exceptions, which is the subject of this four-part series.
Do you want to know how to build an error logging system using the chain of responsibility schema with PHP? If your answer is a loud yes, then in this group of articles you’ll find what you’ve been looking for! Welcome to the concluding part of the series “Understanding the chain of responsibility between PHP objects.” This set of three tutorials shows you how to define a specific chain of responsibility that involves several PHP objects, and applies this concept to creating an expandable error logging mechanism.
After introducing you to the subject of this series, I'd like to step back quickly to the previous tutorial and recall the topics covered in it. This will make it a bit easier for you to grasp the concepts that I plan to explain in this final part.
As you'll possibly remember, in the previous article I went through the development of a comprehensive error logging system. It used the chain of responsibility pattern to establish the scope of where each involved PHP class should act.
By following this approach, it was feasible to create an error handling mechanism where every component was initially provided with a limited capacity for processing a particular failure -- and when the error in question couldn't be properly handled, it would be immediately transferred to the corresponding parent module.
Indeed, if you reread the above paragraph, it should be clear to you what a chain of responsibility is all about: once a group of hierarchically organized classes have been created, the responsibility for handling a given task is moved from the bottom to the top of the stack structure. Sounds good, doesn't it?
Now, paying attention to the topics that will be covered in this tutorial, what you'll learn here will consist essentially of applying the chain of responsibility schema to expand the capacity of the error logging system that was developed previously.
If you’re one of those PHP developers that wants to expand your background in pattern-based programming, then this article may suit your needs. Welcome to the second part of the series "Understanding the Chain of Responsibility Between PHP Objects." Comprised of three installments, this series goes through the basics of building a chain of responsibility across several PHP objects, and teaches you how to apply this pattern by using copious code samples.
This coding tip demonstrates how to deal with PHP core notices and warning (aka recoverable errors) in the exception way, using try/catch statement.
Let's face it - none of us write perfect code, and your almost-perfect PHP scripts are bound to throw an error now and then, even if you've tested them hundreds of times. It's simply impossible to rule out everything, and that's no problem really, as long as you handle the errors properly.
PHP scripts should never publicly display any error on a live production website, as it could lead to security problems, and it just looks bad to your visitors. Can you imagine your bank's website throwing an error when trying to view your bank account? I'm sure that wouldn't inspire much faith in you.
That's why in this article I'm going to show you how to handle errors in PHP. In this article I will first take you through the basics of error handling, by catching all PHP errors with the set_error_handler() function. After that we'll have a look a new PHP 5 feature called Exceptions which can also be used to create and catch errors. At the end of the article I will show you how to trigger your own errors.
Welcome to the last part of the series “Error Handling in PHP.” In two parts, this series introduces the basics of error handling in PHP. It demonstrates some of the most common methods for manipulating errors in PHP 4, and explains the implementation of exceptions in PHP 5, particularly in object-oriented environments.
As with any programming language, when you code in PHP, it helps immensely if you set up your applications to handle errors gracefully. This article explores some of the most common error checking methods available in PHP, and provides hands-on examples that use different error handling methods.
