The debugger pauses at leashed ports when tracing or when finding a spy + character for predicate spy points, and a * character for Port number, when a spy point is set for the current clause or goal, theĭebugger will print a # character for line number spy points, a Note that, when tracing, spy points will be ignored. Might be alternative solutions for the goal. When a call succeeds with choice-points pending, thus indicating that there The debugger also providesĭeterminism information by prefixing the exit port with a * character Succeeds with the answer ::female(morticia). In the output above, you can see for example that the goal ::female(_1082) Numbers are unique and allows us to correlate the ports used for a goal. Each trace line starts with the port,įollowed by the goal invocation number, followed by the goal. While tracing, the debugger will pause for user input at each leashed port, This feature is a consequence of the encapsulation of Of spy points allows the user to specify the Information to allow tracing of the goal execution. WhenĬompiling an entity in debug mode, Logtalk decorates clauses with source Second,ĭebugging is only possible for entities compiled in debug mode. When compared with some of the more sophisticated Prolog debuggers. This translates to a different, although similar, set of debugging features Unlike most Prolog debuggers, the Logtalk debugger is not a built-in featureīut a regular Logtalk application using documented debugging hook predicates. Implementation of the Logtalk debugger that you should be aware. There are some differences, however,īetween the usual implementation of Prolog debuggers and the current This tool implements debugging features similar to
It can also be loaded automatically at startup time by using a
Using the term-expansion mechanism for debugging.Defining line number and predicate spy points.Declarative object-oriented programming.
0 kommentar(er)
