5 comments about Oracle JDeveloper 10g for Forms & PL/SQL Developers: A Guide to Web Development with Oracle ADF (Osborne Oracle Press).

1. This book served well our need to train Oracle Forms developers in JDeveloper/ADF. The first part is a good technological review, the second a hands-on to build an application that not only tells what to do and how to do it, but explains it fully. It was useful even after attending formal Oracle training.



2. This is an excelent book for begining web development, it explains you step by step how things work and "glue" together. The only reason for me to give it 4 stars is that, in the book it explains how to build part of an application (tuhra) and it tells you to look for the rest (of the app.) on the web site..... I looked for it but it is nowhere to be found... (they only have the parts of the app. that you develope while doing the books excercises).



3. Great



4. exellent Book
   
   Goods Tips for programming Oracle ADF
   
   greetings from Toluca, EdoMex, Mex.



5. Being a traditional pl/sql developer, I was drawn to the title of the book immediately. I know I need to eventually buckle down and learn Java, but what better way than by drawing parallels to pl/sql and Forms.
   
   I like the hands-on examples that has you build a fairly complete application from scratch. I say fairly complete because its only a 500 page book and it allows the reader to go out and research ways to improve it.
   
   One of my favorite parts of the book is a summary section that shows up after a large chunk of instructions called "What did you just do?" This sums up what the reader just performed - explaining in layman's terms what you actually just did.
   
   Although I'm sure you can get similar tutorials on OTN somewhere, having a book to flip back through is always nice.

5 comments about Project Arcade: Build Your Own Arcade Machine.

1. I like the book. but i wish to warn buyers about outdated parts. in the book and on the cd it lists many links. but many of the website have gone down and are dead. in the description for the book it says it gives details on making controls, but some cases it just gives links. some of are dead. but it does give good info on emulator, encoders and many other things that are hard to find on the web. but i think the man should have cut some parts short and added controle construction.



2. This book covered so much more than what I was expecting. If you have never built an arcade cabinet before then I would recommend this book if only to see how many different ways it can be done.



3. This book is a lot more "Techie" than I expected. It involves taking apart and reconfiguring quite a few things to get what you need. Sure it shows where to buy the components if you wish, but then why not just buy the arcade game already made. It does show you how to build the case. I thought it would show how to take your X-Box or Playstation and build an arcade enclosure to get the arcade feel. That is not what this book is about. You take a computer and several components, plus a moniter to make an arcade game. It is very informative but not quite what I expected. It is not a 1 or 2 weekend project. Do a search for mame to see what I mean. Mame is very important to this project.



4. This is a good book.
   My only thing is most of this is on the internet and may even be more updated if you find the right websites.
   
   But it is helpful as for the beginner will help you plan things out in advance. Would be nice to have a few more illustrations like some sample wire diagrams of the controls etc.
   
   But again..it has lots of reference websites listed in the book that can also assist.
   
   My suggestion is -> don't build a Mame Cabinet if you don't have the internet...because you will need it.
   
   Seems to have covered all the basis and the added cd is a nice touch.



5. Following the Arcade scene for a few years, I've been promising myself this book once I'm ready to sit down and start building my own MAME Arcade cabinet.
   
   After getting the book and skimming through the pages, I was disappointed to find it's either information I've already discovered on my own by surfing the Internet, or the links to additional content or files are severely outdated and a number of external links no longer work. The copy of MAME they provide you is ver 0.7x (Latest incarnation of MAME is over .100)
   
   Don't get me wrong, this book is great for those who haven't already done the research and want an all-in-one book on how to do it. For me however, I gained nothing from the book.

5 comments about Hibernate in Action (In Action series).

1. This is not a bad book. I'm glad I bought it and glad I read it. Its problem is that it doesn't live up to its hype. It is not "the ultimate Hibernate reference" by any stretch. In fact, it's not much of a reference at all, so if your expectations of it are too high, you may end up disappointed.
   
   If you are serious about learning Hibernate and want to get as much depth and background on as many aspects of it as possible, this book is definitely worth reading. The text is well-written and clear, and the information is straight from the most qualified Hibernate committers.
   
   On the downside, this book is missing most of the important administrative and troubleshoting information you will want when you are actually using Hibernate, the book isn't organized so you can easily find any particular detail, and Hibernate is moving on, so some of the information is dated.
   
   Ultimately, if you want practical information or a good reference on Hibernate, I don't think the question you want to ask is "what book should I buy?" You want to ask "why should I buy a book at all when I get much better info for free from google search?"
   
   When you are first getting started, the "getting started" example from the online doc distributed with Hibernate is comprehensive and useful. By contrast, the "Hello World" example in this book is superficial and missing information you need. For example, the very first thing when you work with Hibernate you'll have to include about a dozen .jar files into your project, and you have several choices among alternative jars that you won't care much about `till you become more advanced. Some help is online, little or none is in "Hibernate in Action."
   
   I think Hibernate is all-in-all a great piece of software. Object-to-relational mapping is a hard problem to solve, Hibernate does a great job at the basics of it, and the world is a better place because the boys from jboss donated us their solution. When it works it's like good magic should be. But when it fails, it fails hard, horks all over itself, and spews out a bunch of mostly unhelpful junk. Hibernate suffers from having been developed by an insular group of developers who are too close to their problem, and who have lucrative day jobs as consultants they need to get back to. The result is not much in the way of troubleshooting help, and troubleshooting help is what you'll find you need most. Hint 1 - you won't find such help in "Hibernate in Action" so go to google and type in the text of the error message you get. Hint 2 - you will find a lot more people asking the same question than people answering it. Perservere and be a good detective and you will figure out what you need.
   
   References are organized so you can easily find that one little detail of information you need right now. References have things like short sections with short clear titles that are language keywords or clearly intuitive concepts. References also have long, detailed indexes with a lot of repitition. "Hibernate in Action" has none of this, and it is devilishly hard to find details in it even though you know they are in there somewhere. My copy has about 25 little sticky note bookmarks to help me find things, but most often I don't bother and I just go straight to google.
   
   Finally, Hibernate has evolved since this book was published. My favorite change is that it now includes support for Java 5 annotations as an alternative to XML or XDoclet configuration. Hibernate is notable, like Struts, in helping you get out of J2EE-EJB hell, and into XML configuration purgatory. Annotations rock in relieving you of the keeping-the-XML-in-sync-with-the-Java torture, and you need a reference that doesn't steer you towards doing it the old way. AFAIK, as of this writing, that's only available online.



2. With this book, we have the rare circumstance where the founder and principal developer of the technology has authored the material. Moreover, the back jacket promises that the text would build on a single example to show how to use Hibernate in practice.
   
   Sorry, dear reader. This book falls far, far short of its promise. Yes, you can download a single cogent example. But the authors make only loose reference to that example, choosing instead to offer dozens and dozens of snippets, out of context with the example. A first-class book, such as Mastering WebLogic, not only provides a robust example, but also walks the reader entirely through the example, from design choice, through coding practices, and ultimately into implementation decisions. In stark contrast, this book offers nothing more than a progression through various topics, illustrated via pieces of java classes, leaving the reader to hunt for the relevance to the downloadable application.
   
   The book does have its uses. As you dive into various real-world situations, this book should serve, after some digging, to reveal an optimal approach to solving the problem at hand. The topics are covered to a healthy depth. I suspect this is the best treatise available on abstruse topics such as caching, transaction handling, and mapping to legacy data stores.



3. I found this book useful and readable, and it helped me develop my first (and second) Hibernate applications. It begins with a brief overview of the kinds of problems which ORM solutions need to address. It then introduces Hibernate along with a couple of examples, upon which subsequent chapters build. (Some reviewers have criticized the examples, but I thought they were useful, and I didn't have trouble following them) One thing you should be aware of: while this book is a good narrative, it's not as useful as a reference. I find myself paging back and forth among several chapters which cover topics in different levels of detail. That shouldn't be a show-stopper since reference material exists on the web. You might be concerned is the book covers Hibernate 2.1, while Hibernate 3.x and Ejb 3 are out; the book is still relevant and valid, and I've used it along side Hibernate 3 with no problem.



4. This book is for Hibernate 2. Hibernate 3 is covered by the same authors in Java Persistence with Hibernate



5. A great book for getting going with Hibernate quickly.
   Some parts are heavy going because it is packed with info. This pays off because there is little or no padding/rubbish.

5 comments about Exceptional C++: 47 Engineering Puzzles, Programming Problems, and Solutions (C++ In-Depth Series).

1. This book is a collection of silly, unusable tidbits. The author discusses unimportant issues that most programmers have no need to know in order to create excellent c++ code. If this is how one becomes a C++ Guru, then count me out!



2. There seems to be a bit of confusion about what level this book is at. Based on some of the reviews I've read, I was a bit concerned that much of this book would fly right over my head, exploring advanced and obscure features. So let's get one thing straight: this is pitched at the same level as Effective C++, and has a similar structure and style.
   
   And it's not just a 'puzzle' book - although it does highlight some tricky issues to do with templates and name lookup, which might conceivably appear in an unimaginative job interview.
   
   And it's not just about the language feature of exceptions. All aspects of the language are covered, but the section on exceptions is particularly good.
   
   Nor is it 'advanced' in the sense that many practitioners of C++ would consider, e.g. template metaprogramming, or non-portable hacks that take advantage of memory layout of compilers. Instead this is advice at an intermediate level, assuming you know the syntax and purpose of C++, but exploring their most appropriate use.
   
   The structure of the book does involve a series of posed questions, but they differ wildly in how specific or general they are. You can see them more as a rhetorical device to frame the subsequent discussion, rather than questions you must answer (unless you want to retrospectively crown yourself guru of the week, of course).
   
   Each question is followed by a significant discussion of a particular language feature, and summarised advice and recommended principles. Therefore the book is similar in structure to Effective C++. There is some overlap between the books, although even where similar material is included, there is differences in how much detail is given.
   
   To some extent, this book is a victim of its own success. A lot of the advice given here can now be found in other books. But its legendary status means that like Effective C++, this is still essential reading as soon as you've graduated from introductory tomes.



3. This book presents advices more or less in the same format than books from the Effective C++: 55 Specific Ways to Improve Your Programs and Designs (3rd Edition) (Addison-Wesley Professional Computing Series) serie. What is similar is that topics are divided in 47 small items of few pages each. The difference is that the author first ask questions to the readers or propose exercises and encourage the reader to put down the book and to take the time to think about the problem and then come back to read his answer. This format is more or less original as I have seen something similar in Tom Cargill C++ Programming Style (Addison-Wesley Professional Computing Series) book.
   
   I have read this book pretty fast which is a good sign of my interest in a book but in the same time this book did not leave me a strong impression that will make me remember this reading for a long time. It is hard for me to say exactly why but I think that it is because most items focuses on very small details of C++. Some of these problems are very hard and probably is an indication that the book targeted audience is advanced C++ users which is not a bad thing by itself but I am not convinced that mastering these small details actually has a high impact on someone programming skills. It is probably just a matter of topic choices as I really appreciate much more the sequel than this book.
   
   My review will probably not affect your decision to read or not this book. You will have to read it to find out if you like it but hopefully I have been helpful to let you know what to expect from this book.



4. Just finished it. It may not be so apparent at first, but definitely you need it to find how to write a "perfect" C++ code.
   Of course, before reading this book, several intermediate books demand reading, such as "Effective C++", "More Effective C++", "Effective STL". Some system programming book may also need to be read. Otherwise, you may have no idea why you need this book.



5. This book and exceptional c++ series are the best book series, I have ever read. Its language and presentation of material is exemplary. I learned a lot from this book and suggest to anyone to leverage his/her knowledge.

1 comments about Beginning XML Databases (Wrox Beginning Guides).

1. I work with a lot of school leavers and people outside IT and often have to advise them on how to empower themselves in IT in the right way. Surely SQL and databases are one of the first topics people should understand. HTML was also high on the list. With this book, the author has combined all of them in one making it a very relevant combination for today's beginner. I will recommend this book to school leavers, financial people and people outside IT wanting to empower themselves quickly. Another great advantage of XML and databases is the platform independence. Very well done to the author for combining these topics at the entry level in such an easiliy understandable way!

5 comments about C++ in a Nutshell.

1. I found this book is excellent. It concisely covers many finer
   points of c++ language, which are not fully explained
   in many other similar books. Of course, your understanding of
   this book will be greater if you have already studied c++ for
   a while.



2. I always like O'Reilly books and are usually what I purchase. The "In A Nutshell" may be misleading to some. Just think of it as "C++ A Language & Library Reference." If you are a beginner looking for a how to, this isn't the one for you. "Thinking in C++" by Bruce Eckel (great book), or "Practical C++ Programming" would be the one a beginner would want. However, when you are ready to explore the inter-details about what C++ classes provides, this would be a good one to add to your collection. The first half describes C++ in general, while the last half details the language reference. I like how the reference is structured, grouped by the easy to find header declaration at the bottom of the page. Quickly finding what you need is a great feature here. You can only do so much "std::cout << "hi" << std::endl; without a reference and this one covers the missing details. Not for beginners, but an excellent reference.



3. This is a great reference book. You definitely need to know something about c++ to get the full benefit of it. I would recommend it.



4. Many implementations of C++ extend the language and standard library. Except for brief mentions of language and library extensions in the appendixes, this book covers only the standard. The standard library is large, but it omits much that is common in computing today such as concurrency, network protocols, database access, graphics, and windowing. However, Appendix B contains some information about nonstandard libraries that provide additional functionality.
   
   This book is a reference, not a tutorial, thus those unfamiliar with C++ might find portions of this book difficult to understand. Although each portion of the book contains some advice on idioms and the proper use of certain language constructs, the main focus is on the reference material. This book is divided into two interleaved sections that cover the language and the library, and a couple of appendixes. Roughly speaking, the language is the part of C++ that does not require any additional #include headers or files. The library is the part of C++ that is declared in the standard headers.
   
   Chapter 1 through Chapter 7, Chapter 11, and Chapter 12 cover the language itself. The first seven chapters form the main language reference, organized by topic. It is customary for a programming reference to contain a formal grammar, and this book does so in Chapter 12, which is organized alphabetically by keyword with some additional entries for major syntactic categories, such as expressions. Chapter 11 is a reference for the preprocessor. Chapter 13 is the library reference, organized alphabetically by header. Chapters 8 through 10 present an overview of the library and introduce the topics that span individual headers. A detailed accounting of each chapter follows:
   
   Chapter 1. Language Basics - describes the basic rules for the C++ language.
   1.1. Compilation Steps
   1.2. Tokens
   1.3. Comments
   1.4. Character Sets
   1.5. Alternative Tokens
   1.6. Trigraphs
   
   Chapter 2. Declarations - describes how objects, types, and namespaces are declared and how names are looked up.
   2.1. Declarations and Definitions
   2.2. Scope
   2.3. Name Lookup
   2.4. Linkage
   2.5. Type Declarations
   2.6. Object Declarations
   2.7. Namespaces
   
   Chapter 3. Expressions - describes operators, precedence, and type casts.
   3.1. Lvalues and Rvalues
   3.2. Type Conversions
   3.3. Constant Expressions
   3.4. Expression Evaluation
   3.5. Expression Rules
   
   Chapter 4. Statements - describes all the C++ statements.
   4.1. Expression Statements
   4.2. Declarations
   4.3. Compound Statements
   4.4. Selections
   4.5. Loops
   4.6. Control Statements
   4.7. Handling Exceptions
   
   Chapter 5. Functions - describes function declarations and definitions, overload resolution, argument passing, and related topics.
   5.1. Function Declarations
   5.2. Function Definitions
   5.3. Function Overloading
   5.4. Operator Overloading
   5.5. The main Function
   
   Chapter 6. Classes - describes classes, unions, structures, members, virtual functions, inheritance, accessibility, and multiple inheritance.
   6.1. Class Definitions
   6.2. Data Members
   6.3. Member Functions
   6.4. Inheritance
   6.5. Access Specifiers
   6.6. Friends
   6.7. Nested Types
   
   Chapter 7. Templates - describes class and function template declarations, definitions, instantiations, specializations, and how templates are used.
   7.1. Overview of Templates
   7.2. Template Declarations
   7.3. Function Templates
   7.4. Class Templates
   7.5. Specialization
   7.6. Partial Specialization
   7.7. Instantiation
   7.8. Name Lookup
   7.9. Tricks with Templates
   7.10. Compiling Templates
   
   Chapter 8. Standard Library - introduces the standard library and discusses some overarching topics, such as traits and allocators.
   8.1. Overview of the Standard Library
   8.2. C Library Wrappers
   8.3. Wide and Multibyte Characters
   8.4. Traits and Policies
   8.5. Allocators
   8.6. Numerics
   
   Chapter 9. Input and Output - introduces the I/O portion of the standard library. Topics include formatted and unformatted I/O, stream buffers, and manipulators.
   9.1. Introduction to I/O Streams
   9.2. Text I/O
   9.3. Binary I/O
   9.4. Stream Buffers
   9.5. Manipulators
   9.6. Errors and Exceptions
   
   Chapter 10. Containers, Iterators, and Algorithms - introduces the suite of container class templates, their iterators, and generic algorithms. This is the portion of the library that has traditionally been called the Standard Template Library (STL).
   10.1. Containers
   10.2. Iterators
   10.3. Algorithms
   
   Chapter 11. Preprocessor Reference - an alphabetical reference for the preprocessor, which is part of the language, but with a distinct set of syntactic and semantic rules.
   
   Chapter 12. Language Reference - an alphabetical reference for the language and grammar. Backus-Naur Form (BNF) syntax descriptions are given for each keyword and other language elements, with pointers to the first seven chapters for the main reference material.
   
   Chapter 13. Library Reference - a reference for the entire standard library, organized alphabetically by header, and alphabetically by name within each header section.
   
   Appendix A. Compiler Extension - describes ways that some compilers extend the language: to satisfy customer need, to meet platform-specific requirements, and so on.
   
   Appendix B. Projects - describes a few interesting, open source C++ projects. You can find information about additional projects on the book's web site.
   
   The book illustrates the descriptions and definitions it covers with plenty of examples - some quite short, and then some longer ones as you get further into the book. If you need a good desk reference on C++, this is definitely the one to buy and keep by your side.



5. Hi,
   I'm a recent graduate B.Sc CS and used this book extensively for a month+ as to prepare for a c++ job interviews.
   
   Unfortunately I can't say I loved this book. I found the examples to be overcomplicated by irrelevant information and language to be ambiguous at the times.
   
   As an example, from page 160 (classes/ covariant return types):
   "In a derived class, a covariant return type is a pointer or reference to a class type that derives from the return type used in the base class" ?!
   
   Code examples are contaminated by the irrelevant programming techniques and irrelevant code. Page 158, "declaring and using virtual functions", the code example extends over two pages. In it, author uses concepts of templates, complicated operators overloading, constructor and destructor, pure virtual functions (its different topic in the book, much later) as well as a very complicated programming code. And all of this extra information used to explain a rather simple virtual functions.
   
   If the reader is not very familiar with some concepts of programming language, reader might face a difficulty to understand the topic illustrated, as it would be polluted with much unrelated code technique.
   
   I wouldn't recommend this book for the beginners, and would proceed with caution if you are an intermediate programmer. This is a great start but author need to maintain focus on the particular topic and not to make it more complicated then it's already is. After all it's a reference book and not the collection of the brain teasers.

2 comments about Visio 2007 For Dummies (For Dummies (Computer/Tech)).

1. As usual the Dummies series is pretty good and gives you a general intro and easy to build on concepts and how the product works and how to work it as you need it.



2. I recommend against buying this book. I read only about a third of it and found two errors on fundamental points. On p. 67, there is a glaring misstatement about the use of Wizards that suggests that the authors never even tried the feature they are "explaining." And on page 98 there is a section on "Nudging" shapes where in half a page of text the authors do not reveal the one thing that one must do in order to "nudge" a shape -- namely, hold down the Shift key while using the up and down arrow keys. It appears that nobody bothered to proofread this book after it was written.

4 comments about Mastering Joomla! 1.5 Extension and Framework Development.

1. I recently read "Mastering Joomla! 1.5 Extension and Framework Development" by James Kennard, and I must say I really enjoyed it. Every time I read a book about Joomla! framework and extension development, I get all sorts of new ideas. This time was no exception. The book provides a thorough description of the topics surrounding Joomla! 1.5 extension development, and it is a great reference book. I would not recommend reading the book cover-to-cover, but I think it is a great resource to have handy when attempting to develop extensions for Joomal! 1.5. The book was written for experience PHP developers who already have a working knowledge of Joomla! For those wanting to learn Joomla! extension devleopment, I recommend starting with Joe Leblanc's book, "Learning Joomla! 1.5 Extension Development", and having "Mastering Joomla! 1.5 Extension and Framework Development" as a reference for getting more in depth with the framework.



2. The really frustrating thing about this book is the style and lack of indexing. When I buy a technical reference, the most important thing is being able to look up any relevant term or function name and immediately find the place to read about that. This book has the terms subcategorized under other terms that only make sense if you already know Joomla programming! I seriously almost never find the term I'm looking for in the index. This really drives me crazy. When I have found the area I'm looking for, however, I've been pretty happy with the quality of explanation provided. Indexing is all important.



3. If I didn't already know MVC, Joomla 1.5 and had made components before I think this book would be useless.
   
   
   If you have dabbled in developer code however and Joomla 1.5 this is a great resource.
   
   This book lacks examples of building finished components.
   
   If it combined the style of other books like learn joomla 1.5 as well as having this great resource of information it would be worth solid gold.
   
   Without it and without a good index It takes time to find what you are after. Once you find it however it always provides great, accurate information.



4. The book was a good resource for me to get to grips with the Joomla 1.5 API, having had very little experience of Joomla and PHP development in general, however having a good background in programming. I feel the book has been written with developer's like me in mind, i.e. people who have knowledge of general web application programming but little or no knowledge of Joomla. The way the book has been sectioned progresses nicely, starting with a brief intro to Joomla (for completeness' sake), a Joomla programming Getting Started chapter and then delves into the API per se. It introduces the general classes Joomla uses, and how they relate to each other. Each chapter then introduces and describes more enhanced functionality, such as accessing the database, developing components, the MVC model, and keeps on building, with each chapter building and adding to the knowledge learned in the previous chapters.
   
   Overall I think this book is a good start for anyone delving into the Joomla Development world. It introduces the concepts, explains, and with that knowledge you can go ahead and dive into your development.

5 comments about Microsoft SQL Server 2005 Stored Procedure Programming in T-SQL & .NET.

1. If you are looking for a good review of exisiting as well as new features available for T-sql and stored procedures in SQL Server 2005 , then this book will start you in the right direction. The author has many examples and useful insights peppered throughout the book. I do wish though that he used the AdventureWorks database instead of his own since Adventureworks is the new demo database provided by Microsoft.



2. I got this book as a present and started reading it immediately upon receiving it. I read it from cover to cover in about 2 nights. It lays next to my computer at work for constant reference. [...]
   
   It is very informative and very well laid-out. I never once was lost and wondered what the author was talking about. It's vocabulary and grammer are just right for the advanced programmer to the programming newb.
   
   I was able to excel my sql server skills very quickly with the help of this book. I suggest buying this book to all sql programmers new and old.



3. I got this book for school, since it was required. Usually I'm skeptical about publishers other then O'reilly, WROX and Programmers for Programmers and maybe Friendsoft, since I think that quality of the book somehow depends on the publisher =), but this one is looking pretty good so far. I'm on the page 200 out of 650 and It's pretty clear, except for some minor points that I was able to search on the web for. I like it, it has some good examples and detailed enough explanation.
   
   I give it 4 mainly cause nothing is perfect =)
   
   Thanks,
   Alexander



4. Dejan Sunderic, Microsoft SQL Server 2005 Stored Procedure Programming in T-SQL and .NET (McGraw-Hill, 2006)
   
   Not a bad little book, this, though if you've had to dig into SQL2005 for work you're likely to have picked up on a good deal of this already. Still, Sunderic digs down into a number of places where most developers either don't normally have a reason to go or simply fear to tread. You're sure to find things in here you've overlooked (or never thought to look for) unless you're a guru, and even then there might be a [...]bit or two. For someone who just got thrust into "we're upgrading!", it's been great. *** ½



5. First off I know the author personally. In spite of that, the book definitely stands solidly on its own merits. This book is shock full of tips, tricks, angles and perspectives to maximize the use of stored procs in your SQL databases. Dejan really goes under the covers to the many aspects of SQL and the reader is the richer for it. This is a very important how to and reference for any serious SQL developer. You will go back to this book again and again. Highly recommended!

5 comments about Expert C Programming.

1. I buy a lot of programming books and this one has always stood out as being exceptionally well written and useful. I remember this book as a code quality/best practices book for anyone who wants to spend less time fixing bugs by clearing up common misconceptions and eliminating them once and for all.



2. First of all, this book is not really for beginners in C rather its more for the experienced C programmer. It contains the nuances of C and offers a historical perspective and after which the author provides a workaround, if applicable.
   
   i love the anecdotes and stories in each chapter and provides a wonderful read. I would also recommend "A Book on C(4th Edition)" by Kelly & Pohl where in that book it contains all of the stuff that "Expert C Programming" has and covers basics to advanced topics.
   
   Last thing, i love peter's sense of humour :-)



3. I bought this book over a decade ago, in a rush to learn things that I needed. I recall it was a distinct waste of time. I'm no expert in C, so I needed tips. In the end, I favored other books that provided examples along with anecdotes. This book seemed to be much more focused on exhibiting how clever the author is, instead of actually helping me pull myself up by the bootstraps. The book I actually leaned on for advice (and I did write some code at the time) was Pointers on C by Kenneth Reek.
   
   Save your money, look for another resource.



4. This book is for advanced C programmers. You should only move on to it after you have a good grasp of the material in Kernighan & Ritchie.
   
   You will find this book informative as well as entertaining. It is a perl. Go for it, you won't regret it!



5. I am still making my way through the book but it has been worth the purchase price already. I have a queue of two friends that want to borrow it already :D