1 comments about Applied Data Structures with C++.

1. Smith assumes you know the basics of C++. What he presents here is how to implement higher level data structures within the language. These include sets [an unordered group], lists [where an ordering is implied], stacks, queues and trees. Workhorse structures that are used in many areas of programming. The ideas behind each structure are rolled out, and example code is given, to implement the structure.
   
   The book appears directed at a new or intermediate C++ programmer. Advanced programmers should already be well versed in these ideas.

No comments about Invitation to Computer Science: C++ Version, Third Edition: C++ Version.

2 comments about You Can Program in C++: A Programmer's Introduction.

1. Francis Glasborow is one of the most frequent problem solvers on comp.lang.c++.moderated. And he has done a wonderful job authoring the book.
   
   I can recommend this book to anybody who knows basic programming (in any language) and wants to learn C++. In addition to the coverage of C++ basics that you find in many other C++ primers, you will find invaluable caveats and tricks.
   
   There are a few typos in the example programs in the later chapters. In spite of those, I still rate the book 5 stars as I could learn more C++ from this book than most others. After going thru 388 pages of this book, I find myself capable of taking on advanced C++ books -- like Modern C++ Design.



2. This C++ text is considerably less verbose than most, as it makes some significant assumptions about the reader's prior programming knowledge.
   
   These knowledge assumptions are the book's primary weakness for beginners. Early on the book presents concepts that many readers, even those with prior, but non-C++, programming experience, will not have previously encountered. For example, the author presents the term side-effect without explanation. As early as page 31 basic exception handling is presented in a small program. Iterators are first mentioned without an adequate discussion of what iterators are. Other items from the STL are also presented with explanations so limited that most novice C++ reader's will find the presentations very difficult, if not impossible, to follow.
   
   The author spends too little time providing details for a reader completely new to C++ or object-oriented methods to properly understand many of the new concepts presented, and too little time presenting well-coded exemplars. In chapter 3, e.g., the author states, "I deliberately leave some of these problems in my code because I want you to check code rather than taking my word for it." For beginners, this approach seems fraught with problems. I would have preferred to see programs correctly coded in the presentation sections, with code demonstrating poor practices, explicitly identifying what those poor practices are and providing examples correcting those weaknesses. Otherwise, code with potential problems should be left to the exercises. What reader's need are appropriate examples of good coding practices that they can emulate, not poorly written code examples. Snippets of code can be an excellent approach to presenting key concepts, but fully coded examples should demonstrate appropriate coding practices.
   
   Concepts are "fleshed-out" in later chapters, but "newbies" may find this book does not provide the solid understanding of the basics that they seek.
   
   Additionally, the improved and updated software does not always respond in the same way the earlier software versions used by the author did. For example, in the author's first floating point program, he deliberately leaves off an #include statement and comments that the user will see the compiler complain about this. However, my version of the updated C++ compiler, which is a later release of the one used by the author in preparing the text, accepts this situation without a problem and successfully compiles and runs the program.
   
   Many, in my opinion, unnecessary sections of the book relate to the author's inclusion of a graphic software package he developed called Playpen. This package provides extremely limited capabilities, and simply takes too much time and effort to learn. The package has essentially no value beyond the course. The author would have been better served to provide basic explanations of how to use the built-in graphics capabilities of the major OS systems currently in use. Perhaps he could have selected one, e.g., Microsoft's OS, and as he did for the IDEs mentioned earlier provided additional information on other OSs, e.g., Apple's, presented on the CD. This would have been far more helpful to readers, and have had real value beyond the course. I hope this approach will be followed for latter editions of this work, thus allowing the Playpen package to be removed. This package's limited educational value takes time away from important topics that could otherwise have been covered.
   
   However, in spite of, or because of, the author's conclusion about his readers knowledge level, many readers with some, even limited, background in C++ will appreciate this book's "get to the point quickly" approach. The author is also excellent in presenting appropriate C++ idioms, and showing where idioms carried over from other programming languages, even C, are inappropriate for C++. The author also takes time to explain why they are inappropriate.
   
   In summary, although the book indicates that it is appropriate for those with knowledge of another programming language, I don't concur. However, for those with prior C++ experience or knowledge gained from prior self-study of C++ basics, this is quite a nice book. It gets the reader programming from the start, and provides lots of short, complete, and easily understood programs illustrating key C++ concepts. It provides clear and appropriate short programming exercises throughout. It successfully brings many important advanced features of C++'s together in an authoritative manner.
   
   Thus, although it is not recommended as a first C++ book, it is definitely recommended as a good choice for those with some prior C++ knowledge or experience.

No comments about Computer Algebra With SymbolicC++.

3 comments about Mastering C Pointers: Tools for Programming Power/Book With Disk.

1. The writing style talks down to the reader. The book focuses on the MS/DOS architecture. Why isn't it titled as such? I stopped reading after the author commented that many programmers are afraid to use functions that return pointers. He then went on to give an example of how to use them. It was wrong! Reference page 111 of the SECOND EDITION. The "combine()" function returns a pointer to a local variable which is out of scope when it is dereferenced. I would have returned the book but unfortunately it came with a disk which I had prematurely ripped out! I doubt ant AP books will be finding a space on my bookshelf.



2. As a novice C programmer I found Robert Traisters book Mastering C Pointers useful for demystifying the use of C pointers. Especially valuable were the examples showing the importance of coding style and the use of spaces for making C code comprehensible. His comment towards the end about the importance of commenting code and using good structure was priceless. It goes something like this (I will paraphrase). Frequently it is stated that comments and good coding structure are essential to assist the programmer who comes along in a few months and gets stuck maintaining a piece of code. With C programming comments and good coding structure are essential ... so the progammer can understand his own code after coming back from coffee ... It is so true!



3. The material which this book presents on C pointers must, I repeat, MUST, be thoroughly mastered and understood before a beginning C programmer can become a serious professional. This book will provide that mastery. If every piece of C code which I have seen had been programmed by someone who had thoroughly and completely understood how to use C pointers, then the vast majority, if not all, of the memory leaks and other memory related problems in those programs would never have seen the light of day. Particularly useful is the discussion about uninitialized versus initialized pointers, pointer indirection, and addresses (constant pointers). The book is best summed up by a single sentence on page 77: "Always know where and to what your pointers point." Although this book lacks the glitz and polish of other comparable books on C, it is clearly a must read. As a C programming professional, I highly recommend this book.

1 comments about Windows Graphics Programming with Borland C++.

1. To get an old DOS Borland C program to compile and run under a Windows interface I bought the McMillan C & C++ Starter Kit with Borland C++ 4.52. If you are new to C++ graphics or Windows OWL, this book is a real gem and a good adjunct to these starter kits popping up in the stores.

1 comments about Pluggable Authentication Modules: The Definitive Guide to PAM for Linux SysAdmins and C Developers.

1. 
   The information contained in the book was easy to understand but it did not go into as much detail as I had hoped it would about what I was purchased it for.

1 comments about Writing DOS Device Drivers in C.

1. Much of this book is a rehash of what you can get from standard documentation. Some of the author's ideas and suggestions are not very practical. Really just a minor survey of the basic mechanics with little or no insight into the subject at hand

5 comments about The C Answer Book.

1. It is absurd that the authors and/or publishers of this book have such little regard for its readers as to hold them hostage. They should make it explicitly clear that the solutions to the problems will cost another $.



2. While Kernighan and Ritchie scored underground success with "The A answer book", followed by the solid "B answers", Their third effort finds the duo treading water, creatively. The authors borrow much from their earlier works and there is little here to suprise veteran readers of the series. Even bringing in new talents Clovis L. Tondo and Scott E. Gimpel fails breathe life into this flat treatise, which leaves the reader only to wonder what he can expect of their next endeavor. Still, the facts are for the most part accurate and this makes it worthy of a place on the shelf of the beginning student of C.



3. The book it answers, "The C Programming Language", is one that every C programmer probably owns and with good reason. This answer guide is a necessary complement to those of us who are curious about the authors' solutions.

   Maybe you need the extra explanations; I know I did at times, if only to clarify or validate my thought processes. If you have a professor using "The C Progamming Language" as the primary textbook, you won't need this book. However, if you're going it alone, it's a good complement to self-study because it will engage you in some rational dialogue about the solution methodology.

   That's the final star; if the book discussed rationale a bit more, it would merit the fifth star.




4. This book contains solutions to all the questions and exercises in the K&R C second edition. If you can figure everything out easily, then you don't need this book. If you want to cheat or need some help, get this book. I have it as a reference and to show my students.



5. I took the C programming class from Dr. Tondo and I appreciate the clarity of his explanations which are included in this book. 5 stars sure! This book is a little gem...

1 comments about Hardware Verification with C++: A Practitioners Handbook.

1. This is the first book I've read on functional verification not to talk about whitebox/blackbox blah blah, but all useful and practical tricks/best practices. I've just finished a systemverilog DV project with Mike. I joined the project half-way. I would say it was so easy for me to pick up the verification code and got up to speed. Lots of the tricks talked in the book were applied to this project, such as the logging output format, irritator, the "dance", directory structure, listener connection... The environment was done in a very neat and adaptable way.
   
   Personally I believe C++ is going to excel in the long run in the DV field. Because there is basicly no limitation on what you can do with C++. You have better control than with the current proprietary and sometimes arcane HVLs.
   
   I highly recommend this book to intermediate to advanced DVer.