Any time an instance of jsx3.lang.Exception is created, it stores the current call stack. This can be accessed with either the getStack() or printStackTrace() methods of the class. This feature can be very helpful when diagnosing a problem in an application. Unfortunately, in Internet Explorer, the native exception class does not store stack information. Therefore, an instance of jsx3.lang.NativeError only contains the stack up to the point when it was created, not up to the point where the error it wraps was raised. The one exception to this is when a native error reaches the top of the call stack. In that particular case, the General Interface logging system does have access to the entire stack up to the function where the error was raised. This is problematic from the point of view of a developer, however, because the choice is between maintaining the stack by catching an error but losing information about how that error was created and seeing the full stack trace of the error but not being able to recover from the error. One possible development practice to deal with this shortcoming of Internet Explorer is to include fewer try...catch statements in the early stages of developing an application and including more as the quality of the code improves. |
Contents
|