10.18.2 Debugger Changes
- The meaning of the
goal(G) breakpoint test has changed: it succeeds
if the current goal is an instance of
G, instead of checking if the
current goal unifies with
G. Similarly for the
- Any variable instantiations introduced in the evaluation of the test
part are undone before executing the action part.
parent_pred/[1,2] tests perform module name expansion on their
flit/2 commands are allowed at non-call
ports, too; their module name expansion rules have changed.
current_breakpoint/4 is changed to
current_breakpoint/5. It now returns the breakpoint conditions in
exactly the same form as given to
- The interpretation of the first argument of
changed; the order of list elements does not matter any more.
- The new
get condition allows to access action variables from
within the action part.
exited/1 replaces test
- A breakpoint condition can be a variable at
time, as long as this variable gets instantiated by evaluation time.
- Breakpoint macros are expanded at
add_breakpoint time, rather
than during evaluation.
- It is not possible any more to redefine a built-in breakpoint condition
using the breakpoint expansion mechanism.