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:

  var newObject = createObject(dataPiece1, dataPiece2, dataPiece3);
  if (newObject == null) {
    // do something here when the object was not created
    ...
  }
  else {
    // getElementIndex return an index or -1 for an error
    var index = newObject.getElementIndex();
    if (index == -1) {
      // handle the error case
      ...
    }
    else {
     // finally, you can do something with index
     ...
    }
  }

  try {
    var newObject = createObject(dataPiece1, dataPiece2, dataPiece3);
    var index = newObject.getElementIndex();
      // do something with index
  }
  catch() {
    alert("System Error; Call your sw vendor");
  }
  finally {
    // do nothing
  }

People who read this tip also read these tips:

• Creating IIS Web Server Virtual Directories
• Setting Variables in XSLT
• A Sample Batch of Namespaces
• Using the Index Number as the Selecting Criterion
• Switching from XSLT to XPath for Pattern-Based Node Selection