# 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

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

Edinburgh syntax is the basis of ISO standard. 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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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. and running the following queries against it: • • • • likes(john.Section 4: Facts and Rules Since we've just met facts and rules. likes(Y. likes(Y. testing the above queries each time The Family Tree Example Page 26 . The Rules The program we wrote in the last tutorial was a fairly small one. and use Prolog's "if" operator. likes(mary. (Do this now. Test your program by loading it into Prolog after each modification. so we won't be adding many rules.food).X).X). . we want to get some practice with using them. before you change anything!) The difference between facts and rules is that rules are conditional. For the moment. we'll just be using three operators in Prolog: Operator :.wine).

and copy and paste the above program into it. parent(charles2.. male. female and parent. Start a new file in your text editor (call it "family.. 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(james2. The basic entities will be people. which will describe a family by a series of facts. . % female(P) is true when P is female female(catherine). parent(catherine. male(george1). james1). female(sophia). brother. parent(george1. % parent(C.. male(charles1).". We choose three basic predicates. male(charles2). james1). or "list all John's sisters" and so on. charles1). charles1). parent(elizabeth.. Page 27 . mother. female(elizabeth). sophia). sister. elizabeth). so that we can ask questions like "is John related to .. male(james2). parent(sophia..pl").Suppose that we want to represent a family tree. charles1).P) is true when C has a parent called P parent(charles1. the properties we will want to look at will be father.

Remember that "and" in Prolog is represented using a comma. "uncle". Parent). charles1). 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. Try adding the following rules to the program. If you get this done. Also. the connection between predicates should be made by sharing variables (and not by embedding one predicate inside another). george1). Who was Charles I's parent? Query: parent(charles1. "grandparent". can you add rules for: • • • "sister".We can now formulate some queries (try entering these yourself): • • • Was George I the parent of Charles I? Query: parent(charles1. "brother". "cousin" Page 28 . Who were the children of Charles I? Query: parent(Child. "aunt".

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

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

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

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

and 0 otherwise. when n>0 fib(0) = 1 (b) The Fibonacci function: fib(1) = 1 fib(n) = fib(n-1)+fib(n-2).y) = y+1 (c) Ackermann's function: Ack(x. 5.y-1)) when x. 4. 6.Ack(x. the result of adding 1 to a number the function signum(x) which is x-1 if x>0. 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). when n>1 Ack(0. 3. 2.0) = Ack(x-1.y>0 (a) Factorial: Page 33 .1) when x >0 Ack(x.y) = Ack(x-1.1.

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

simply move that disc from A to B Recursive Case: To transfer a stack of n discs from A to B. when x>y gcd(x. grandparents. write a predicate which gives all the direct ancestors of a person i. Going back to the family tree example. in which case we say that if A[m]=E then return "yes". moreover. we suggest that recursion will help us to do this. Page 35 .e. • • • Data Structure: The number of discs to be moved Base Case: One disc . their parents. Euclid's algorithm to calculate the greatest common divisor of two numbers can be stated as follows: x. great-grandparents etc. when we wish to transfer n discs we assume that we already know how to transfer n-1 discs. There are only two rules: 1. In fact. otherwise search between m+1 and n.y-x). 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.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. The discs are all of different sizes.y). (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. in which case the answer is "no" Recursive Case: m < n.To transfer a stack consisting of 1 disc from peg A to peg B. and no disc can be placed on top of a smaller one We want to write a Prolog program to solve this. Only one disc can be moved at a time 2. posing it as a recursive problem simplifies matters considerably. Exercise: 1. when x=y gcd(x-y. when y>x 2.

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

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

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

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

basic salary. if we get a person's boss. based on this.use the "min" predicate here. that is. Page 40 .. and then their boss' boss and so on. number of years of service. 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..accountant etc. and the name of their immediate boss.). and make sure to have a special case for the director. Now.this should be a list of facts containing "employee-details" structures. when given a person's name. by adding the information that:  All employees with over 5 years service get a bonus of \$5. Write a predicate which. we should end up with the company director. will check if this is so. The company director is his/her own boss! Write a Prolog database containing the employees' information (make up 5 or 6 entries) . 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. basic_salary/2: Get a person's basic salary real_salary/2: Get a person's real salary.000  No employee (even after bonuses) can earn more than his/her boss . make up some rules to answer the following: (the name of the rule.

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

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

We can write: % size(List. and try it on some examples.N1). size([H|T].Since [mary. then call the predicate recursively with the tail T The length of a list Suppose we wanted to write a predicate size(L.size(T. perform some action on the head H.N) meaning "the size of list L is N" (by size we mean the number of elements it contains). 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.0).N) is true if List has N elements size([]. 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].. Page 45 . they are defined for: • • The base case: the empty list [] The recursive case: for a list of the form [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. Some Examples Almost all predicates which use lists are recursive.. To paraphrase: • • The size of the empty list is 0. thus [pat] is the same as [pat | []]. The size of the list whose head is H and whose tail is the list T is: 1 + (the size of T). and then only if H1 unifies with H2 and T1 unifies with T2 As a consequence of these rules. Type in this definition. 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. pat] is also a list with head mary and tail [pat] (a one-element list).N) :. N is N1+1. we note that [] can never be the same as a list of the form [H| T] (for any element H and list T).

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

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

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

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

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

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

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

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

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

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

X=Y.q :.p -> q . Now. s :.Y). 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. it is not proper negation. % Q is true whenever P fails. work out what is the logically correct answer to the following queries. fail. q. we might just write: add(Elem. If-then-else in Prolog One common use of the cut predicate is to mimic the "if-then-else" construct found in imperative languages. !. An example of using this would be the following predicate which will be satisfied if X and Y cannot be unified.. different(X. For example.List. we might write: Page 58 .[Elem|List]).. out(sue). !. we need only write: s :. suppose we wanted to write a predicate to add an element to a list. Suppose now that we want to change this predicate so that no duplicates are added to the list. Prolog assumes it always has all relevant information: hence.\+(out(X)).Y) :. Prolog has a shorthand for this built-in.\+(p). that is. 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) :. different(X. it must be false. if something can't be proved true.r. 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 :.p. r. Warning! This way of implementing what is effectively the predicate "not" is called negation as failure. As with any Prolog program involving the cut.