# Visual Prolog Tutorial

Jim Mims April 2008

Contents
Contents..................................................................................................................... 2 Preface.......................................................................................................................5 What is Prolog?........................................................................................................5 What are strengths and Weaknesses?.....................................................................5 Section 1: Introduction............................................................................................... 6 The Compiler........................................................................................................... 6 Horn Clause Logic....................................................................................................6 PIE: Prolog Inference Engine....................................................................................8 Extending the Family Theory.................................................................................10 Prolog is a Programming Language.......................................................................11 Failing.................................................................................................................... 13 Backtracking..........................................................................................................13 Improving the Family Theory.................................................................................16 Recursion...............................................................................................................17 Side Effects............................................................................................................19 Conclusion............................................................................................................. 20 Section 2: A First Example......................................................................................21 Open Visual Prolog................................................................................................21 Section 3: Getting Started........................................................................................24 Typing in a Prolog program...................................................................................24 Starting Prolog.......................................................................................................24 Loading the Program.............................................................................................24 Running a query....................................................................................................25 Section 4: Facts and Rules........................................................................................26 The Rules...............................................................................................................26 The Family Tree Example......................................................................................26 Section 5: Operators and Arithmetic........................................................................29 Some Prolog Details..............................................................................................29 Arity....................................................................................................................29 Spaces................................................................................................................29 Comments..........................................................................................................29 Simple I/O in Prolog............................................................................................29 Arithmetic in Prolog...............................................................................................30 Built-In Predicates..............................................................................................30

Page 2

Arithmetic Operators..........................................................................................30 Some queries:....................................................................................................... 31 Defining your own relations...................................................................................31 Exercises............................................................................................................... 32 Section 6: Recursion.................................................................................................34 Using Recursion.....................................................................................................34 Some Examples.....................................................................................................34 Exercise:................................................................................................................35 The Towers of Hanoi...........................................................................................35 The Grid Example...............................................................................................36 Section 7: Structures................................................................................................38 The General Form of a Structure...........................................................................38 Arithmetic "Functions" and Structures..................................................................38 A simple example of using structures...................................................................38 Exercises............................................................................................................... 39 Section 8: Recursive Structures................................................................................41 Inserting an element.............................................................................................41 Exercises............................................................................................................... 42 Binary Trees..........................................................................................................42 Exercise.................................................................................................................42 Section 9: Introducing Lists......................................................................................44 Format of Lists.......................................................................................................44 Empty and Non-Empty Lists..................................................................................44 Some Examples.....................................................................................................45 The length of a list.............................................................................................45 Summing a list................................................................................................... 46 List Membership.................................................................................................46 Exercises............................................................................................................... 46 Section 10: Lists as Accumulators............................................................................48 Collecting information...........................................................................................48 Joining two lists......................................................................................................49 Reversing a List.....................................................................................................49 Exercises............................................................................................................... 51 Built-In list predicates............................................................................................51 Section 11: Backtracking and Cut.............................................................................52 Analysing Cases.................................................................................................... 52

Page 3

.......................61 File I/O...................................................................................................................................................................................................................................... 54 Yet Another Cut.............................................................................................................................................................................................................................59 Section 13: Input and Output.........57 Green cuts .................................................................................................................................................................................57 Negation as Failure...................62 Page 4 .................57 Warning!..................................57 Red cuts .............................................................................................................57 Kinds of cut................................................................................................................................................................... 55 Section 12: More Control Features......54 Another Cut........................................................................................ 58 The repeat predicate...................................................62 An Exercise..........................61 More on I/O................. 61 Saving and Restoring a Knowledge-Base...................................................................................................................61 Other Approaches to I/O......55 Exercises................................................................................................................................................................................................................................................................................................................................................................................................................................................An Example Of Using The Cut..............................................................................................53 The First Cut.58 If-then-else in Prolog....

Logic Programming Language Based on Horn clauses What are strengths and Weaknesses? Good at Grammars and Language processing Knowledge representation and reasoning Pattern matching Symbolic AI Poor at Repetitive number crunching Input/Output Page 5 . High-level interactive language.Preface What is Prolog? Programming in Logic. Edinburgh syntax is the basis of ISO standard.

It will also be placed on selected computers in the lab. PIE is a "classical" Prolog interpreter. strictly typed and mode checked. Horn Clause Logic Visual Prolog and other Prolog dialects are based on Horn Clause logic. You will of course have to master all this to write Visual Prolog programs. namely that one is the father of the other. i. I might as well have chosen it the other way around: The order of the arguments is the choice of the "designer" of the formalization. Here I have two "things": John and Bill. But here we will focus on the core of the code. then Visual Prolog Help . father is a predicate/relation taking two arguments. you must be consistent.1\bin\vip  When the program opens. etc. In Horn Clause Logic I can formalize this statement in the following way: father("Bill". Horn Clause logic is a formal system for reasoning about things and the way they relate to each other. "John"). click on Help at the top. Notice that I have chosen that the second person should be the father of the first. For this purpose we will use the PIE example that is included in the Visual Prolog distribution. types.\visual prolog 7.1 Personal Edition will be distributed in class. and a "relation" between these. the code when disregarding classes. However. types and modes.  Run setup to install the program . So in my formalization the father must always be the second person. by using this you can learn and experiment with Prolog without being concerned with classes.e.good explanations are provided Visual Prolog is object oriented. once you have chosen. In natural language I can express a statement like: John is the father of Bill.Section 1: Introduction The Compiler A disk with Visual Prolog 7. Page 6 .works under XP and Vista  To create a link to the executable (assuming you accepted the default locations) go to c:\program files. where the second is the father of the first.

father(Father. "John"). I have also introduced a predicate for the grandfather relation.father("Pam". ?. ?.father("Sue". X). GrandFather). if X is the father of Y and Y is the father of Z where X. A theory is a collection of facts and rules. GrandFather). "Bill"). grandFather(Person. Y and Z are persons. But for now we will be content with this simple formalization. while statements like "X is the grandfather of Z. When reading rules you should interpret :. With formalizations like the one above I can state any kind of family relation between any persons. But for this to become really interesting I will also have to formalize rules like this: X is the grandfather of Z.e. With facts and rules we are ready to formulate theories. Statements like "John is the father of Bill" are called facts. The purpose of the theory is to answer questions like these: Is John the father of Sue? Who is the father of Pam? Is John the grandfather of Pam? Such questions are called goals. GrandFather) :father(Person. father(Father. father("Pam". I have chosen to use variable names that help understanding better than X. It is wise to be consistent like that. GrandFather) :father(Person. Page 7 . In Horn Clause Logic I can formalize this rule like this: grandFather(Person. that the arguments of the different predicates follow some common principle. if X is the father of Y and Y is the father of Z" are called rules. i. Father). And they can be formalized like this (respectively): ?.as if and the comma that separates the relations as and.grandFather("Pam". Again I have chosen that the grandfather should be the second argument. In a more complex world this would not be sufficient because many people have same name. Father). "John"). "John"). Y and Z.I have chosen to represent the persons by their names (which are string literals). Let me state a little theory: father("Bill".

When the program starts it tries to find a solution to the goal in the theory. X = "Pam". rules and goals are called Horn clauses. A Prolog program is a theory and a goal. For example: ?. Some goals may even have many solutions. hence the name Horn Clause Logic. the Prolog Inference Engine. Some goals like the first and last are answered with a simple yes or no. Before we start you should install and build the PIE example.  Open the PIE project in the VDE and run the program. as it is described in Tutorial 01: Environment Overview When the program starts it will look like this: Select File -> New and enter the father and grandFather clauses above: Page 8 .Such questions are called goal clauses or simply goals. That comes with Visual Prolog. has two solutions: X = "Bill". Together facts.  Select "Install Examples" in the Windows start menu (Start -> Visual Prolog -> Install Examples). Y = "John".father(X. like X = "Bill". Y = "Bill". Y). PIE: Prolog Inference Engine Now we will try the little example above in PIE. For other goals like the second we seek a solution.

. Once you have "consulted" the theory. File -> Consult will load the disc contents of the file regardless of whether the file is opened for editing or not.PRO Reconsult loads whatever is in the editor. For example: When the caret is placed at the end of the line. You should see a result like this: Page 9 .While the editor window is active choose Engine -> Reconsult. In the Dialog window you should receive a message like this: Reconsulted from: . press the Enter key on your keyboard. This will load the file into the engine. if you want to save the contents use File -> Save..\pie\Exe\FILE4. On a blank line in the Dialog window type a goal (without the ?.. PIE will now consider the text from the beginning of the line to the caret as a goal to execute.in front). without saving the contents to the file. you can use it to answer goals.

You should try that yourself. whether some person is in deed the grandMother of some other person. Parent). etc. like this: parent(Person. father(Person. Parent) :. I suggest that you use persons from your own family.father(Person. You are a parent if you are a mother. because that makes it lot easier to validate. The first rule reads (recall that the second argument corresponds to the predicate name): Parent is the parent of Person. Given mother and father we can also define a parent predicate.Extending the Family Theory It is straight forward to extend the family theory above with predicates like mother and grandMother." which means or. Parent). Parent) :mother(Person. You should also add more persons. parent(Person. Parent). Therefore we can define parent using two clauses like this: parent(Person. if Parent is the mother of Person or Parent is the father of Person I will however advise you to use semicolon as little as possible (or actually not at all). There are several reasons for this: Page 10 .mother(Person. you are also a parent if you are a father. Parent) :. if Parent is the mother of Person You can also define the parent relation using semicolon ". Parent). This rule reads: Parent is the parent of Person.

Father). Sibling) :. Father). because it will require that both the father and the mother are the same: fullBlodedSibling(Person." is very small. Father). And indeed Prolog can be used as an expert system. Mother). two persons are also siblings if they have same father. father(Sibling. Sibling) :. Sibling) :mother(Person. Mother). Mother). We shall not deal with this problem now. if Mother is the mother of Person and Mother is the mother of Sibling The reason that you receive siblings twice is that most siblings both have same father and mother. Father).e. father(Person." is often a source of confusion. Prolog is a Programming Language From the description so far you might think that Prolog is an expert system. but it is designed to be a programming language. Try creating a sibling predicate! Did that give problems? You might find that siblings are found twice. especially when it is on the end of a long line. And therefore they are found twice. if you have rules like this: sibling(Person.• • The typographical difference ". We miss two important ingredients to turn Horn Clause logic into a programming language: Page 11 . The first rule reads: Sibling is the sibling of Person.mother(Person. and therefore they fulfill both requirements above. A fullBlodedSibling predicate does not have the same problem. but the semantic difference is rather big. mother(Sibling. At least if you say: Two persons are siblings if they have same mother." and ". father(Sibling. Mother). currently we will just accept that some rules give too many results.". I. rather than a programming language. ". since it is easily misinterpreted as ". Visual Prolog only allows you to use semicolon on the outermost level (PIE will allow arbitrarily deep nesting). mother(Sibling.father(Person. sibling(Person.

Y). Then the system will always try to solve the sub-goal grandFather(X. the facts and rules are always tried from top to bottom. For example. Given this evaluation strategy you can interpret clauses much more procedural.father(X. to solve the first sub-goal. When solving a particular sub-goal. Z). And we are using the rule grandFather(Person. mother(Y. Y) before it solves mother(Y. the right hand side replaces the sub-goal in the current goal. if the current goal is: ?. mother(Y. Z).e. Father). if the first (i. mother(Y. But Prolog does not use a "random" search strategy. The system maintains a current goal. Consider this rule: Page 12 . Y). i. father(Father.e. left-most) sub-goal cannot be solved then there is no solution to the overall problem and then the second sub-goal is not tried at all. Father). instead it always use the same strategy. if the current goal is: ?.father(Person. When a sub-goal is solved by using a rule.grandFather(X. Z).e. You can do it in many ways. Y). then the resulting current goal will be: ?.father(X. you might just consider at the second fact in the theory and then you have a solution. Z). I will explain the details later. father(Father. Y). i. GrandFather).• • Rigid search order/program control Side effects Program Control When you try to find a solution to a goal like: ?. Notice that some variables in the rule have been replaced by variables from the subgoal. which is always solved from left to right.grandFather(X. GrandFather) :.

GrandFather) is called. GrandFather) :.father(Person. In the logical reading we interpreted this clause as: Parent is the parent of Person if Parent is the mother of Person or Parent is the father of Person. GrandFather). Or even like this: When grandFather(Person. With this procedural reading you can see that predicates correspond to procedures/subroutines in other languages. when it is not the goal that fails. During the execution of a program a lot of alternative choices (known as backtrack points) might exist from earlier predicate calls. father(Person. This will be discussed in details in the next sections. GrandFather) first solve father(Person. Father) and then call father(Father. first call father(Person. GrandFather). Prolog handles such multiple choices by first trying one choice and later (if necessary) backtracking to the next alternative choice. X) has no solution as there are no parent facts or rules that applies to "Hans". Given the strict evaluation we can read this rule like this: To solve grandFather(Person. If Page 13 . If some predicate call fails. then we will backtrack to the last backtrack point we met and try the alternative solution instead. GrandFather).e. Father). for example calling parent("Hans". Parent) :mother(Person. Father) and then solve father(Father. The next section will explain how failing is treated in the general case. Parent). Failing A predicate invocation might not have any solution in the theory. Parent). Consider the clause parent(Person. etc. If the goal fails then there is simply no solution to the goal in the theory. The "or" introduces two possible solutions to an invocation of the parent predicate. The main difference is that a Prolog predicate can return several solutions to a single invocation or even fail. We say that the predicate call fails. Backtracking In the procedural interpretation of a Prolog program "or" is treated in a rather special way. father(Father.grandFather(Person. i.

meaning that there was no solution to it. And then we try the first clause. BB). Page 14 . father(Person. such that BB is the father of AA and CC is a parent of BB.e. parent(BB. "Bill"). father("Pam". Consider the clauses: father("Bill". "John"). Parent)) and then call mother(Person. "John"). and then try the first clause. When father is invoked we first record a backtrack point to the second clause. BB and CC. but one choice might itself involve a choice. With this in mind we can interpret the clause above like this: When parent(Person. to the call to father(Person. Example To illustrate how programs are executed I will go through an example in details. "Bill"). father("Jack". we first record a backtrack point. parent(Person. CC). father("Pam". Consider the clauses: father("Bill". This goal states that we want to find three persons AA. If there are three or more choices we still only create one backtrack point. father("Pam". "Bill"). but that backtrack point will start by creating another backtrack point. Parent) A predicate that has several classes behave in a similar fashion.father(AA.no further backtrack points exists then the overall goal has failed. Parent). The backtrack point we create points to some code. "John"). Parent) :mother(Person. When father is invoked. "Bill"). And then consider this goal: ?. which will itself create a backtrack point (namely to the third clause) and then try the second clause. "Lisa"). Thus all choice points have only two choices. "Bill"). Parent). father("Bill". father("Jack". Parent) is called first record a backtrack point to the second alternative solution (i. Consider these clauses: mother("Bill".

Therefore we backtrack to the second clause. The mother predicate fails when the first argument is "John" (because it has no clauses that match this value in the first argument).e. So we now effectively have the goal: ?. In case of failure we backtrack to the last backtrack point we created. Page 15 . but that fails. When executing the father predicate we first create a backtrack point to the second clause. After the creation of this backtrack point we are left with the following goal: ?.mother("John". We now try to use the first father clause on the goal. The second clause also fails. CC). The current goal is an "or" goal. So we call the mother predicate.parent("John".mother("John". So we will now pursuit the goal: ?. which gives the following goal: ?. so we backtrack to the third clause. because the first arguments do not match (i.father("John". which corresponds to the first call in the original goal. but before we use this clause we create a backtrack point to the third clause. one to the second alternative in the parent clause. "John" does not match "Bill"). CC). So we call parent. CC). CC). and then use the first clause. When calling father this time. we will again first create a backtrack point to the second father clause.As mentioned we always solve the goals from left to right. so first we call the father predicate. and one to the second clause in the father predicate. father("John". so we create a backtrack point to the second alternative and pursuit the first. since "John" does not match "Pam". since "John" does not match "Jack". Recall that we also still have a backtrack point to the second clause of the father predicate. You will notice that the variables in the clause have been replaced with the actual parameters of the call (exactly like when you call subroutines in other languages). Using the first clause we find that AA is "Bill" and BB is "John". This also fails. CC). We now have two active backtrack points.

So we now effectively have the goal: ?.mother("Bill". because it is rather difficult to determine the sex of a person (unless the person is a father or mother). BB = "Bill". So all in all there are four solutions to the goal. BB = "Bill". CC = "Lisa". CC). CC). The problem is that we have chosen a bad way to formalize our theory.mother("Bill". If we instead first focus on the entities. When calling parent we now get: ?. then the result will naturally become different. which was the second alternative in the parent predicate: ?. BB = "Bill". AA = "Jack". CC). BB = "Bill". CC). Using the second clause we find that AA is "Pam" and BB is "Bill". father("Bill".Now we must backtrack all the way back to the first father call in the original goal. CC = "John". The reason that we arrived at this theory is because we started by considering the relations between the entities. So now we have found a solution to the goal: AA = "Pam".parent("Bill". If we try to find more solutions we will find AA = "Jack". CC = "John". CC = "Lisa". CC). Page 16 . here we created a backtrack point to the second father clause. Improving the Family Theory If you continue to work with the family relation above you will probably find out that you have problems with relations like brother and sister. When trying to find additional solutions we backtrack to the last backtrack point. After that we will experience that everything will eventually fail leaving no more backtrack points. Again we create a backtrack point to the second alternative and pursuit the first: ?. So now we have found one more solution to the goal: AA = "Pam". This goal will also succeed with CC being "John".father("Bill". This goal succeeds with CC being "Lisa".

You will use it again and again. which did not exist in the other formulation. Ancestor) :. P1). "male").. parent(P1. person("Pam".parent(Person.parent(Person. . If we follow the principle above. Ancestor) :. parent(P1. Page 17 .Our main entities are persons. This declaration states that a parent is an ancestor. I will choose to have parent as facts and mother and father as rules: parent("Bill". Ancestor) :. in a real scale program this would not be true). Therefore we define a person predicate. ancestor(Person.parent(Person. "John"). Ancestor). P1). Ancestor). Father) :. like this: person("Bill". Ancestor) :. Recursion is however fundamental to Prolog programming. person("John". a definition that is defined in terms of itself. ancestor(P1. parent(P2. Persons also have a sex. "male"). Ancestor) :. But when it comes to "infinite" relations like ancestor we need something more. Instead of using mother and father as facts.e. The first argument of the person predicate is the name and the second is the sex. parent("Pam".parent(Person. Persons have many other properties. father(Person. ancestor(Person. so eventually you will find it completely natural. Ancestor). "male"). The way to overcome this problem is to use a recursive definition. "Bill"). person(Father.parent(Person. Father). Persons have a name (in this simple context will still assume that the name identifies the person. but none of them have any interest in our context. Ancestor).parent(Person. So this theory also has a built-in consistency on this point. like this: ancestor(Person. Recursion Most family relations are easy to construct given the principles above. "female"). and that an ancestor to a parent is also an ancestor. Notice that when father is a "derived" relation like this. ancestor(Person. If you are not already familiar with recursion you might find it tricky (in several senses).. it is impossible to state female fathers. The main problem is that this line of clauses never ends. P2). i. Ancestor). P1). we should define ancestor like this: ancestor(Person.

AA). This succeeds with the solution: AA = "Bill".parent("Bill". ancestor(P1. AA). AA). and then we use the first.so we find P1= "Bill".Let us try to execute an ancestor goal: ?. and then we have to goal: ?.parent("Pam". This gives the following goal ?. ancestor(P1. Here we will again find that "John" is the parent of "Bill". P1). If you pursuit this goal you will find that it will not have any solution. finding the new goal: ?. AA).ancestor("Bill". So now we have found two ancestors of "Pam": "Bill" and "John". This gives the new goal: ?. Then we try to find another solution by using our backtrack point to the second ancestor clause. AA). This gives the goal: ?. AA).ancestor("Pam". Two things are important to remember: Page 18 . Again "Bill" is the parent of "Pam".ancestor("John". We create a backtrack point to the second ancestor clause.parent("Pam". This goal has the gives the solution: AA = "John". and thus that P1 is "John".parent("Bill". Recursion is very powerful but it can also be a bit hard to control. So all in all we can only find two ancestors of "Pam". P1). To solve this goal we first create a backtrack point to the second ancestor clause and then we use the first one. AA). If we use the backtrack point to the second ancestor clause we get the following goal: ?.

Consider the following goal: ?. When running programs in PIE. The following goal will write the found ancestors of "Pam": ?. we will find and write all ancestors.e. and then it will write the value of AA. of course) and then it is written. So. but nevertheless all the solutions we wanted was given as side effects. so the overall effect is that your output and PIE's own output will be mixed. and then we will fail again. There are a few important points to notice here: • The goal itself did not have a single solution. and then the complete goal will fail. This might of course not be desirable. The write call will write the string literal "Ancestor of Pam : ".ancestor("Pam". it has no solutions).ancestor("Pam". write("Ancestor of Pam : ". But then we call fail this will of course fail. fail. it makes no calls to the predicate itself). write("Ancestor of Pam : ". nl(). I. When pursuing this backtrack point.• • the recursion must make progress the recursion must terminate In the code above the first clause ensures that the recursion can terminate. PIE itself writes solutions. nl(). we have ensured that we make some progress in the problem. The first three predicate calls have exactly the same effect as above: an ancestor is found (if such one exists. fail is a predefined call that always fails (i. AA). In the second clause (which is recursive) we have made sure. AA). before making the recursive call. we will find another ancestor (if such one exists) and write that. and eventually there will be no more backtrack points. Therefore we must pursuit a backtrack point if we have any. And so forth. For example Prolog has a number of predefined predicates for reading and writing. A very simple way to avoid PIE's own output is to make sure that the goal has no solutions. The ancestor call will find an ancestor of "Pam" in AA. AA). Side Effects Besides a strict evaluation order Prolog also has side effects. AA). The nl call will shift to a new line in the output.e. that we go one ancestorstep further back. Page 19 . because this clause is not recursive (i.e.

who learns Prolog. In our examples above all the stated predicate are "calculating" predicates. Anybody. If you need to write out. You learned about the execution strategy for Prolog including the notion of failing and backtracking.• Side effects in failing computations are not undone. Perhaps. You have seen facts. rules and goals. They all calculate some family relation. And finally you have been introduced to side effects. because they are not undone even if the current goal does not lead to any solution. Page 20 . this little advice can help you: Separate the "calculating" code from the code that performs input/output. "parents". You have also seen that backtracking can give many results to a single question. But they represent different level of optimism. These points are two sides of the same thing. will sooner or later experience unexpected output coming from failing parts of the program. for example. Conclusion In this tutorial we have looked at some of the basic features of Prolog. while the second is more pessimistic and states that you should be aware about using side effects. create a separate predicate for writing parents and let that predicate call the "calculating" parent predicate. The first optimistically states some possibilities that you can use.

The following screen will appear. GrandFather):father(Father. type the following father("Bill". Click that you understand the program cannot be distributed commercially. When asked if want to register program. select PIE application. "John"). GrandFather). grandFather(Person. select Build. Go to directory containing Visual Prolog Examples. New. select Continue Evaluation. select File. father(Person. At top of page. Father). then Execute.Section 2: A First Example Open Visual Prolog At top of page. "Bill"). You will then see the following screen. father("Pam". On the screen provided. At top of page. select Project Open. open PIE directory. Page 21 .

At top of page, select Engine, Reconsult

At top of page, select File, Consult. Highlight the file you are working on (FILE0 in this case) and click Open - as shown below.

In the Dialog box (open the Dialog box by selecting Window, Dialog type the following father("Sue", "John"). Press Return In the Dialog box type the following father(X,Y). Press return
Page 22

Output for each query is presented below.

Page 23

Section 3: Getting Started
In this tutorial we just want to have a first shot at running Prolog...

Typing in a Prolog program
Firstly, we want to type in a Prolog program and save it in a file, so, using a Text Editor, type in the following program:
likes(mary,food). likes(mary,wine). likes(john,wine). likes(john,mary).

Try to get this exactly as it is - don't add in any extra spaces or punctuation, and don't forget the full-stops: these are very important to Prolog. Also, don't use any capital letters - not even for people's names. Make sure there's at least one fully blank line at the end of the program. Once you have typed this in, save it as intro.pl (Prolog files usually end with ".pl", just as C files end with ".c")

Starting Prolog
Start Prolog at the command prompt; to start GNU Prolog you just type in gprolog. After a while, you should get something like the following on screen:
Copyright (C) 1999-2004 Daniel Diaz | ?-

The Prolog interpreter is now running and waiting for you to type in some commands.

Writing programs in Prolog is a cycle involving 1. 2. 3. 4. Write/Edit the program in a text-editor Save the program in the text editor Tell Prolog to read in the program If Prolog gives you errors, go back to step 1 and fix them

5. Test it - if it doesn't do what you expected, go back to step 1 We've done the first two of these, so now we need to load the program into Prolog.

Page 24

The Rules The program we wrote in the last tutorial was a fairly small one. and running the following queries against it: • • • • likes(john. likes(Y. likes(Y. .Section 4: Facts and Rules Since we've just met facts and rules.X). For the moment. before you change anything!) The difference between facts and rules is that rules are conditional.X). Meaning if and or Open the file in the text editor and try adding in rules to express the following: • • • John likes anything that Mary likes Phrase this as: John likes something if Mary likes something John likes anyone who likes wine Phrase this as: John likes someone if that someone likes wine John likes anyone who likes themselves Do these one at a time. we want to get some practice with using them. we'll just be using three operators in Prolog: Operator :. likes(mary.food). Test your program by loading it into Prolog after each modification.wine). so we won't be adding many rules. and use Prolog's "if" operator. (Do this now. testing the above queries each time The Family Tree Example Page 26 .

sophia). james1).P) is true when C has a parent called P parent(charles1.Suppose that we want to represent a family tree. female(sophia). charles1). % parent(C.. parent(elizabeth. which will describe a family by a series of facts. male(james2). the properties we will want to look at will be father. parent(catherine.pl").. male. and copy and paste the above program into it. sister.. . Start a new file in your text editor (call it "family. mother. We choose three basic predicates.. male(charles2).. female and parent. parent(charles2.". % female(P) is true when P is female female(catherine). male(george1). parent(sophia. Take the following family tree as an example: James I | | +----------------+-----------------+ | | Charles I Elizabeth | | | | +----------+------------+ | | | | | Catherine Charles II James II Sophia | | | George I In Prolog we represent this as: % male(P) is true when P is male male(james1). parent(george1.. or "list all John's sisters" and so on. james1). so that we can ask questions like "is John related to . female(elizabeth). Page 27 . charles1). The basic entities will be people. male(charles1). elizabeth). charles1). brother. parent(james2.

Also. "grandparent". the connection between predicates should be made by sharing variables (and not by embedding one predicate inside another). charles1).We can now formulate some queries (try entering these yourself): • • • Was George I the parent of Charles I? Query: parent(charles1. "cousin" Page 28 . can you add rules for: • • • "sister". "uncle". Who was Charles I's parent? Query: parent(charles1. Who were the children of Charles I? Query: parent(Child. Remember that "and" in Prolog is represented using a comma. If you get this done. "brother". and check the results: • • • M is the mother of P if she is a parent of P and is female F is the father of P if he is a parent of P and is male X is a sibling of Y if they both have the same parent. Parent). "aunt". Try adding the following rules to the program. george1).

"(" . Prolog doesn't really mind how you lay out your code (you can add extra spaces and carriage-returns almost anywhere) with one main exception: • when defining or calling a predicate. Prolog would count the number of arguments. Basically. and reference the appropriate definition. and demonstrate this by looking at how Prolog deals with arithmetic. another common source of error in defining a predicate is putting spaces in the wrong place. The character "%" followed by any sequence of characters up to end of line. when you called one of them. The number given with each predicate is called its arity. you should not put a space between the name of the predicate and the opening bracket .Section 5: Operators and Arithmetic This week we just want to get some more practice with writing and querying knowledge bases. we want to emphasise that Prolog deals with relations and not functions. The symbols "/*" followed by any sequence of characters (including new lines) up to "*/" Simple I/O in Prolog Page 29 . two forms of comment are allowed in Prolog: 1. you may want to comment them for your own reference. Some Prolog Details In this section we want to emphasise a few points. 2. but it might help explain some seemingly strange errors in your input! Spaces While we're on the subject. Thus you could define two totally different predicates with the same name but a different number of "parameters". but different arity. In particular. for example likes/2 in last week's example. The reason Prolog always refers to the arity is that Prolog allows you to have different predicates with the same name. The arity of a predicate is simply the number of arguments it takes. and look a little closer at how Prolog works.which follows it. It's not really a good idea to do this (as it can be confusing). Comments As you write more knowledge bases. some of which you might have come up against in last week's tutorial. Arity You have probably noticed that Prolog's error messages always refer to a predicate name along with a number.

non_zero(N) :. the latter is called prefix). the former is called infix. write them between their arguments). many commonly-used predicates are built in to Prolog.N>0. *.We'll be looking at I/O in a little more detail later.. it is the same as the "==" relation in C. There are ways of making your own infix predicates. prime(5).N<0 . It is thus a completely different term to "1+4". As you might expect. However these do not work exactly as expected! The important point here is to realise that writing "2+3" in Prolog is not an instruction to carry out the addition (remember. Thus if we have the knowledge base: prime(2). instead of having to write them before their arguments. The built-in arithmetical predicates are the obvious ones: <. prime(3).e. or "3+2". exp. >=. A simple example of their use would be the following two predicates: positive(N) :. Arithmetic Operators Prolog also has arithmetic operators like +. but we won't worry about this for the moment. >. and certainly different from "5*1" etc. Prolog is not an imperative language). (for the record. = etc. and we can use these in our programs. =<. -. an important point here is the difference between functions (as in C) and Prolog's relations. Note that Prolog's "=" relation is equality (not assignment). Because these are part of the language we can use them like a normal relation (i. . Rather it represents "the addition of 2 and 3".. but for the moment you should know about the following predicates: • • nl which moves to a new line on screen write(X) which writes X on screen Arithmetic in Prolog In this section we want to look at how Prolog deals with numbers. N>0. Built-In Predicates To date we have been defining our own predicates as we needed them. Page 30 . / and also the usual collection of functions like sqrt. cos.

because the terms they contain cannot be unified with any of those in the knowledge base. In C/C++. the variable used before the is should be unbound. So. we might write a function of the form: Page 31 . X = 3. Y is 2 ** 4. I is I+1. N is X+1. you'd need something like: | ?. It's worth emphasising this point: in general. any variables occurring in the arithmetical expression should have a value. N is 1+1. in the above example.the standard way of doing is to use Prolog's assignment predicate is. Suppose we wanted to define a predicate to calculate the minimum value of two numbers. Only two of these are actually valid queries . and make sure you understand Prolog's response in each case: • • • • • • N is 1+1.make sure you understand why. it's important to remember that in Prolog all "operations" must be represented as relations . After it succeeds.The queries "prime(1+1)" or "prime(5*1)" will both fail. • The predicate "N is E" will succeed whenever N is an unbound variable. Try entering them. P is N*2.this can seem a little strange at first. I is 6. J is I+1.X is sqrt(9). and E is some arithmetic expression (like 2+3). to use one of the built-in arithmetic functions. I is 6. I is I+1." would succeed. N will be assigned the computed value of E. Q is P+Q. Thus. However.0 Z=3 Some queries: Each of the following can be entered as a query to Prolog.14). Defining your own relations The relations positive and non_zero that we defined above represent things which would be regarded as relations in most languages. Z is floor(3. The value of an arithmetic expression is only actually computed when we ask Prolog to compute it . the query "X is 1+1.0 Y = 16. since the is will cause the term 1+1 to be evaluated to 2. prime(X).

Thanks to Boris Glawe for pointing this out.Y..X) :. } This function takes two arguments and returns one value. so this has to be represented as a relation. int y) { if (x < y) return x. Exercises Define predicates to calculate the following: Page 32 .Y.. * Note: In the C version of the min function. since we know that minimum(x.Z) is true if Z is the minimum of X and Y minimum(X.". Thus we note that: • In general. It's a bit like if we insisted that all our functions in C/C++ were to be of type void. int y. The corresponding Prolog expression is: minimum(X. We should read a statement of the form "minimum(X. in C/C++ we might write something like "(minimum(x. thus in C++ we might write*: void minimum(int x.y) > 0)" to test if the minimum of two numbers is positive...X>=Y.y) represents a value. so we might phrase the signature as void minimum(int x. int y. and return their result by pointers or reference. we'd use pointers rather than reference parameters. since applying the predicate minimum to something will not give a value.X) :.X<Y. Note the way that the two alternatives are expressed as separate clauses in Prolog. a function that takes k arguments will be represented in Prolog as a relation that takes k+1 arguments (the last one being used to hold the result) Thus in Prolog we write: % minimum(X. else z = y. In Prolog we don't' have functions. the third argument will be the result. Z>0..Y. The first two arguments to the relation will be the input values. You should be very careful not to do this in Prolog.Y. else return y.Z).Y. int* z). int& z) { if (x < y) z = x." as saying"the minimum of X and Y is X if . } Remember also that these predicates cannot be used in expressions like functions.int minimum(int x. minimum(X.Y) :.

when n>0 fib(0) = 1 (b) The Fibonacci function: fib(1) = 1 fib(n) = fib(n-1)+fib(n-2). 5. the maximum of two numbers the maximum of three numbers the absolute value of a number The following well-known recursive functions: fact(0) = 1 fact(n) = n*fact(n-1).Ack(x. the result of adding 1 to a number the function signum(x) which is x-1 if x>0. and 0 otherwise. 2. 6.y) = y+1 (c) Ackermann's function: Ack(x.y-1)) when x. when n>1 Ack(0.y) = Ack(x-1. 4.1) when x >0 Ack(x.0) = Ack(x-1.y>0 (a) Factorial: Page 33 . 3.1.

but it will be used in almost every nontrivial Prolog program from now on. When you do recursion you must have three things: 1. A similar definition to test if a number is odd would only need to change the base case to refer to 1 rather than 0. *1. and we'll be using it a lot from now on. This is OK to do. Using Recursion In imperative languages like C/C++/Java we deal with situations which require iteration by means of constructs like while. we have n! = n * (n-1)! Note that we define n! in terms of (n-1)!. usually dealing with an empty structure 3. This is really important in Prolog. We can express this in terms of recursion as follows: • • • Data Structure: natural numbers Base Case: 0! = 1 Recursive Case: For any n>0. the factorial of some number n. Basically recursion involves defining something in terms of itself. written n! is n*n-1*n-2* . since we know that (n-1) < n Even: We do not always have to decrease by 1 each time. A recursive case definition.. we use recursion. trees etc. Page 34 . Recursion can take a little time to get used to. Prolog does not use these imperative-style constructs: instead.Section 6: Recursion In this tutorial we simply want to practice using recursion. The key to ensuring that this makes sense is that you always define something in terms of a smaller copy of itself. Some Examples Factorial: By definition. Some set (or "data structure") over which you are doing the recursion: common examples include numbers. Recursion is the algorithmic equivalent of "proof by induction" in maths.. explaining how to work out a non-trivial case in terms of some smaller version of itself. so you should try and work through all of the following. A base case definition.. do. when we need to iterate.. For example. 2. arrays. for and so on. we can define a test to see whether a number is even as follows: • • • Data Structure: natural numbers Base Case: 0 is even Recursive Case: For any n>0 we know that n is even only if n-2 is even.

moreover. and no disc can be placed on top of a smaller one We want to write a Prolog program to solve this. • • • Data Structure: The number of discs to be moved Base Case: One disc .y) = gcd(x.Sequential Search: Suppose we want to search some section of an array A (say between location m and n) to see if an element E is present • • • Data Structure: section of an array Base Case: m>n. write a predicate which gives all the direct ancestors of a person i. otherwise search between m+1 and n. There are only two rules: 1. when x>y gcd(x. posing it as a recursive problem simplifies matters considerably. in which case the answer is "no" Recursive Case: m < n. Page 35 . in which case we say that if A[m]=E then return "yes".y). The discs are all of different sizes.e. Only one disc can be moved at a time 2.y-x). simply move that disc from A to B Recursive Case: To transfer a stack of n discs from A to B. Exercise: 1. when x=y gcd(x-y. when we wish to transfer n discs we assume that we already know how to transfer n-1 discs. (be sure to use recursion!) The Towers of Hanoi This is an old chestnut: A group of over-proud monks in a Hanoi monastery were assigned a task to perform: they had to move 100 discs from one peg to another with the help of a third peg. Going back to the family tree example. when y>x 2. In fact.To transfer a stack consisting of 1 disc from peg A to peg B. Euclid's algorithm to calculate the greatest common divisor of two numbers can be stated as follows: x. grandparents. great-grandparents etc. we suggest that recursion will help us to do this. their parents. do the following: o Transfer the first n-1 discs to some other peg C o Move the last disc on A to B o Transfer the n-1 discs from C to peg B Thus.

inter). assume that it is possible to place an object at the intersection of any two lines.B). % Recursive case .B.B. and try the query: transfer(3.B. we'll just write out the instructions for each move.A. write('Move topmost disc from ').N discs transfer(N. % Transfer topmost N-1 discs from A to I move(A.B.B) :nl. transfer(N.A.B. % Transfer remaining N-1 discs from I to B Type this in (save it as hanoi.I) where: • • • • N is the number of discs to be transferred A is the peg on which the discs are stacked B is the peg we are to move the discs to I is the (empty) intermediate peg to be used for storage Basically. write(B).1 disc transfer(1.A.A. In Prolog.A).peg1. % Move biggest disc from A to B transfer(M. Let's define a predicate that will write out one instruction: % move(A.B) is true if we move the topmost disc from peg A to peg B move(A. write(A). Now to actually do the main work. The Grid Example Imagine a grid consisting of (evenly spaced) horizontal and vertical lines.A.I) :M is N-1. A possible configuration of objects on the grid might be: | | | | | | Page 36 .move(A..A.I. write(' to ').B).I. transfer(M. % Base case ..pl).peg2.I) is true if we can transfer N discs from A to B % using I as an intermediate peg. let's code it in Prolog.I) :.B). we'll define a recursive predicate which will have the form transfer(N.To see that this works. Since our knowledge of I/O is fairly narrow.I) will be satisfied if we can find an algorithm to transfer N discs from A to B using I Thus we define: % transfer(N.B. Suppose also that the lines are potentially infinite in length.

4. describe the position of the objects relative to each other (after all.) Think along the lines of the family tree example: make sure that you separate the facts which describe a given situation. Page 37 . Rather than using absolute co-ordinates (remember .. Now write some rules which will check the following (you might already have expressed some of these as facts): 1. 2. 6. generalise the above so that they return all objects to the right/left or above/below another (using recursion!). 5. from the rules which will work in any situation. 3.it's infinitely large in theory). Prolog is a relational language.| | | | | | ----+------[A]-----[B]------+------[C]------+---| | | | | | | | | | | | | | | | | | ----+------[D]-----[E]-----[F]-----[G]------+---| | | | | | | | | | | | | | | | | | ----+-------+------[H]------+-------+-------+---| | | | | | | | | | | | | | | | | | ----+-------+------[I]------+-------+-------+---| | | | | | | | | | | | Suggest an appropriate format for a Prolog knowledge base that will represent this.. an object is immediately to the right of another an object is immediately to the left of another an object is immediately above another an object is immediately below another an object is exactly between two others. either in a horizontal or vertical direction an object is directly beside another in a diagonal direction Finally.

the person entity might have a number of attributes such as age. Thus.. structures do not need to be declared. Prolog tells the difference between predicates and structures only by seeing where they appear in a clause. Arithmetic "Functions" and Structures You might have noticed that Prolog does not treat structures any differently during unification from the arithmetic functions (like log or cos) that we met in the last tutorial. height. Remember: predicates represent relationships. This is due to the declarative nature of Prolog: log(10) represents an object. age.. . For example. using a structure in Prolog corresponds to an instance of a class in an OO language. attribute ) Note Note that structures look like predicates. This represents an important difference from imperative languages: in Prolog it is important to think of terms like log(10) as structures rather than function-calls when it comes to unification. A simple example of using structures Suppose we want to represent cars with attributes make. The General Form of a Structure A structure has the form: structure-name ( attribute. not a computation. In languages like C we represent this information using structs. In Prolog we use structures. a structure can appear in a clause anywhere a variable or constant would appear: it is another form of term. price. weight. In general. it consists of entities which have a number of different attributes. Page 38 . Structures (just like any other terms) never appear on their own: they must always appear as the argument to some predicate. and thus can be treated like any other object. we can simply use them wherever we want. structures (and other terms) represent objects. in an OO language we'd probably use a class. As with all other terms we have used in Prolog.Section 7: Structures Much of the information that we want to represent in a program is compound.. that is. but they work differently. and so on.

Price)).2. try some queries to make sure you understand what is happening. her/his position in the department (secretary. Type the "car" example above into a Prolog program (called car.has(_.pl. has(mick. car(ford. car(ford.5. 3. car(ford. we might ask: | ?. try adding a "colour" field to the structure. Data on each employee of a company consists of the following: employee's name. car(opel. department in which s/he works.has(Person. Make = ford Price = 2000 yes Exercises 1. car(toyota. e. Page 39 .C) is true if P has a car matching C has(joe. Price=2000 If we only want to get information about some fields we can use Prolog's "don't care" marker . has(mick. car(Make.We might use a three-place structure called car. car(ford. 5000) might represent a 3year-old Ford selling for \$5. Price < 5000.the underscore character ._)). has(joe._. Age.g. Structures of this type could be used in clauses such as: % has(P. | ?. And we can pose queries like: "What kind of Ford does Mick have?" Query: has(mick. 2. Price)) Answer: Age=2.1000)). head.2000)). Also._. Make = toyota Price = 1000 ? .to indicate this.2. If we wanted to know what make of car sold for under 5000. car(ford. Person = joe ? . Person = mick yes The underscore "_" has indicated to Prolog that we aren't fussy about what matches these fields (and that we don't want to know what does).6000)).5000)).000.3.

we should end up with the company director. based on this.use the "min" predicate here. by adding the information that:  All employees with over 5 years service get a bonus of \$5. that is. and make sure to have a special case for the director. The company director is his/her own boss! Write a Prolog database containing the employees' information (make up 5 or 6 entries) . along with its arity is given in each case) o o o o o department/2: Find the department in which some particular person works manager/2: Given a person's name. number of years of service. Write a predicate which. basic_salary/2: Get a person's basic salary real_salary/2: Get a person's real salary. and then their boss' boss and so on.000  No employee (even after bonuses) can earn more than his/her boss . find out who's the manager of the department in which they work valid_employee/1: Your list of facts should ideally form a tree. Page 40 .. when given a person's name. will check if this is so.). basic salary.accountant etc.this should be a list of facts containing "employee-details" structures.. and the name of their immediate boss. make up some rules to answer the following: (the name of the rule. Now. if we get a person's boss.

then add Elem to the right subtree Try running the following queries: o o o tree_insert(nil. and Elem is less than the element stored at the current node.7.T2)..o o If the tree isn't empty. Notice how lop-sided the last tree is . tree_insert(T2. tree_insert(nil.T1).T2). tree_insert(T2. tree_insert(nil. and Elem is greater than the element stored at the current node.T1). tree_insert(T3. tree_insert(T1.T3).T3).4.T4).e.4. tree_insert(T3.4.7.5.T3). Write a program that gets the height of the tree..5. the maximum length of any path from the root to a leaf.2. then add Elem to the left subtree If the tree isn't empty.2. tree_insert(T2. i. tree_insert(T1. tree_insert(T1. 2.T2).T4).clearly the structure of the tree depends on the sequence in which we insert its elements. Write a predicate that gets the sum of all the elements on the tree 4.5.T4). tree_insert(T3. Page 43 . Write a predicate that calls write/1 for each element stored on the tree.7.5.T1). so that it prints out all elements in order 3.

Every non-empty list can be separated into two parts: • • the head. pat] is a list with three elements. In fact. mary. This is the list which contains no elements. As with any term. Thus [john. they must only appear in a clause as arguments to a predicate. We write a list in Prolog using the brackets "[" and "]". Thus the list [john. mary. X] is also a valid list. like anything else which represents objects in Prolog. pat] is [mary. Remember that lists. we just use them when needed. written "[ ]". lists are Prolog's other built-in data type. a list element may be any kind of term: that is. and separate the elements by commas. a constant. Page 44 . which is the first element the tail.Section 9: Introducing Lists We have already met structures. pat]. pat] is john The tail of [john. or even another list. mary.pat]]. In Prolog we have a special notation just for dividing up lists: • [Hd | Tl] denotes the list whose head is Hd and whose tail is (the list) Tl. Empty and Non-Empty Lists There is one special unique list in Prolog called the empty list. mary. they correspond (roughly) to vectors in C++/Java. extendable sequence of terms. 6. Format of Lists A list is simply an ordered. structure. are terms. pat] can also be written as [john | [mary. mary. List elements do not all have to look the same: ['string'. which is the list containing all the other elements Thus: The head of [john. variable. Thus we don't need to "declare" them. It is not valid to try and get the head or tail of the empty list.

size([H|T]. and so we can write the full list as: [john | [mary | [pat | []]]] This type of division is used in predicates which process lists.N1). thus [pat] is the same as [pat | []]. We can write: % size(List.N) meaning "the size of list L is N" (by size we mean the number of elements it contains). pat] is also a list with head mary and tail [pat] (a one-element list).Since [mary.0). perform some action on the head H..N) :.size(T. Page 45 . we can also write the above list as: [john | [mary | [pat]]] Any one-element list can be written as that element joined to the empty list. then call the predicate recursively with the tail T The length of a list Suppose we wanted to write a predicate size(L.N) is true if List has N elements size([]. we note that [] can never be the same as a list of the form [H| T] (for any element H and list T). To paraphrase: • • The size of the empty list is 0. Some Examples Almost all predicates which use lists are recursive. these take advantage of the unification rules for lists: • • The only term that unifies with [] is [] A list of the form [H1|T1] will only unify with a list of the form [H2|T2]. The size of the list whose head is H and whose tail is the list T is: 1 + (the size of T). they are defined for: • • The base case: the empty list [] The recursive case: for a list of the form [H|T].. The size of the list is exactly equal to the number of times we can perform the head/tail division before we get the empty list. and try it on some examples. N is N1+1. Type in this definition. and then only if H1 unifies with H2 and T1 unifies with T2 As a consequence of these rules.

Define Prolog predicates for the following: 1.[X|_]). Note that we did not have to define a predicate for the case where the list was empty.T). N is N1+H. contains will fail if the list is empty). List) is true if List contains Elem contains(X.2]) contains(E. average(L. Type in the contains predicate. and try entering the following queries: • • • • contains(2.3]) contains(E. This will be a little like the size/2 predicate. because this case could never be true.N) is true if N is the average of all the numbers in L. List Membership Similarly we can define the predicate contains(X.3]) contains(E.contains(X. []) Exercises Let L be any list of terms. X is a member of the list whose head is anything and whose tail is T if X is a member of T.L) which is true if X is an element of the list L. or just 0 if the sum is 0 Page 46 .. except now at each stage we want to add in the current element to the total.2. or X is in the tail of L.. [2. Thus we write: % contains(Elem.Summing a list Suppose we know that a list contains only numbers. In other words: • • X is a member if the list whose head-element is X (and whose tail is anything). Thus we write: % sumlist(List. we should then be able to write a predicate that will get the sum of those numbers. (That is.sumlist(T.0).2.1.N1).N) :. sumlist([H|T]. [1. We observe that X is contained in L if • • X is the head of L.[_|T]) :. contains(X. N) is true if the elements of List sum to N sumlist([]. [1.

N) is true if N is the sum of the squares of all the numbers in L maxlist(L. maxpos(L.N) is true if N is the position of the largest element in the list L. 3. final(L.N) is true if N is the sum of all the positive numbers in L sumsquare(L. up to the end of the list (Use write/1 to print out the elements. evenpos(L) which prints out the elements of L at positions 2. 4..) 6.6.2.4. 5.N) is true if N is the largest element in the list L. sumpos(L. (If there's more than one occurrence of the maximum.. then this should be the first position at which it appears.) Page 47 .E) is true if E is the final element in L 7.

If we try running this we would get something like: | ?. N1 is N-1. We should work it out int he usual recursive manner: • • • Base Case: If the number entered is just 0. collect_to(N1. the process will still use the standard "[H|T]" notation that we have been using. However. N1 is N-1. nl.prints out all the numbers down from N to 0 print_to(0) :. print_to(N1). L=[N|T]. and L was the list containing the answer. say N. since now we want to build a list as we iterate.T). then the answer will be just [0].[]). the more common way of writing this predicate would be: new_collect_to(0.N>0. We might write: % print_to(N) .L) :. 5 4 3 2 1 0 Now suppose we wanted to take these numbers and process them in some other part of the program. and printed out all the numbers between it and 0.write(0).print_to(5). but as you get used to lists in Prolog you'll find ways to take advantage of its pattern-matching. print_to(N) :.N>0. the code looks like: collect_to(N.L) :. The above solution is correct.L) where N was the input number. rather than take one apart. • • Page 48 . new_collect_to(N.Section 10: Lists as Accumulators In the previous tutorial we have concentrated on moving through lists and processing their elements in the usual head/tail fashion. This will be slightly different to the other list predicates. so we write: collect_to(0. write(N). to do this we would have to store them somewhere .[N|T]) :. then we can assume that we know how to collect all the numbers up to N-1 (thanks to recursion) so we just need to know how to add on the extra bit of information about the current element. new_collect_to(N1. Thus we'd want a predicate of the form collect_to(N.the natural choice is to use a list. Collecting information Suppose we wanted to write a predicate that took a single argument.T).N>0. In this section we want to look at predicates that build new lists.L=[]. N1 is N-1. Recursive Case: If we're dealing with a number.

[3. If we consider the possibilities for L1 1. join_list(X.T3). One rather bad way of doing this would be: % bad_reverse(L1.4]. join_list(X. L2.[6.6]). Presumably the predicate will be of the form reverse(L1. L2) :bad_reverse(T. L2).L2. The problem with this is that it works rather inefficiently .L2. and that they both do the same thing! If the second. L1 is of the form [H1 | T1]. If we are to append L2 on to the end of this we will get a list whose head is still H1.7].L2.6]).2]. in which case L3 is just L2 2. the predicate join_list(L1. join_list(T1.a bad implementation of list reversal bad_reverse([].6]. join_list([3. L3=[H1|T3]. Since we know that Prolog will do unification when it matches parameters against arguments. join_list(L1.L2).4.NT). append(NT.[H].L3) :.the second predicate goes through the tail once to reverse it (putting the result into NT). and try the following queries: • • • • join_list([1.L2. Y. Type in the join_list predicate.L3). Page 49 . [H1|L3]) :. L3=L2.L1=[].L1=[H1|T1].5.2]). bad_reverse([H|T]. join_list([H1|T1].[1.L2).join_list(T1. L1 is the empty list. Reversing a List Another good example of accumulating results in a list is a predicate to reverse a list. but whose tail is the result of appending T1 and L2 Thus an initial attempt might be: join_list(L1. a simpler (but equivalent) solution would be: join_list([].L3) means "if we join L1 and L2 we get L3". Prolog has a built-in version of this predicate called append/3.You should try both of these to make sure that they work. L2. where L2 is just L1 backward. and then again in order to stick H onto the end.[]). [3.L3) :.X).L2) .Y. Joining two lists We can write a predicate to join two lists together. more compact version doesn't seem so natural. then you can stick to the first (longer) method of defining this kind of predicate for the moment. [5.5.L2.

[].If we think about the problem for a while. pr_reverse([Head|Tail]. pr_reverse(List. Output=~q". SoFar. and so are different from the first one (which only has two). there's no real way of doing this with just two lists. Make sure that you understand this example . Reversed) :format("\nInput=~q. Reversed) :pr_reverse(List. ?Reversed) % is true when Reversed is has the same element as List but in a reversed % order.2. we can just copy this to the output list.Reversed. Reversed). for example.. Intermediate=~q. and the output list).Reversed]).[[Head|Tail]. I've called this good_reverse/2 to stop it clashing with the built-in reverse/2 predicate. List must be a proper list. SoFar. good_reverse([]. Reversed) :format("\nInput=~q.3] [3] [] Output -----[] [1] [2. In the Prolog library. Reversed).3] [2.[[]. Reversed).try running the following version (which prints out what it's doing) with some queries. []. List must be a proper list. ?Reversed) % is true when Reversed is has the same element as List but in a reversed % order. Reversed. % pr_reverse(?List.1] Unfortunately. Output=~q". we can see that we need to go through L1. What we need to do is to mimic the "Towers of Hanoi" example a little. Page 50 . When we're done. pr_reverse([]. good_reverse(List. and put each element that we met into L2. and then copies the intermediate list to the output list. and this then calls the three-argument version with the empty list as the starting point for the intermediate storage. Reversed) :good_reverse(Tail.2. What happens here is that the user calls the first predicate.SoFar.. there's an implementation of this as follows: % myreverse(?List. Intermediate=~q.2. good_reverse/3 then copies the first list into the intermediate until it's empty. Reversed). Reversed. an intermediate list. The last two predicates above actually have three arguments (the input list. good_reverse([Head|Tail]. Reversed) :good_reverse(List.3] should go something like: Input ----[1.1] [3. and use an intermediate list to store the answer that we're creating. [Head|SoFar]. reversing the list [1.Reversed]).

call split(T. sort T1 and T2. evens(L1.L2) which is true if L2 has the smallest number in L1 as its head. ?integer). but also to their "mode". Exercises 1. for example length(?list. and L3 contains those elements of L1 greater than N. You might notice the format of the definitions. Use the last predicate to implement a quicksort as follows: 1.N. and then append these along with H (in the middle) together to form the answer. Sorting the empty list gives you the empty list 2. (This is a lot like the ordered binary trees example.T1.T2).L2) which is true if L2 contains just those elements in L1 which are even in the same order 2.L2) which is true if L2 contains just the first N elements of L1 3.L2) which is true if L2 is L1 with the last element removed 2. and all the other numbers in the same order 3.H.N.L2. cutlast(L1. To sort a list of the form [H|T]. Use recursion and the last predicate to implement a predicate that sorts a list by iteratively moving the smallest element to the head. Reversed).L3) which is true if L2 contains those elements of L1 less than or equal to N. Here. This not only gives a hint as to the expected type of the arguments to the predicate. Write a predicate split(L1. 4. Built-In list predicates Many of the predicates that you will most commonly use when working with lists (such as those in the previous section) are built-in to Prolog.) 5. The notation is pretty standard: Page 51 . format/2 is a built-in printing predicate that works a little like printf in C or Java. Write a predicate beg_small(L1.pr_reverse(Tail. trim(L1. [Head|SoFar]. then the next smallest to the second position and so on. Write predicates for the following: 1.

weekend(Day). and goes on to try to satisfy weekend(friday) which fails.may1).. weekend(friday). it would have backtracked to the last choice point.. !.holiday(Day.. weekend(When). picnic(Day) :. With the same query Prolog proceeds as before.weather(Day.holiday(Day... This time we go on to process: weekend(friday) which fails. The first rule for weather is: weather(friday.fair). and so we go back to the last choice point without meeting the cut.. Now when we pose the query: Picnic(When) Prolog will try to satisfy the sub-goal: weather(When. picnic(Day) :.. !.The First Cut Now change the definition of picnic to the following: picnic(Day) :. !. Prolog passes the cut.. weekend(friday).may1).. (Check that this is so.fair). so the new sub-goal becomes: .fair). Since we also have: Page 54 .fair) But now the presence of the cut stops it going back. Previously..weather(Day. and gone on with processing weather(saturday. weekend(Day). so it is trapped between the cut and the end of the (failed) predicate.) Another Cut Change the definition of picnic for a second time to get: picnic(Day) :. !... !.fair). until it gets to the sub-goal: . The answer now is simply: No.

p(a). Assume that we have a Prolog program with the following facts: 2. and ultimately get: When = saturday. change the definition of picnic once more.may1). it cannot go back. Since there is a successful answer. r(1. (Check this. and so it will not return any extra answers. which was for the goal: weather(Day.. Exercises 1. because it has met the cut. However. and Prolog puts down the "no going back" marker.. which we can't do.fair)..weather(saturday. picnic(Day) :.fair) fits.fair). We backtrack to the last choice point.1). and so we try to satisfy: weekend(friday) which fails. This time the whole goal succeeds.1). we are free to consider the alternatives.5).!. This time when we ask picnic(When) the first thing we do is to process the cut.. weekend(Day).. Page 55 . the new sub-goal becomes: . Prolog prints out: When = saturday. r(3. When = sunday. q(a. weekend(saturday).fair) Since we can get back here without passing the cut. Thus there are only two solutions in this case. Note that the second attempt to get the answer friday never happens.holiday(Day.) Yet Another Cut Finally. and Prolog processes the cut... !. because getting to the goal for this would involve crossing the cut. to get: picnic(Day) :. As before weather(friday. weather(Day. Any solutions we get from now on have to come from between the "!" and the end of the clause.

r(Y. r(Y.Y). 8. a number. r(Y. p(X). insert(X.Y). 5.Y.Y).7). r(3. insert(X.Y.Z).2). p(X). p(X). 4. q(X. r(2.4). q(X. r(4. r(4. Provide an appropriate query to show that this program is incorrect 2.3. a sorted list.[H|T]. !.8). Provide an appropriate query to show that this program is incorrect (try using all constant arguments) 2. p(b). q(b.3). What are the results of running the following queries? 1. 6. 6.[H|T1]) :. giving the third argument (also a sorted list): 10. max(X. 1.Z). !. !.Y).Z). insert(X. 11.Z).6).T1). p(X).4). max(X.T. 4. r(1. q(a. Consider the following program which is intended to define the third argument to be the maximum of the first two numeric arguments: 7.X) :. Change the program so that it works correctly Page 56 . q(X.Y). q(X. !. r(Y.X>H.X >= Y. !. 1. q(X.[X|L]). !. q(b. 2. r(Y.Y).2). 5. Change the program so that it works correctly 9.Z). into its second argument. r(2.3). Consider the following program which is supposed to insert its first argument. p(X).L. 3.

it also makes them more difficult to understand. they do this by eliminating some of the possibilities that might be considered. Negation as Failure If we ask Prolog to satisfy some goal P. fail.Section 12: More Control Features The cut predicate has a number of associated predicates. Note that if we left out the cut here then Q would always be satisfied. We can do this using a combination of cut and another built-in predicate. all of which deal with changing the way Prolog goes about solving goals. In general we distinguish two types of cut: Green cuts These are cuts which are introduced simply to make the program more efficient by eliminating what the programmer knows to be useless computations. Thus to say "q is true if p isn't". Red cuts These cuts are introduced to make the program run in a different way. !. we might write: q :. q. thus we might write: Page 57 . since the second case would be reached after the first failed. Prolog has a built-in shorthand for this: the meta-predicate "\+". which always fails. Thus they change the logical meaning of the program.p. Use these sparingly! Kinds of cut While using the cut can make programs shorter or more efficient. Green cuts are useful for speeding up computations. and Prolog responds no. In certain situations we will want to define predicates in terms of the negation of other predicates. fail. we take this as meaning that P cannot be satisfied. They do not remove any extra solutions! Running a program without green cuts should still give the same answer. even though it may take a little longer to do so. and less "logical" in nature. red cuts should be avoided where possible.

\+(out(X)). % Q is true whenever P fails.X=Y. out(sue). and then try them in Prolog: • • • Is Sue at home? Is John at home? Is anyone at home? The apparent contradiction is caused by Prolog's closed-world assumption. suppose we wanted to write a predicate to add an element to a list. !. For example. if something can't be proved true. Prolog has a shorthand for this built-in. An example of using this would be the following predicate which will be satisfied if X and Y cannot be unified.p -> q . work out what is the logically correct answer to the following queries. Suppose we want to define some predicate S which should be of the form: "if P then Q else R" We can define this in Prolog as: s :. !. fail.q :. If-then-else in Prolog One common use of the cut predicate is to mimic the "if-then-else" construct found in imperative languages. q. As with any Prolog program involving the cut. we might just write: add(Elem. Now.[Elem|List]). different(X...r.List. r.Y) :.Y). Suppose now that we want to change this predicate so that no duplicates are added to the list.\+(p). different(X. Warning! This way of implementing what is effectively the predicate "not" is called negation as failure. that is. it must be false. you should be very careful when using it! An example of where negation as failure can give unexpected results is the following predicate: home(X) :.p. s :. we need only write: s :. it is not proper negation. Prolog assumes it always has all relevant information: hence. we might write: Page 58 .