check.pl -- Consistency checking

This library provides some consistency checks for the loaded Prolog program. The predicate make/0 runs list_undefined/0 to find undefined predicates in `user' modules.

See also: - gxref/0 provides a graphical cross referencer; - PceEmacs performs real time consistency checks while you edit; - library(prolog_xref) implements `offline' cross-referencing; - library(prolog_codewalk) implements `online' analysis

check is det

Run all consistency checks defined by checker/2. Checks enabled by default are:

list_undefined/0 reports undefined predicates
list_trivial_fails/0 reports calls for which there is no matching clause.
list_redefined/0 reports predicates that have a local definition and a global definition. Note that these are not errors.
list_autoload/0 lists predicates that will be defined at runtime using the autoloader.

list_undefined is det

list_undefined(+Options) is det

Report undefined predicates. This predicate finds undefined predicates by decompiling and analyzing the body of all clauses. Options:

module_class(+Classes): Process modules of the given Classes. The default for classes is [user]. For example, to include the libraries into the examination, use [user,library].

See also: - gxref/0 provides a graphical cross-referencer.; - make/0 calls list_undefined/0

list_autoload is det

Report predicates that may be auto-loaded. These are predicates that are not defined, but will be loaded on demand if referenced.

See also: - autoload/0
To be done: - This predicate uses an older mechanism for finding undefined predicates. Should be synchronized with list undefined.

list_redefined

Lists predicates that are defined in the global module user as well as in a normal module; that is, predicates for which the local definition overrules the global default definition.

list_void_declarations is det

List predicates that have declared attributes, but no clauses.

list_trivial_fails is det

list_trivial_fails(+Options) is det

List goals that trivially fail because there is no matching clause. Options:

module_class(+Classes): Process modules of the given Classes. The default for classes is [user]. For example, to include the libraries into the examination, use [user,library].

trivial_fail_goal(:Goal)[multifile]

Multifile hook that tells list_trivial_fails/0 to accept Goal as valid.

list_strings is det

list_strings(+Options) is det

List strings that appear in clauses. This predicate is used to find portability issues for changing the Prolog flag double_quotes from codes to string, creating packed string objects. Warnings may be suppressed using the following multifile hooks:

string_predicate/1 to stop checking certain predicates
valid_string_goal/1 to tell the checker that a goal is safe.

See also: - Prolog flag double_quotes.

string_predicate(:PredicateIndicator)[multifile]

Multifile hook to disable list_strings/0 on the given predicate. This is typically used for facts that store strings.

valid_string_goal(+Goal) is semidet[multifile]

Multifile hook that qualifies Goal as valid for list_strings/0. For example, format("Hello world~n") is considered proper use of string constants.

checker(:Goal, +Message:text)[multifile]

Register code validation routines. Each clause defines a Goal which performs a consistency check executed by check/0. Message is a short description of the check. For example, assuming the my_checks module defines a predicate list_format_mistakes/0:

:- multifile check:checker/2.
check:checker(my_checks:list_format_mistakes,
              "errors with format/2 arguments").

The predicate is dynamic, so you can disable checks with retract/1. For example, to stop reporting redefined predicates:

retract(check:checker(list_redefined,_)).