root/tags/lgt290/library/debugging.notes

Revision 2, 1.2 KB (checked in by pmoura, 7 years ago)

Initial revision

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1=================================================================
2Logtalk - Object oriented extension to Prolog
3Release 2.9.0
4
5Copyright (c) 1998-2001 Paulo Moura.  All Rights Reserved.
6=================================================================
7
8
9To load all objects in this group consult the debugging.loader utility
10file.
11
12You will need to load FIRST the events.loader file otherwise you will get
13a runtime error.
14
15
16The object debugger enables you to:
17
18    - spy all or specific messages to an object
19    - trace an execution
20    - specify the streams used for debugger input/output
21
22These capabilities rely on the use of the event-based programming built in
23Logtalk. That means that you can only debug public messages sent using the
24::/2 operator.
25
26You can have any number of debuggers active simultaneously, possibly
27assigning different input/output streams to each one.
28
29Input/output is one area where Prologs compilers can differ, sometimes
30because of differences in the underlying operating system. Therefore,
31it is advisable that you look at the code of class debugger before
32trying to use it. The i/o operations are done by the methods output/3,
33query_user/1 and execute_option/1.
Note: See TracBrowser for help on using the browser.