Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
Minor update to the documentation of the new bench example
  • Loading branch information
pmoura committed Jul 9, 2018
1 parent 12994f4 commit d162c79
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 6 deletions.
4 changes: 2 additions & 2 deletions examples/bench/NOTES.md
Expand Up @@ -24,7 +24,7 @@ Logtalk wrappers for those programs. Loading this example and an individual
plain Prolog benchmark allows us to evaluate the overhead of the implicit
execution context argument that the Logtalk compiler adds to object (and
category) predicates. Note that this old set of benchmarks don't cover all
features of modern day Prolog and Logtalk programing.
features of modern day Prolog and Logtalk programing (e.g. meta-predicates).

All plain Prolog programs define a `top/0` predicate to run the benchmark.
The Logtalk versions provide a `top/0` public predicate.
Expand All @@ -45,7 +45,7 @@ The copyright of the plain Prolog benchmark programs should be assumed to
belong to the original authors. Most of the programs lack any licensing
information or distribution terms, however. Some don't even mention the
author. Some go back to the earlier days of Prolog where programs were
often shared in an academic setting without concerns about licensing.
often shared in an academic setting without much concern about licensing.
We redistribute these programs in good faith but undersand that anyone
repackaging the Logtalk distribution may choose to delete this example
given the unclear legal status of some of these files.
8 changes: 4 additions & 4 deletions examples/bench/SCRIPT.txt
Expand Up @@ -43,8 +43,8 @@ yes
Time = ...
yes

% for accurate timings of ::/2 goals, the lgtunit::benchmark/3 calls
% should be made from compiled code in order to avoid the top-level
% for accurate timings of compiled ::/2 goals, the lgtunit::benchmark/3
% calls should be made from compiled code in order to avoid the top-level
% interpretation of the goals; an handy alternative is to use:

| ?- logtalk<<(lgtunit::benchmark(boyer::top,1000,Time)).
Expand All @@ -54,8 +54,8 @@ yes

% some Prolog compilers such as SWI-Prolog and YAP provide a handy time/1
% predicate that may also be used in alternative to the `lgtunit` benchmark
% predicates (the adapter files for these two systems ensure the argument
% of the time/1 is fully compiled prior to calling it):
% predicates (the adapter files for these two systems ensure that ::/2 goals
% in the argument of the time/1 are fully compiled prior to calling them):

| ?- time(true). % autoload if necessary
...
Expand Down

0 comments on commit d162c79

Please sign in to comment.