|
CLEO and Tcl/TK have many layers of error traps. This document will familiarize you with what you should expect if some error occurs. CLEO Info, Warning, and Error MessagesWe have added numerous informational, warning, and error traps to our CLEO code. Examples of where we use such traps are:
Tcl/Tk Error Messages:If we have made a coding error, Tcl/Tk has a built in error trap routine that in many cases will automatically detect the problem. We have modified the standard error trap so that a popup dialog will appear that will give you the choice to e-mail us a bug report, including a full stack trace of where the error occurred, examine the stack trace for yourself, or ignore the error and try to continue. In any case, the application will try to continue executing. If the problem is severe enough you might get more of these popup windows.
Untrapped Errors or BugsIf an error occurs that one of these methods doesn't trap, you should send a bug report to us using the GNATS bug reporting web page. You can get to the web page from every CLEO application's Help menu or from the URL: http:/etamin.gb.nrao.edu .You might also want to use the feedback form accessible from every CLEO application's Help menu or at the URL: http://www.gb.nrao.edu/~rmaddale/CLEOManual/feedback.html |
Copyright © 2000 Associated Universities, Inc. Washington
D.C., USA |