☰

Persistent database for incremental analysis

This module handles the maintenance of the persistent database needed for resuming a stopped incremental analysis.

Usage and interface

Documentation on exports

PREDICATEset_loaded_module/1
No further documentation available for this predicate.

PREDICATEreset_persistent_db/0
Removes previous persistent data of an incremental analysis.

PREDICATEload_persistent_if_needed/2

Usage:load_persistent_if_needed(Top,Fs)

Restores the persistent analysis of tiles in list Fs if it existed and the flag inc_persistent is on.

  • The following properties should hold at call time:
    (atm/1)Top is an atom.
    (list/1)Fs is a list.

PREDICATEtop_level_of_files/2
No further documentation available for this predicate.

PREDICATEhas_dump/2
No further documentation available for this predicate.

PREDICATEset_inc_persistent/1

Usage:set_inc_persistent(St)

This flags controls the storage of persistent information after the analysis.

  • The following properties should hold at call time:
    (inc_persistent_status/1)St Defines whether the analysis should be stored persistently.

REGTYPEinc_persistent_status/1
inc_persistent_status(X)

X can be:

  • on: Analysis information will be stored in the same location as the analyzed code (as dump files). This is usefull when analysis scheduling involves loading and unloading modules. To perform an analysis from scratch, these files have to be manually removed.
  • off: No information is stored.

Usage:inc_persistent_status(St)

St Defines whether the analysis should be stored persistently.

    PREDICATEsave_persistent_analysis/0

    Usage:

    Makes incremental analysis persistent by saving it to disk.

      PREDICATEclean_persistent_analysis/0

      Usage:

      Removes the persistent incremental analysis from disk.

        Documentation on imports

        This module has the following direct dependencies:
        Generated with LPdoc using Ciao