next up previous index
Next: Operating System Interface Up: Saving States Previous: Invoking Saved States

Limitations

A saved file may be copied between directories if desired. However, the saved file may only be restored using the ECLiPSe binary from which it was created (e.g. you can not use another ECLiPSe version).

The input/output state (opened streams etc.) is not saved by either save_program/1 or save/1. It is re-initialised by restore/1, i.e.\ after restoring only the ECLiPSe standard streams are opened.

Dynamically loaded object files (i.e. C externals loaded using load/1) are not contained in saved states. They have to be loaded again after restarting a saved state. Alternatively, static linking can be used, as described in chapter gif on page gif.

The saved state facilities might not always work properly together with the MegaLog features, e.g. creating a saved state while the database is open.



Micha Meier
Mon Mar 4 12:11:45 MET 1996