5 comments about Thinking in C++: Introduction to Standard C++, Volume One (2nd Edition).

1. If you're looking to learn C++ as your first language, or your first OO language, good luck to you! I tried learning C++ after FORTRAN77, and in retrospect, that was a big mistake. Go and learn another object oriented language first, Python or Java or Ruby (maybe even OO Perl). You probably also want to learn a tiny bit of C, just to get used to pointers and memory management.
   
   Done all that? Good. I will be assuming in this review that you already know how to program reasonably and you're not trying to cram C, C++ and OO into your head at once. So, you just want to learn C++. If that's the case, this is the perfect book to start with.
   
   The book assumes that you're coming to C++ from C, and builds up from C++ as C with a stricter compiler, then onto C++ as 'object-based' language - objects as structs with functions and encapsulating initialization and memory allocation with constructors and destructors. Finally, object orientation (i.e. inheritance and polymorphism) is introduced. Rounding things off is a brief chapter on templates and iterators, but it's only a sneak preview, really.
   
   Only the core of C++ is covered: the standard libraries and other topics (like exceptions) are deferred until volume 2. This leaves volume one as a lean and mean exposition of the core of the language. This is quite an achievement, especially as it manages to be both comprehensive and readable. The somewhat begrudgingly object oriented flavour of C++ is also on display in this book, particularly when compared to Thinking In Java from the same author: there are interesting explanations of what the compiler is getting up to behind the scenes, which should presumably assuage the fears of the more paranoid C programmer. There are copious code examples, although the expected output is not given, which would have been helpful. The introduction to the make utility will also be very welcome to many (including me).
   
   This is not quite as good as Thinking in Java, perhaps because of its C-centric opening section, which may require you to familiarise yourself with the differences between C99 and C++ simultaneously (this is particularly apparent in the discussion of the static and const keywords).
   
   But it's still a great introduction to C++, and it doesn't waste time with the basics of variables, loops and conditionals. Between this, the second volume, and Koenig and Moo's Accelerated C++, you have all you need to graduate onto the intermediate C++ books, like the Exceptional C++ and Effective C++ series.



2. This book was a pleasure to read. It does a very good job of teaching you the C++ syntax in the context of the C++ paradigm; a great improvement over many similar introductory books that seem to focus upon teaching you syntax only. By the time you get through with this book, you will have a good idea why things in C++ work in the way that they do, and such knowledge helps you considerably when you actually start writing useful code.
   
   Overall, this is one of my favorite programming books, and it's highly recommended.



3. this is a must have for all people that need to learn c++
   even if you are novice or experience developer this is a book that you will always open and consult.



4. Bruce Eckel's book very thoroughly covers the Standard C++ programming language. It may be a little dated (my copy says (C) 2000), but I don't think the Standard has evolved since his writing.
   
   The Good: Bruce does a terrific job going into gory detail on all aspects of this (let's just face it) complicated language. C++ has lot's of traps and ditches to offer compared to C# or Java, and if you plan to use a lot of the advanced concepts of the language, a helper like this book is almost indispensable. If you are coming from the C realm, this books is a real hit: Bruce constantly points out the subtle differences between C and C++, and also explains how C++ is a safer language than C in almost every facet. The book does a fairly decent job in going from the simpler to the more advanced concepts, though a few times he has to use constructs that will only be covered in later chapters (Bruce does point out these outlooks though appropriately). If you are really into learning a new language, the Exercises at the end of each chapter are a terrific way to learn the new concepts.
   
   The Bad: The text within the chapters is not very well structured. If you later on try to find something, the prose form of the sections does not really help you doing that. Also, the Index is not that great either. Often times you are sent to pages that just marginally address the keyword, and the essential introduction or explanation of the keyword may not be in the index at all. My real gripe though is with the practicality of the examples. While I previously stated that the Examples by itself are a great way to learn the languate, a lot of his examples are just plain bad ideas how to code. I understand where Bruce is coming from, he tries to find examples for all the subtleties he just covered in the section. Nevertheless, he often asks for pretty bad things to be implemented. On principle, from my own personal experience a lot of the special cases of the language are hardly ever used in real life situations.
   
   I do recommend this book, especially if you are coming from C. Just take the examples with a grain of salt. If you are a seasoned software developer, you can probably tell anyways which of the examples or techniques should not be used on the job.



5. Observations:
   - aimed at C programmers
   - gradual introduction to C++
   
   Constructive criticism:
   - lacking diagrams and elegance
   - detailed description of problems when using C

5 comments about Applied Cryptography: Protocols, Algorithms, and Source Code in C, Second Edition.

1. This book is now in the thirteenth reprinting of it's second edition with more than a hundred thousand copies sold. It is the definitive book on cryptography from the standpoint of a general overview of what sending secret messages is all about. It is not specifically oriented to the developer, but is more general in nature. There is not enough here for the mathematically inclined to seriously research the background of all the various systems.
   
   As such consider this to be an introductory book on cryptography in general with a bit of history, a bit of story telling, an analysis of various cryptographic protocols and systems. There is source code provided for nine common protocols, and an invitation to order a three disk system that has source code for several more algorithms, functions, systems and additional text on various subjects. This disk set can only be sent to US and Canada addresses because of export rules on cryptographic information.
   
   This is the definitive book on the subject. The only complaint I have is that it could stand to be done over in a third edition that would bring it more up to date.



2. Great Book! The author's style makes this very easy to follow, and he frequently clarifies on topics which are difficult to grasp. Most importantly, he writes from a practical point of view; the material is very grounded and applicable instead of being a math textbook. That being said, he cites over 1600 sources; the book is riddled with leads to sources with more complete coverage for those interested in the fine details. Though I have some programming experience, I don't intend to write any programs; but it is interesting to read the logic in code. It was my goal to learn about modern cryptography and I have achieved that and much more.



3. This book is extremely complete. It briefly covers the history of cryptography. It describes the political implications of cryptography and finally it shows how cryptography can be used in applications and presents the different cryptographic algorithms.
   
   The algorithm section starts with a number theory primer.Honestly, I have found it a little bit too thin to learn all the needed background to fully understand the algorithms but on the other side, you cannot expect a simple 600 pages book to provide that background in the latest mathematical research number theories. It has at least the merit that it did stimulate my curiosity about number theory when I have read the first edition of this book.
   
   Another point that makes this book interesting is that at the end of each chapter presenting the various algorithms in a given category, you will get Bruce Schneier opinion on which algorithm is the best. Of course, this type of information usually become outdated real fast but it is interesting to follow his thought process and test his predictions as the book grow older.
   
   So, if you are looking for your first cryptography book, it should be this one.



4. Sadly, this book is more than a few years old. That said, it is still the finest single volume introduction to data security in the modern age. For clarity of description, for illustration, and for its success at communicating essential concepts and ideas without resorting entirely to mathematics, it is without peer.
   
   Every so often I look on Amazon and hope that I'll find Schneier has penned a third edition, updating this work with the results of the AES selection process and all the other recent developments in this suddenly fast paced field. Alas, I don't think that's going to happen. But I'm not sure that it would really make any difference -- the field now evolves so swiftly that any detailed, thorough volume would be obsolete by the time it reaches the shelves.
   
   So instead of looking for something more recent, pick up Applied Cryptography. Read it and keep it close at hand as a reference (mine is almost falling apart from years of loving use). Nothing presents the fundamentals as well. If you need to know about a new cipher, a new hash, a new encryption mode or protocol, that's what the Internet is for.
   
   But to really understand the underlying ideas, techniques, challenges, risks, and rewards of cryptography, nothing finer exists.



5. Applied Cryptography is a classic book on how and why cryptography works. It is written very clearly and explains in detail how various aspects of cryptography work.
   
   Some math-based sections are included, but overall math knowledge is assumed to be minimal. Overall, the book is very consitent in how much it expects the reader to know, few sections are much more advanced than others.
   
   While not up-to-date with the latest algorithms and available computing specifications, it focuses as much as possible on the timeless aspects of cryptography. A recommended read to all aspiring cryptographers.

5 comments about Programming in C (3rd Edition) (Developer's Library).

1. I haven't spent much time with this book but I wanted to make sure others didn't experience the same surprise that I did with this book. I bought this book via the marketplace link above, and was shocked to find it is a book written in 1983 (mine is a 1987 reprint of the original edition). I thought the seller had listed the book on the wrong page, since the Amazon page says it was revised in 2000, but the ISBN # is the same...



2. For an experienced assembly language programmer looking to apply C programming to embedded systems, this book has just the approach that suits my needs. Logically organized and very readable, it keeps layering concept upon concept, subtley bringing in different techniques, while informing not only about the language, syntax and use, but also about how compilers interact with various constructs.I also enjoyed the well thought out example programs and exercises.



3. Great explanations, accompanied by good examples. Definitely a must if you're new to C. I've had experience with C++, so the concepts weren't anything new, but the syntax presentation for C was clear. Get it, it's cheap compared to other books.



4. First and foremost, this is an excellent book. Everything is explained very well with not too much "fluff". I found a few errors in the text but that's to be expected in any programming book.
   
   Now the reason I gave it only 4 stars is because of the style of the code. He uses "thisVar" or "this_var" in programs and many times uses both in the same program! The same for braces. He goes from same-line braces to line-after braces many times in the same program!
   
   For those unaware, that's:
   
   blahBlah {
   ....
   }
   
   and
   
   blahBlah
   {
   ....
   }
   
   This doesn't affect the functionality, but when coding in the real world you need a consistent style. These are the only issues I have with this book.



5. This was the only text required for my college level C-Programming Course. I honestly didn't read as much of it as I should have. I did feel that most of the examples were thorough and helpful.

5 comments about Programming 16-Bit PIC Microcontrollers in C: Learning to Fly the PIC 24 (Embedded Technology) (Embedded Technology).

1. I have thouroughly enjoyed reading and using this great publication. It is absolutely the best introduction to PIC24 in particular and C30 as well. This book makes a great companion for the Explorer 16 development board from Microchip.
   I look forward to a follow up edition with a few more projects and peripheral code segments.
   
   Very Well Done Lucio



2. I already had a problem to solve in my mind when I statred to read this book. The book worked out for me in two ways: First, the topics of the book cover my problems very well, and secondly the code in the book worked well as I tested them project by project as a learning process. Also, I agree with the points other reviewers made before my review. So, no need to repeat them. I am not an EE and new to microcontroller. To understand a topic of the book I still need to cross-check some sections in the data sheet of a PIC24 and its corresponding C header file. This slows down my reading, but turns out to give me a better understanding. I completely recommend this book.
   
   David W. at Ferndale, MI, USA



3. I've bought several books on microcontrollers, and most of them have been poorly written. This book is exceptional: the writing is clear, it has been professionally edited, and the audience focus is clearly stated. It contains a lot of valuable background that only someone who works at Microchip would know.
   
   I have to take off a star because the book does not mention the numerous hardware problems these microcontrollers have. All microprocessors have some issues, but the errata for PIC24F parts is unusually lengthy. Jasio neatly sidesteps the hardware minefields, for example by using an SPI communication protocol rather than the more elegant I2C. Don't get me wrong: I'm a big fan of these parts, and I think everyone who designs with microprocessors should look at them seriously. Still, I can't believe that someone could write a book like this and not mention the errata.



4. I WAS REFERRED TO AMAZON.COM TO PURCHASE THE BOOK. TRUSTING MY FRIEND WHO REFERRED ME THAT THEY ARE A REPUTABLE COMPANY, I TRANSFERRED THE CASH FOR THE PURCHASE. AMAZON CONFIRMED HAVING RECVEIVED THE CASH AND PROMISED TO SHIP THRE BOOK IMMEDIATELY. THAT WAS MORE THAN A MONTH AGO.
   
   I HAVE NOT RECEIVED THE BOOK YET AND HAVE CHECKED WITH ALL THE SHIPPING COMPANIES IN SOUTH AFRICA (BEARING IN MIND THAT AMAZON.COM IS UNABLE TO PROVIDE A TRACKING NUMBER). THE BOOK HAS POSITIVELY NOT ENTERED INTO THE COUNTRY THROUGH ANY OF THE ENTRY POINTS.
   
   NUMEROUS E-MAILS SENT TO VARIUS E-MAIL ADDRESSES AT AMAZON.COM FAILED TO PRODUCE ANY RESPONSE FROM THEM. I DESPERATELY NEED THE BOOK, AND IT SEEMS AS I WILL HAVE TO FIND ANOTHER SUPPLIER WHO CAN DELIVER BEFORE THE BOOK IS SO OUTDATED THAT I WOULD NOT WANT TO READ IT ANYMORE.



5. This book pretends to be a programming book on the PIC24 16-bit microcontroller family from Microchip. And if it were only that, it would easily earn a 5 rating. But the author has gone way beyond his calling. He turned this into a real insider's view of what gcc is doing under the covers with this MCU. This is better than good because there are so few good books on embedded C programming, and none of them do a good job of showing both sides. As a C programmer you normally don't care what the computer is doing under the covers. But as an embedded C programmer this is critical information! So I'd like to give this book a 10: 5 for PIC24 coverage and 5 for under-the-cover info on what gcc is doing. Even if you don't use the PIC 24, you need this book!

5 comments about Operating System Concepts (7th Edition).

1. I had to buy it for the course, but I really prefer Tanenbaum books, you can find more science. Pages reflect light so you should have indirect lighting, I had difficulties reading it.



2. This book is very informative if your interested in learning how operating systems work. Unfortunately, Im not really interested in it, I just have to read it for a required class. The material is very dry so its hard to focus on what your reading.



3. I have been using this book for my master in IT science and it has been a great help in my studies. I hardly have to go elsewhere for research; its content is very clear and very concrete. I have to say that this book has added a great value to my studies.



4. This book offers coverage of issues encountered in designing an operating system, but does this in a rather dry and uninteresting manner, using examples and diagrams which are somewhat contrived and confusing at times.
   
   Its code snippets are often incorrect and shows no sign it has ever been checked for correctness. I am basing this assumption on the fact this is the 7th edition and blatant errors still exists. Errors range from syntax to logic errors, both in the explanations and code provided.
   
   The book also does not explain certain algorithms, and merely prints them in pseudo code, then moves on with not insights into the how and why of it.
   
   If you have no other choice, then this book will suffice as long as you take what it says with a grain of salt, and apply your own logic rather than take what the authors say as gospel.
   
   Cheers,
   Steve



5. That uses this as it's text, be worried. The book is decent, but definitely just "concepts," no intensive knowledge is conveyed in it's pages. Oh well.

5 comments about C Programming: A Modern Approach, 2nd Edition.

1. This is the second of King's books I have purchased. It is also the second that I am very very pleased with.
   
   This book presents a quick systematic clear way of learning to program in C period. This has to be the easiest programming book I have ever read that goes beyond absolute basics.
   
   Frankly I don't understand the few negative reviews others have given the book. Yes it would have been nice to have answers to the exercises. However this is a programming book, you get the answers yourself by doing the work. Mistakes are readily apparent, simply because it won't work!
   
   In terms of difficulty, the exercises are doable. There have been a few that did stump me.....for a little while. With a bit of rereading and some experimenting, I have managed to answer all that I have attempted.
   
   Do yourself a favor if you are learning C and buy the book either as a stand alone or as a supplement to another book.



2. This is definitely the best book on C that I have ever read. King presents just about everything there is on the language in a clear and easily understandable way. One thing that I loved about this was King's mentioning the %g format specifier, which is something that has been very useful and that I haven't seen mentioned too frequently.



3. in order to really understand what was going on you need to intently read every single word. There are no solutions for the excercises which i thought were too difficult, and many times the means to find the answer could not be found in the chapter.



4. This book was an excellent complement to the professor I had for basic C programming. I'd venture to say that even someone with little to no computer experience could learn from it. One really nice feature is the Q & A section where obvious questions about the material are asked and then answered by the author such as: "Why is the C language so terse?" There is not an excess of information, but it gives a great deal of examples and even source code so you can see how the system compiles it. If I were teaching myself the C language, this would probably be the first book I went to.



5. I ordered K.N. King's ``C Programming: A Modern Approach (Second Edition)'' from Amazon for my recent birthday. Having had more birthdays than I care to admit, this gift to myself is right up there with a Lionel train set I got for my eighth birthday (not from Amazon, of course -- it didn't exist that long ago but passengers trains sure did :)).
   
   In this second edition, I think that KNK is now the logical heir to K&R. That's not meant as blasphemy -- Kernighan and Ritchie's still great volume is around 20 years of age and it's unlikely they'll be getting together for K&R3. The C language has undergone enough changes (with the amendment of 1994) and C99, that a ``Modern Approach'' really is needed.
   
   There's another author familiar to readers of the comp.lang.c newsgroup for his approachable, engaging writing style. That author is a wonderful writer but doesn't let the truth get in the way of good narrative. King, though, is an equally engaging writer but is obviously passionate about correctness and adhering to the C standard. He's also meticulous about portability so that the examples are written in pure C and not some platform-specific variant.
   
   I've the entire book and can find hardly anything even nitpick. Aside from a minor style difference about using parentheses with the ``sizeof'' operator, which King explains his rationale for doing so, that's about it.
   
   His explanation of C99 (and the differences from C90 are clearly indicated) made me aware of some really nice features of the current standard for the language (and makes me wonder why one very notable compiler implementer hasn't yet supported C99).
   
   In short, get this book. The Q&A sections at the end of each chapter are very well done. The exercises and programming projects help to amplify the material presented. And King's examples will teach you more about barcodes and ISBN numbers than you ever thought possible.
   
   If you can appreciate the work of a fine craftsman in film such as Martin Scorsese, you'll find that King is of that caliber in the realm of lucidly dealing with this technical subject.

5 comments about Effective STL: 50 Specific Ways to Improve Your Use of the Standard Template Library (Addison-Wesley Professional Computing Series).

1. I tought I knew STL but Dr. Meyers showed me how little I knew. His in-depth analysis and numerous examples gives new insight into STL and how to best implement solutions using it. This is a must-have for every C++ programmer/software engineer.



2. I really enjoyed to read this book as it contains very good tips. The only detail that annoys me a little bit is the amount of cross references between the items. The author first 2 books were a little bit like that but it seems to me that this one is too much. I would have prefered to have items more self contained. If you want to refer to a particular item, this one will refer to 2 other items that will refer to some more items and so on to the point where if you would like to close the open loop, you would need to consult all the items.
   
   Except for this small annoyance, this book is very good. You should read it or have it.



3. The man Meyers has worked his magic on the STL. If you've read Effective C++, then you know what to expect, and should invest accordingly. Meyers is on top of his game, finding the right balance of sage advice and dry wit as he guides you through the complexities of the STL. If you haven't read Effective C++, you really ought to before reading this one.
   
   A wide range of advice is dispensed, including: advice on what containers to use, range member functions, avoiding loops, erase-remove, auto_ptr, associative containers, equality vs equivalence, gotchas like const keys in sets and maps and references to reference problems, efficiency in sorting, searching and inserting, iterators, functors and adapting them.
   
   Phew. A lot of ground is covered. You will want to be familiar with the structure of the STL, I don't recommend learning the STL from scratch from this book, and you may want a good STL reference. But those aren't half as much fun to read as Scott Meyers.



4. What a great book! Helped me get past mental blocks on using the STL.



5. I would suggest this book anyone dealing with STL. It provides extensive best practice input for the experienced C++/STL developer.

5 comments about Absolute Beginner's Guide to C (2nd Edition) (Other Sams).

1. As an IT professional I have read many programming books. Many of which in their attempt to teach you something about their topic end in more confusion than clarity. Not so with this text. This is one of the only texts I have encountered that actually reads as it was described, assuming no programming experience yet having the ability to teach you practical implementations of the language. I found this text to be a fun read, not overly technical (it is a beginning level text) and very much worth my time and effort. I would highly recomend this text to anyone just starting out with C, it will give you the core understanding of concepts you will need to advance your C programming abilities. Nice work Mr. Perry.



2. The author did a great job of explaining in this book. It was very easy to understand and enjoyable to read. I highly recommend this book for a true beginner. Also, the author includes a helpful and handy "Crib Notes," which is a tear out reference sheet of Functions and Statements covered in the book. No doubt, I rate this book 5 stars!



3. Hi, my name is Adrian Mowrey, and I'm a computer programming student. I always wanted to learn C, but I couldn't because I wasn't able to find a good reference for beginners until I found this book. Another thing that made it harder for me to understand other books is that English was not my first language, and many other books talk too technical for me to understand. This book is much easier for someone, like myself, whose first language is not English. After I read this book, I decided to move forward and order "The C Programming Language" by Brian W. Kernighan and Dennis M. Ritchie. I hope I will advance to a respectable level from where I can build my personal ideas with C, and I'm sure I won't have any problems since I have these two books.



4. This book is extremely simple and by far too verbose.
   
   Book is about 360 pages which could easily be fit in 90 page none-verbose version. Still good start if you are absoutely new to C.
   
   To be more specific, this book doesa good job to defining compplecated C terms like Stack/Hip and dynamic memory allocation.



5. Greg Perry has a way of teaching complex subjects to absolute beginners. This book is easy to follow even if you've never programmed before.

5 comments about Agile Principles, Patterns, and Practices in C# (Robert C. Martin Series).

1. First, this book is well written and presents information in a constructive manner. It is well thought out, and is not just another C#/OOP/XP book.
   
   Now for the bad news. One unnecessary oversight is the use of casts and "object" in some examples. Any author writing any C# book since 2005 must know that these idioms should no longer be encouraged. It is unacceptable for a book published in February 2007 to possess this flaw.
   
   Generics, used in moderation, result in cleaner code that is also type-safe, and usually performs better due to the absence of boxing/unboxing. The authors should consider posting alternative examples that favor Generic types and collections on their errata web page. If you purchase this book, you would be well-advised to review the examples with a bias against the use of casts and the word "object".
   
   To be entirely frank, I don't see how other reviewers can justify a five star rating.



2. Simply the best treatment of object oriented design, patterns and practices I have ever read. Extremely well organized and easy to read. Should be in every software engineer's library.



3. I have purchased and read alot of books on software design and development over the years and I cannot think of a single one of them that I would rate higher than this one.



4. Very readable, entertaining, useful. One of the few books that has been easy to follow and enjoyable to read. Very good general coverage.



5. Agile practices and design patterns written in a clear, concise way. Granted there are a handful of mistakes throughout the book, and the occasional awkward reference to a pattern that won't be covered for another 5 chapters, but they're easy to spot.
   
   The information is presented just right - a little background info, succinct descriptions, and simplified code examples. Outstanding.

5 comments about Accelerated C++: Practical Programming by Example (C++ In-Depth Series).

1. I have purchased about 15 books on C++ and this was hands down the best. As the description says, it is more top down than bottom up. There are thousands of features of C++. You might even use some of them in a program. This book gets you programming immediately using the more important and commonly used C++ functions and explaining in actually pretty gory detail what they do and how they do it. I found it utterly approachable and useful from the first page on.
   
   You can always by a reference to look up more features as you need them. I really liked this book and I think its approach is actually seminal. This is how teaching programming should be done.



2. They have got magic lamp to capture C++ gene in a very small book. You need to have some programming experience before you start since it goes from 0 to 80 mph in 7 seconds (chapters) like a sports car. And surprisingly you catch every thing on your way. They read your mind and explain it before you draw wrong conclusions.
   They do not spend useless time on "Primer" details though it starts from basic programming constructs. Try it...



3. This is a great place to start. Iterators, templates, then pointers... That's a different approach. Each topic is explained well, though the author gets bogged down in the details of his ever expanding example. Never-the-less, templates are my friend. I can build my own with the power of pointers and convenience of iterators.
   
   You'll inevitably need authoritative books on C++, OOP, and MFC to do anything useful in Windows. But this is a great intro to the C++ language and STL.
   
   Cheers!



4. First of all, I'll say what's good with the book. The author's way of writing demands that you learn C++ terminology quickly. This, infact, annoyed me because the terminology does not interest me, and I was more interested in the concepts, but by forcing me to follow the wankish terms, I am better able to understand other programmers. The book is also good at not dwelling on the same subject endlessly for the most part. However, I think some of the concepts should have been explained more while others were needlessly over explained, but that may not be the case for a different reader with different strengths and weaknesses.
   
   Now comes the bad. The student grading project, which is changed throughout many of the chapters is horribly boring. It is harder to focus on what you're reading when what's being explained is so incredibly trivial and unimpressive. The biggest beef I have with the book is the exercises. Ofiten times the hardest part with the exercise is figuring out what the exercise actually wants you to do. Also, some of the exercises require knowledge not yet covered in the book, and sometimes even things never covered in the book at all. To top it all, the authors provide no answer sheet to the exercises to even check your solutions. The exercises are simply not thought out and are poorly explained.
   
   I got the book to learn from, and if the exercises demand I learn stuff outside it then it's not being useful. The book is the first in its series, and the first few chapters of the book are aimed at complete beginners, so the expectation of prior knowledge is a little absurd.
   
   As far as the criticism from some of these surprisinginly positive reviews go about not knowing what input to give the student grading program: By the time you enter all the code, you were explained how all of it worked part by boring part. If you truly knew how it worked then you should know what input it expects. Pretty obvious, really.



5. I do not understand how some people can give negative reviews for this book. This book is MUST have in case if you want to get basic to intermediate level of C++ programming.
   
   I wish they publish something for advanced level programming.
   A+