home / experts / javascript / column38 |
|
Handling JavaScript-thrown ExceptionsIn any programming language, your code will throw a run-time exception when trying to execute an illegal command. One of the most trivial illegal operations you may attempt is a division by zero. Your operating system will definitely complain when trying to divide a number by zero. This is not a good example, as JavaScript does execute the operation and assigns More often than not, you want to avoid system errors. System messages are usually cryptic and do not make sense for the average user. In fact, system messages are bad for your reputation as a programmer, as they are clear and tangible evidence of your bugs. Naturally, you'll want to avoid these messages by checking for them in your code, before they hit the operating system. Checking for exceptions in your code will surely make it more cumbersome. Mingling error-checking with the normal flow of your code is inevitable when the language does not support exception handling. The following skeleton code checks for two errors: accessing a null object and out of range array element:
The crux of the exception handling support in JavaScript (as well as in other languages, as explained later in this column) is the
Here is another example that you can actually run on your computer:
The exception enforced in this example is accessing an array element that is outside the array boundaries. The highest index used is |
Produced by Yehuda Shiran and Tomer Shiran
Created: April 26, 1999
Revised: April 26, 1999
URL: http://www.webreference.com/js/column38/jserror.html