next previous up contents index
Next: exaEdit Tests Previous: Inserting Record Numbers Up: Functions


exaEdit Errors

It is very difficult to write exaEdit, as any large program, without mistakes. Unfortunately, one has to live with the danger of an unexpected abortion of the program. To save as much as possible of the work you have done, exaEdit tries to write the content of the altered workfiles in new files on the disk. In particular, the following things happen:

exaEdit leaves the window mode and performs the rest of its jobs in the line mode. First, there appears one of these messages:

Second, a file exaEdit.dmp is opened, in which exaEdit is supposed to write information that could be necessary for the search for mistakes. Success or failure of this task lead to the message

The content of the file exaEdit.dmp cannot be predicted. It depends on the progress of exaEdit and on the place, at which the program exaEdit was aborted.

To save the changed workfiles, exaEdit checks all workfiles on whether they were altered but not saved yet. For every such a workfile a file with a certain name is opened. All the records of the workfile are expected to be written in the new file. Success or failure of the opening of the new file leads to the message

Here, the following abbreviations are used:
      jjjjfor the year,
      mm for the month,
      tt for the day,
      hh for the hour,
      mm for the minute,
     ss for the second,
      wfn for the name of the workfile,
      dsn for the name of the file.
If the records of the workfile could be saved successfully, you receive the message:

After every the workfiles have been checked and saved to files when necessary, the protocol file exaEdit.dmp is closed (if it was possible to open it). This is indicated by the message


next previous up contents index
Next: exaEdit Tests Previous: Inserting Record Numbers Up: Functions