As the instructor of "Practical Object-Oriented Programming" (a 5-week course that uses Dylan that teaches object/functional application in the software domain), I chose _Dylan Programming_ as the text book. It is well-suited to the methodology of teaching programming: the chapters can be comprehended by people with no programming background (I had two such students), yet the material is stimulating so that even experienced programmers find it useful. Married with the Functional Developer (a Dylan IDE), _Dylan Programming_ makes teaching, or learning, Dylan quick and easy.

I have three points where I find the book wanting: organization, exactness/correctness, and completeness.

I found the book's organization a bit puzzling: especially when it came to control structures. In my teaching sessions, I needed to move forward 11.1-11.5 (skipping parts of 11.3 and all of 11.4) before I covered chapter 4 (classes). Also, interspersing the airport example seemed random at times, particularly in the second half of the book. I chose to skip those chapters (for teaching purposes).

The book was incorrect for several of its page references. This was particularly annoying as it happened that I followed a reference on several occasions, only to be led to the wrong page. For example, page 182 (center) refers one to page 172 for the definition of sum (a function), this function actually appears on page 174. Page 183 (center) refers one to page 147 for the use of curry ... this example is actually at the end of page 148. Page 183 (center), again, refers one to page 181 for the use of the function choose, which is not mentioned until page 182 ... and on, and on, and on. Some references were so obscure that I could not find what these references meant on any page near the page they mentioned. Chasing referred pages, then, became a tiresome venture that often disappointed.

As for completeness, I mentioned in the previous paragraph the function choose, a very useful function. However, if one looks in the index, no mention, anywhere, is made of it. The authors took pains to highlight it in the text, explain it, and provide an example. This exact problem exists also for the function apply, another very useful function. _Dylan Programming_ falls down in the index for generalities as well as specifics, as we've seen: no entry exists for first-, or higher-, order functions. Also, the index entries for protocol and efficiency point to one line definitions in introductory sections, where their explanations occur much later in those chapters.

Even though the index has some faults, the references are off at times (too often, unfortunately), and I disagree with the book's presentation of fundamental topics too late, the book shines overall, and shines primarily that it teaches Dylan well.

First, some of the book's explanations surpass those of the _Dylan Reference Manual_ (DRM). It used illustrations, code examples, and metaphors repeatedly to get the point of the section across. Not only that, but it went in depth on some topics where the DRM chose terseness: for example, _Dylan Programming_ has explained modules as namespaces very well. Accompanying many sections were interactive examples in a Dylan listener so that the reader could try out the topic's techniques as they read.

Second, the book unifies the presentation of the language very well. The DRM is excellent at examining language features piece by piece; _Dylan Programming_ is excellent at putting these pieces together at the chapter level. They even have a bulleted chapter summary of the topics covered.

And, third, the book succeeds in a practical way. All of my students were new to Dylan (some new to programming), yet each completed their final project assignments, due in large part to the help this book gave them. One programming neophyte created a final project that computed the possible blood types of a child from known parents' blood types (a relatively simple task), but then created a blood type inference system that postulated a blood type of a parent based on one parent's and the child's blood type ... a more significant achievement. Another created a mathematical symbolic processor (it found, among other things, the roots of quadratic equations).

Overall, then, this book has some minor shortcomings. As a book to learn Dylan, though, it is without peer, and I strongly recommend it as the first book from which to learn the language.

While primarily aimed at people just learning Dylan, this book has some great info for people who already understand Dylan reasonably well (the chapter on performance is especially valuable.) The book is well written, and the information in the book is very accurate.

The book does not attempt to cover all the standard Dylan functions and classes, and thus it does not intend to replace the Dylan Reference Manual (DRM). I often find myself using this book as a reference for language features though.

I think this is one of the better programming books I've seen, in that it is task-oriented. The authors have a goal of building a program to do airport scheduling; while they are building this program, they are teaching you Dylan. Consequently, you are learning how to do a real-world task (well, at least someone's real world task) rather than just a bunch of example programs that don't correlate well or at all. Along the way, they are teaching you how to build classes and methods effectively, which is sadly lacking in most other programming tomes.

The only thing that I considered a "problem" is that it took them until chapter 11 to start discussing control structures (like the loops and decision statements). My attention was wandering and I had to skip ahead to keep my interest.

It also seems to be oriented towards people who are already familiar with C++ or Java (or some other object-oriented language), which is probably not a bad assumption. I can't imagine someone picking this up as their first language, but it is just a word of warning, just in case.

In summary, very, very good book. Don't make the mistake of getting the Dylan Reference Manual as a way to learn Dylan -- "Dylan Programming" is the book to get for learning the language.

This book was a little too cliched. It's set in the 1700s, where a lot of novels are set, and the story was a repeat of many romances I have read. Also, the love scenes are at least a chapter long, which I think just wastes space. We really don't want to know that much about Sassy and Roarke's intimate moments. I wouldn't really recommend this book, but everyone's entitled to their opinion.

Sassy Adair is a spirited heroine--full of life and courage. And what can't you say about Roarke MacLaren? Bold, spirited and a real man--not one of those little boy types that substitutes for a man nowdays. I loved the book, especially the portions featuring the Scottish highlands!

This is a great book for teens that have spina bifida or their sibs. It explains things that can be confusing.

I recommend this book not only for teens, but parents, because it explains spina bifida in very easy to understand terms, and can help parents of younger kids think about things they can do now to help their children grow into independent adults.

This book is the sequel to Texas Tigress. There is yet a third, titled Love's Lost Angel. The first book in this trilogy, T.T. is the best. The characters are very real, with emotions strongly expressed. Hope she writes another one about the Sundance Saga!

This is a sequel and it picks up exactly where Awake Savage Heart leaves off. The Minnesota Legend at the beginning is enchanting and the little boy--the hero and heroine's son--sets off the story on an intriguing note. Also, the secondary characters, Kristel and Cat-Face were fun to follow in their own "sub-plot" romance. The story was sweet and whimsical, with a touch of mystery and intrigue at the end. But I didn't find any mention of kerosene!

This is a perfect introduction to feminist theories. It covers how these theories have affected the past and allows the reader to conclude how they will affect us in the future.

my friends and myself thought it was a crowning glory of a romance. The blurb on the back page tells it all: They were as different as fire aand ice--shy, demure Anna Lou Mayhugh and brashly passionaate Max Butler. The only two things they shared were the wall between their thriving emporiums in River City, Iowa and the bitter vow that each had made--a vow never to love again. But neither Max nor Anna could deny the jolt of sensual electricity that passed between them when they first met. The searing sweet temptation of loving once more swept away the dark secrets of Anna's tragic past. And as Max's strong arms held Anna close, she knew she could never resist his fiery caress--no matter where their passions might lead...And they found a love that heals all wounds. A bit too sexy for my taste these days, however!

Perhaps the best way to describe the reciprocal feelings of Leo and Sonya Tolstoy is to quote from their own diary entries. He said: "Nobody will ever understand me." She said: "He has never taken the trouble to understand me, and does not know me in the least." It was a marriage that reached to the highest heights, and sank to the lowest depths... over and over again in each direction. And anyone wanting to know more about it should not neglect Shirer's excellent book. By seesawing between the extensive diaries of these two "lovers" Shirer takes the reader right into the eye of the storm... one of the most amazing things about this tumultuous marriage is the extensive and meticulous documentation of the participants. And the author's collation, skillful narrative sense and endnote pages show that he was well acquainted with the extenuating circumstances of these two lives trying to live as one. The latter half of the book is to be commended for its appropriate emphasis on the disastrous influence of Chertkov, the disciple who became the usurper of Tolstoy's most profound devotion. In my opinion, this rift named Chertkov gradually became the uncrossable chasm that irreparably separated Leo and Sonya. During this time, Tolstoy's alliance with his daughter Sasha further alienated husband and wife, and Shirer covers this development with great insight. It's all here... from the peace, courtship, and high hopes of Yasnaya Polyana to the final conflict, rejection and despair of Astapovo.

Shirer knew this was to be his last book, and it was. After such a prolific and successful career (14 books and 52 years), to devote his last energies to such a work must imply that he took a special interest in the subject matter. It shows. All of the other books of his I've read have been excellent, and this one is no exception.

From back of book:
As the beautiful Angel Sherwood sailed from England to Louisiana, she sensed hat her destiny flowed with the rough waves of the ocean.Frightened by the harsh sea, Angel prayed that perhaps, just perhaps, she would find happiness and romance in her new home.

But Angel's fate changed course when she was kidnapped by the cruel, yet captivating pirate, Captain Ty. And even though her future was suddenly in the balance, Angel was strangely warmed by his manly touch.....

This is an absorbing story about Sonya Andreyevna Tolstoy, the wife of the novelist Leo Tolstoy. It details the few years of her life before her marriage and after the death of Tolstoy, but mostly deals with their incredibly difficult relationship during their 48 years together. The reader gets all the inside information through the author's use of diaries, books and articles written by family members (everyone these two people knew or were related to kept a diary or wrote a book!), and quotes from letters. Anne Edwards did an excellent job of using all these sources to write a book that will get your attention and keep it. Women, especially, will feel Sonya Tolstoy's pain, frustration, hope, joy, and despair as they read her story. Leo Tolstoy was an extremely gifted artist and thinker but apparently wasn't easy to live with. Through the years his wife was portrayed as the difficult one and the blame for their troubles was placed mostly at her feet. This book casts her in a more sympathetic light and lets readers understand the reasons behind some of her well-documented actions, yet doesn't paint her as a saint or a martyr. I started reading a copy of this biography 15 years ago and had to return it to its owner before I could finish. I had looked for a copy of my own since that time and could never find one until I looked here (thanks Amazon!). It was well worth the wait!