Programming in Prolog: Using the ISO Standard [Paperback]

Pros:
- Even someone with no programming or math knowledge could pick up the book, read it, and learn Prolog
- Uses ISO-Prolog
- Large section of helpful example programs

Big Cons:
(I'll give citations, only from the first 100 pages to keep things short, lest anyone think I am lying about the problems with the book)
- Frequent syntax errors *in program statements* - in Prolog, every comma and period is absolutely essential, when they are missing it entirely changes the meaning of the statement - the book misses them pretty routinely (p 81, twice)
- Frequent logic errors - in Prolog, the order of facts and rules is extremely important. The book commonly mixes things up, presenting you with programs that will not work (p 56 - note here that they are trying to give an example of what will/won't work, and they get it backwards)
- Frequent editing/formatting errors - charts, diagrams etc are fairly often on the wrong page or in the wrong location, etc. (p 48)
- Poor organization - looking through the table of contents, you would think the book is extremely well organized, but as you read it, you'll find new and important ideas thrown into random sections - if you forget something, and need to find it later, you'll probably need to re-skim the entire book. Things are almost never presented in convenient bullets/numbering, almost always in paragraph form, again, making essential ideas tedious to find.
- Confusing - I have degrees in math and computer science, and have been programming for 15 years, and I still found parts of the book hard to follow - note that it had nothing to do with Prolog itself, which is actually very straightforward, but rather with the explanations given, which sometimes seem meandering and poorly worded.
- A really short and crummy index makes things hard to find. For example, look up "atoms", a concept first mentioned on page 26, and routinely mentioned afterwards, a concept absolutely essential to understanding Prolog - the index shows that the first (and only) time it appears is on page 123.

Average Cons:
- Authors use an "arrow system" to trace Prolog decision making, I think a table system (which could easily show previous, current, and future steps, and details of each iteration) would have been better while presenting more information in a clearer fashion.
- Code re-use - normally a good thing, frustrating in this book. You might have a rule (like a function) called "mother(X)..." early on in the book, not use it for 100 pages, and then it appears again. If you want to try the program out yourself, you'll need to know the exact definition of "mother(X)...". There's no way to find what page the function was on in the index or TOC, so you find yourself spending 30 minutes leafing through the book to find it. 99% of these are a single line of code, so there's really no need to reuse them, it's hardly saving any space.
- Overly complex examples - sometimes the authors illustrate an idea with 20 lines of code, when 4 would have been sufficient. It makes for a lot of extra reading and deciphering.

Small Cons:
- (This could be a pro or con - since I don't know too many people who *start* their programming experience with Prolog, I assume the reader has some experience with programming, and so list this as a con) Book is far too detailed for someone with moderate programming or math experience. This helps some people, but makes it a tedious read for others. Every concept is thoroughly explained. If you're a programmer, this gets a little old during things like variables and recursion. If you know any math, verbose explanations of predicate logic will become tiresome. In fairness, it was no doubt the authors' intention to make a "complete" introduction to Prolog, and so it is hard to criticize this.
- (Another pro/con, depending on the reader) British examples - the authors are British (or at least one of them is), and use British references in their code all the time (9th century princes of Wales, p 34; horses who won races in Britain in 1927, p 53) - if you're British this might break up the monotony and make things a little more interesting, if you're not, it just gets a little old, I'd rather see every example just use "cat","dog","mouse".

Other:
- NOT a good reference book (and it wasn't meant to be), if you know Prolog already and need a reference book, look elsewhere. This is for people who do not know Prolog.

Conclusion:
- I wish I bought a different book. BUT despite everything, I did adequately learn Prolog from this book, so will reluctantly give it 3 stars.

Prolog is a complex subject, especially for someone not well familiar with mathematical logic. Thus, it is very important how the foundation would be laid down. Typically the books I had read on Prolog tend to two extremes. They are either too condensed for such a complicated subject as logical programming, or too broad and mathematically intensive. I would put this book into the first category. Though very concise and well structured, this book does not seem to be a good primer. I would rather recommend the book of Ivan Bratko "Prolog Programming for Artificial Intelligence (International Computer Science Series)" 2nd edition (the third edition of this book is due in August 2000). Ivan Bratko had managed to find the optimal style of presenting both the essence and the practical aspects of the language. Bratko's book covers various practical applications of the language and manages to convey the basic concepts of Prolog without overwhelming the beginner with too abstract or too condensed passages.

Nevertheless, "Programming in Prolog" could be a very good programming reference once you are relatively comfortable with the language.

This is an extreme valuable book on the Prolog programming language that every computer science person should own. Prolog itself is actually a fairly simple language to learn, albeit slightly obscure. It's reputation for complexity comes from its non-standard implementation, but if you don't enter into it expecting it to look and behave like other languages then you should be all right. Once you get past the mathematics and logic, you should be able to get your mind working in that particular direction. This book is a very handy guide for getting the programmer into the Prolog mindset as well as bringing one up to speed on all the (sometimes very confused) syntax.

This book, like Prolog itself, is not for the beginning programmer. If you have a good background in logic or mathematics, then you should find this book to be very rewarding.