Did you know ... Search Documentation:
Predicate style_check/1
Availability:built-in
Sourcestyle_check(+Spec)
Modify/query style checking options. Spec is one of the terms below or a list of these.

  • +Style enables a style check
  • -Style disables a style check
  • ?(Style) queries a style check (note the brackets). If Style is unbound, all active style check options are returned on backtracking.

Loading a file using load_files/2 or one of its derived predicates reset the style checking options to their value before loading the file, scoping the option to the remainder of the file and all files loaded after changing the style checking.

singleton(true)
The predicate read_clause/3 (used by the compiler to read source code) warns on variables appearing only once in a term (clause) which have a name not starting with an underscore. See section 2.15.1.10 for details on variable handling and warnings.
no_effect(true)
This warning is generated by the compiler for BIPs (built-in predicates) that are inlined by the compiler and for which the compiler can prove that they are meaningless. An example is using ==/2 against a not-yet-initialised variable as illustrated in the example below. This comparison is always false. 
always_false(X) :-
        X == Y,
        write(Y).
var_branches(false)
Verifies that if a variable is introduced in a branch and used after the branch, it is introduced in all branches. This code aims at bugs following the skeleton below, where p(Next) may be called with Next unbound. 
p(Arg) :-
        (  Cond
        -> Next = value1
        ;  true
        ),
        p(Next).

If a variable V is intended to be left unbound, one can use V=_. This construct is removed by the compiler and thus has no implications for the performance of your program.

This check was suggested together with semantic singleton checking. The SWI-Prolog libraries contain about a hundred clauses that are triggered by this style check. Unlike semantic singleton analysis, only a tiny fraction of these clauses proofed faulty. In most cases, the branches failing to bind the variable fail or raise an exception or the caller handles the case where the variable is unbound. The status of this style check is unclear. It might be removed in the future or it might be enhanced with a deeper analysis to be more precise.

discontiguous(true)
Warn if the clauses for a predicate are not together in the same source file. It is advised to disable the warning for discontiguous predicates using the discontiguous/1 directive.
charset(false)
Warn on atoms and variable names holding non-ASCII characters that are not quoted. See also section 2.15.1.1.
Tags are associated to your profile if you are logged in|Report abuse
Tags:
  • SWI7
Wouter Beek said (2017-10-28T20:01:01):0 upvotes 0 0 downvotes
Picture of user Wouter Beek.

In SWI7 (7.1.24) support for atom style checking was dropped because the limit on the length of quoted material (i.e., material within single quotes, double quotes, or tildes) was dropped.

Tinkering with the atom option through style_check/1 now produces a warning message.

In the new behavior the Prolog parser reports the start location of the quoted material in case it finds non-terminated quoted material (i.e., end-of-file character occurring before end-of-quote).