Trapping for Errors
An introduction to REALbasic exceptions and traps
Issue: 8.6 (September/October 2010)
Author: JC Cruz
Article Description: No description available.
Article Length (in bytes): 30,512
Starting Page Number: 44
RBD Number: 8609
8609.zip Updated: Thursday, September 2, 2010 at 9:17 AM
Related Web Link(s):
Known Limitations: None
Excerpt of article text...
Error handling is a must for any software product slated for public use. So in today's article, we will explore how to detect and deal with code errors in a REALbasic project. We will learn how to package an error as an exception, and how to trap it at run time. And we will study how our error traps interact with each other and with the main process thread.
So sit back, relax, and have your mug of warm brew within reach.
When Errors Occur
Face it. Errors abound in any software product bound for widespread public use. Plus, the more complex a given product, the more likely it is to have errors. Often, the label error-free means that testing has not found any errors severe enough to detract product quality.
Errors happen because humans plan and write software with tools and hardware built by other humans. Some errors cause crashes, which terminates a product session and endangers critical data. Some cause software freezes, blocking users from interacting with the product. And some cause data corruption -- unwanted changes to user data.
...End of Excerpt. Please purchase the magazine to read the full article.
Article copyrighted by REALbasic Developer magazine. All rights reserved.