Skip to content

Commit 7236ead

Browse files
committed
Fix readme one last once
1 parent 853c6d4 commit 7236ead

File tree

1 file changed

+11
-8
lines changed

1 file changed

+11
-8
lines changed

README.org

Lines changed: 11 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -3,13 +3,14 @@
33
A (WIP) adaptation of the classic [[https://sites.google.com/site/prologsite/prolog-problems][99 Prolog Problems]] by [[https://sites.google.com/site/prologsite/author][Werner Hett]] to
44
higher-order logic programming in [[http://www.lix.polytechnique.fr/~dale/lProlog/][λProlog]].
55

6-
Before undertaking the problems, you may wish to review this slight adaptation
7-
of Hett's wonderful guidance:
86

97
* The spirit of the problems
8+
Before undertaking the problems, you may wish to review this slight adaptation
9+
of Hett's wonderful guidance (additions in =[]=):
1010

11+
#+begin_quote
1112
The purpose of this problem collection is to give you the opportunity to
12-
practice your skills in higher-order logic programming. Your goal should be to
13+
practice your skills in [higher-order] logic programming. Your goal should be to
1314
find the most elegant solution of the given problems. Efficiency is important,
1415
but logical clarity is even more crucial. Some of the (easy) problems can be
1516
trivially solved using built-in predicates. However, in these cases, you learn
@@ -18,22 +19,24 @@ more if you try to find your own solution.
1819
Every predicate that you define should begin with a comment that describes it in
1920
a declarative statement. Do not describe procedurally, what the predicate does,
2021
but write down a logical statement which includes the arguments of the
21-
predicate, and then describe the flow of data through the unification of terms.
22+
predicate, [and then describe the flow of data through the unification of terms].
23+
24+
[Construct types to formalize the possible data for the predicates and
25+
functions, then specify the types and modes for their arguments.]
26+
#+end_quote
2227

23-
Construct types to formalize the possible data for the predicates and
24-
functions, then specify the types and modes for their arguments.
2528

2629
* The problems
2730

28-
#+begin_src
31+
#+begin_quote
2932
The problems have different levels of difficulty. Those marked with a single
3033
asterisk (*) are easy. If you have successfully solved the preceeding problems
3134
you should be able to solve them within a few (say 15) minutes. Problems marked
3235
with two asterisks (**) are of intermediate difficulty. If you are a skilled
3336
Prolog programmer it shouldn't take you more than 30-90 minutes to solve them.
3437
Problems marked with three asterisks (***) are more difficult. You may need more
3538
time (i.e. a few hours or more) to find a good solution.
36-
#+end_src
39+
#+end_quote
3740

3841
- [[file:problems/lists.org][Lists]]
3942

0 commit comments

Comments
 (0)