








The authors are obviously very knowledgable and experienced about software. I encourage them to "throw this one away" and try a rewrite from scratch. Short of that, they could provide a road map through their book; first read this chapter, then skip to the second half of that one, etc.
The sad news is that there may not be any good guide to autoconf etc anywhere yet. Like the DNA in your body, all autoconf files are very likely descended by an evolutionary process from a few original specimens.

Months later, and after doing some actual Linux C development myself (a command interpreter, no less), I came back to this book, and was able to get a lot more out of it. Just be aware that it is geared toward someone doing really involved open-source/GPL'd C development.
This book may have been better if each feature of the autotools were discussed in a more abstract way, without following the development of this sic shell. It is interesting, but that kind of orginisation forces you to read it from front to end to effectively understand it, which of course you SHOULD do, but it's at the expense of being a solid reference. It's no biggie, though, because the free GNU documentation fills that gap.

I sit here, staring at a messy Makefile.am and let me tell you, the future is looking pretty bleak. Imagine the rainiest day, the most miserably cold weather, the most awful meal you've had to eat and say tasted great: for some, the pain of dealing with cross platform Makefiles is exponentially worse.
I thank all the authors of this book every time I try to do something impossible within the constraints of GNU make syntax.
This book clearly explains Makefile syntax. Then, it explains how to automate it all with GNU autotools. Then, it provides a bunch more information. I think this book is clear and well-informed, and I find myself turning to it instead of the on-line manuals. (Note, this book is available on line as well, for free. Buy it anyway.) Some of the details may be lost on people not doing serious, cross platform Unix development, but the read is still highly recommended.
For those still think mulletts are cool, writing Z80 asm is "fun," that women and cooties are inseperable, and that real programmers write their own damn Makefiles, I offer my sincerest sympathies. The first step is admitting you have a problem. The second step is getting this book.
Godspeed.

List price: $18.95 (that's 30% off!)






He quotes every whine or weaze at Shakespeare that he can find. For example, he quotes Tolstoy and his famous dislike of the bard. Not mentioning that he hated Lear because he could see direct parallels in his own life. He quotes Shaw, but does not mention that he hated Shakespeare, partly, because he was considered to be the better playwright. Something Shaw could not abide.
Taylor in his desperation to attack Shakespeare uses any weapon at his disposal, including a motley collection of post modern whines and textual gripes.
No one is allowed to be great anymore and while modern English Literature criticism is hell bent on destroying the pleasure of reading and watching Shakespeare, people will continue to do so as academics like Taylor become more and more remote from what they are writing about. Read this and then Bloom for some sensible writing about Shakespeare.
Taylor is at war with himself, and it is a mess of a book.










I recommend this for divers who have gone through open water and advanced classes (and even Rescue), feeling that they did not get all they could out of the classes and textbook. This book is a must for those wishing to seek a professional dive rating (divemaster and higher), or pursue technical dive certifications.