Fetches source information for the given clause. File is the
file from which the clause was loaded. TermPos describes the
source layout in a format compatible to the subterm_positions
option of read_term/2. VarOffsets provides access to the
variable allocation in a stack-frame. See make_varnames/5 for
details.
Note that positions are character positions, i.e., not
bytes. Line endings count as a single character, regardless of
whether the actual ending is \n
or =|\r\n|_.
Defined options are:
- variable_names(-Names)
- Unify Names with the variable names list (Name=Var) as
returned by read_term/3. This argument is intended for
reporting source locations and refactoring based on
analysis of the compiled code.
- head(-Head)
- body(-Body)
- Get the head and body as terms. This is similar to
clause/3, but a seperate call would break the variable
identity.
Unify the two terms, where T2 is created by writing the term and
reading it back in, but be aware that rounding problems may
cause floating point numbers not to unify. Also, if the initial
term has a string object, it is written as "..." and read as a
code-list. We compensate for that.
NOTE: Called directly from library(trace/clause) for the GUI
tracer.
Hook into clause_info/5 that opens the stream holding the source
for a specific clause. Thus, the query must succeed. The default
implementation calls open/3 on the File property.
clause_property(ClauseRef, file(File)),
prolog_clause:open_source(File, Stream)
Create a Term varnames(...)
where each argument contains the name
of the variable at that offset. If the read Clause is a DCG rule,
name the two last arguments <DCG_list> and <DCG_tail>
This predicate calles the multifile predicate
make_varnames_hook/5 with the same arguments to allow for user
extensions. Extending this predicate is needed if a compiler
adds additional arguments to the clause head that must be made
visible in the GUI tracer.
- Arguments:
-
Offsets | - List of Offset=Var |
Names | - List of Name=Var |
What you read isn't always what goes into the database. The task
of this predicate is to establish the relation between the term
read from the file and the result from decompiling the clause.
This predicate calls the multifile predicate unify_clause_hook/5
with the same arguments to support user extensions.
- Arguments:
-
Module | - is the source module that was active when loading this
clause, which is the same as prolog_load_context/2 using the
module context. If this cannot be established it is the module to
which the clause itself is associated. The argument may be used to
determine whether or not a specific user transformation is in scope.
See also term_expansion/2,4 and goal_expansion/2,4. |
- To be done
- - This really must be more flexible, dealing with much
more complex source-translations, falling back to a
heuristic method locating as much as possible.
Deal with translations implied by the compiler. For example,
compiling (a,b),c yields the same code as compiling a,b,c.
Pos0 and Pos still include the term-position of the head.