From Amazon. I haven't seen such a happiness for a long time, huh, huh, the foreigner is really humorous. Good Reference In Basic UNIX API., September 26, 2001
REVIEWER: "Targeted" (Yellowknife, Canada)
This Book Seemed to Be Magnificent At First As It's Big (700 Pages), Heavy and Has A Nice Cover. And Most of the Text Turned Out To Be Great As Well. But There Were Downsides.
From the first 14-15 chapters it seems like this is one of the best API references I saw. It's not just Unix, it's the way the author writes. He tells you what can be done, how exactly and what to watch for. Typical Chapter CAN Look Something Like:
---
Chapter 93. Cooking Eggs.
Eggs Are One of The Delicious And Nutricious Meals. Kitchenware Provides The Following Functions to Cook Eggs:
EGG_T EBOIL (EGG_T EGG, TIME_T TIME); EGG_T EPANFRY (EGG_T EGG, TIME_T TIME); EGG_T Emicrowave (EGG_T EGG, TIME_T TIME);
All three functions take egg and time to cook and return egg. If time is 0 the egg is cooked until ready. If time is less than 0, it's cooked either for abs (time) or until ready whichever is less. Note, that only superuser can microwave an egg. Historically, these functions were written to operate with kitchen eggs only. Latest versions of Kitchenware add a function yolkctl (egg_t egg, bird_t whose) that you call with eggs before you pass them cooking functions.
EXERCIESES:
1. Microwave an Egg. What happened? Explain why.
---
Well, this is just a few lines, whereas in the book it takes pages and pages of very detailed pedantic explanation. And this was great until approximately chapter 14, when the author started to put more and more sample code inline, in pursue of showing the functional working application or set of functions This is one of the downsides (to me, if you like to dig through C code rather than reading plain text words - all the better).. I think that a book like that should be a reference . The author does not show any algorithms and ideas anyway, so why bothering writing something big Give men a bricks and they will build the house themselves.The other downside is also about the C sample code As I said -?. the way Mr. stevens writes text is very good. and the code is good as well, but not for a sample. In every single sample he is checking every possible error and not simply puts nice little trellis (...) where error handling should be, but Actually Handles Them. Too Pedantic and Turns Half of all the samples into calls to err_output or something. And at the very same time he uses custom header file (ourhdr.h) listed in appendix X, thus making it confusing to catch which is a new function you are reading about, and which IS Another auxiliary macro from what Custom Header.
One more thing - the book is basically all about
