72b037275f
git-svn-id: https://yap.svn.sf.net/svnroot/yap/trunk@1288 b08c6af1-5177-4d33-ba66-4b1c6b8b522a
34 lines
1.2 KiB
Plaintext
34 lines
1.2 KiB
Plaintext
=================================================================
|
|
Logtalk - Object oriented extension to Prolog
|
|
Release 2.25.0
|
|
|
|
Copyright (c) 1998-2005 Paulo Moura. All Rights Reserved.
|
|
=================================================================
|
|
|
|
|
|
To load this example and for sample queries, please see the SCRIPT file.
|
|
|
|
You will also need to load the following files in the library directory:
|
|
types_loader, events_loader, metapredicates_loader, and dates_loader.
|
|
Alternatively, you may simply load the library all_loader file to load all
|
|
library entities.
|
|
|
|
This is a very simple example of the use of events and monitors to make
|
|
profilers for an application. It's easy to modify to make it do much more.
|
|
For instance, most Prolog compilers give you access to data concerning space
|
|
usage (stacks, heap, etc).
|
|
|
|
The example defines three objects:
|
|
|
|
message_counter
|
|
using events, this object allows us to count the messages sent to
|
|
spied objects
|
|
|
|
stop_watch
|
|
using events, this object simply prints the cpu time before and after
|
|
a message sent to a spied object
|
|
|
|
timer
|
|
this object implements a method that sends a message to an object a
|
|
specified number of times, returning the average execution time
|