5 comments about Using C++ (Using).

1. With a first glance I could capture atleast 3 errors from the pg #312 to #314 in the chapter Beyond the basic. But I found very simple explainations of concepts like template and namespaces. Good book to understand concepts, may need little tweak in for the example code.



2. Very easy to read. Easy to understand explanations of difficult concepts in most situations. Quite comprehensive. Nice big margin to scribble notes in. Useful codes samples. Good price. A good starting text or support text.



3. This book is a good one for people who has never before programmed in C++. For those who has done that, I would not recommend this book. Then you should read C++: The Complete Reference instead! The explanations of templates, namespaces, exception handling and operator overloading are a little too simple for me. Also, the last part of the book, The Standard C++ Library, breaks the tutorial form of the book into a pure reference form!!! One of the programs has a very nast bug in it that should have been checked. It completely crashed my system, and I spent the rest of the day figuring out what went wrong!



4. Lots of typos and code errors make this book more difficult to follow than it should be. If you've got some programming background, then you'll catch them easily, so they'll be a nuisance rather than a serious source of frustration. The code examples are also rather trivial. It's not so helpful to see a fully coded and commented example of assigning a pointer, when it's already been presented in the text. Better to see a program that does something useful. The book could have been shortened by 200 pages by omitting excess whitespace and useless code examples. Straightfoward prose explanation seemed to suffer in places. Overall, a pretty good intro to OOP; not a terrible book, but you could probably find a better one.



5. It's hard to find a good c++ book for beginner programmers. Most C++ books assume that you are fimilar with c but this book doesn't required you to know c, it guide to step by step from gound up. I'm teaching myself VC++ using this book. Recommended to all beginner C++ programmers! Ivor Horton's "Beginning Visual C++ 6" is all highly recommended.

5 comments about C++ In Action: Industrial Strength Programming Techniques (With CD-ROM).

1. If you want to quickly get your hands dirty this is another book introducing you to C++. If you are easily bored this is a good book. On the other hand if you don't know anything about programming and you are the type who learns by repeating the same stuff over and over, you can try the Deitel&Deitel alternative...



2. The first part of this book might just as well be skipped through, basics of C++ are given there in such a convoluted (iconoclastic as Bartosz puts it) way that those don't know the basics, wont get anything there. Only those who already know C++ will be able to understand this part, but they actually dont need these basics.

   The rest of the book is extremely valuable: explanation of Windows programming, thoughts about writing maintainable and reliable code and organizing software projects. For intermediate level C++ programmers like myself it's a real treasure trove.

   I still cant believe that English is Bartosz's second language, it's impeccable. Nevertheless, the style is a little bit too sophisticated and assumes a very bright reader. For example Bartosz often gives you a lot of new material and saves all the explanations for later, so you have to go back and forth trying to piece it together. I would give explanations first, and also slow down a little, offering new concepts one at a time.
   Overall - good job.




3. This is the ONLY book I could get hold of that actually attacked head-on the problem of using C++ and Windows without abandoning object-oriented design and sanity in coding. Maybe Jeffrey Richter has done something as good - I don't know - but I bet he takes three times as many pages to do it. You can work through this book or just read it but either way, your C++ & Win32 skills will be greatly consolidated.

   The associated ReliSoft website is well worth a look, with some lovely sarcasm about MFC that didn't make it into the book (plus extra stuff on threads, etc.)




4. For any developer that have had the displeasure of working with Win32 API and/or MFC in C++, this book strikes a very sensitive cord. For the uninitiated, Win32 is an OO programmer's nightmare, and trying to build a decent OO framework on top of it is a Herculean effort that few has dared to attempt. MFC is better, but marginally so, as it ascends Win32 from a nightmare to a very bad dream. The lack of proper standard libraries for other facilities such as threading, sockets, etc. only adds to the hurdles that a C++ developer needs to overcome in order to implement the most trivial functionality in his or her program.

   And along comes this book with the attempt to build an OO layer that encapsulates the horrendous details of the Windows API. Of course, only a limited subset of this monolithic API is addressed in the book, which is understandable. One might consider the whole subject of the book a case study rather than a shrink-rapped solution, which is well-worth the time and money spent on it. If you have programmed with either Win32 or MFC before, and have being stung by their awkward design, or lack thereof, then consider this book a mandatory reading assignment.

   However, the main problem with this book is that it attempts to be a one-size-fits-all material. The first chapters vainly try to introduce the reader to the C++ programming language. And the remaining chapters are bloated with subsections covering the finer details of the language as they are needed. The whole assumption that a total C++ novice can understand the Win32 API (the problem), the OO layer (the solution), AND the C++ programming language along the way is a very ludicrous one. A novice will struggle endlessly with it, and will ultimately find him or herself given up and reverting to more classical texts on C++ and OOP before being able to stomach reading this book again. Alas, the wasted space on introducing C++ could have been put to better use by adding more depth to the material.

   So, you might ask why the four stars. The subject matter is unique and direly needed. And the coverage is adequate if you realistically set your expectations. By all means, buy it and read it. You might find it useful or at least enlightening. I know I did. But don't come unprepared.




5. Buy this book if you are an intermediate in C++ and want to become a GURU in C++. I know i did.
   
   Thank you "Bartosz Milewski" for making this amazing book.

No comments about Turbo C++.

No comments about Practical XView Programming.

5 comments about Sams' Teach Yourself Advanced C in 21 Days (Sams Teach Yourself).

1. This is a great book for learning some advanced C programming. Highly recommended. I can't believe someone would give this book 1 star because they didn't grasp the concepts. That this book is ADVANCED enough to thwart the learning efforts of a beginner makes it worthy of its name. In my mind, this is a praisworthy trait for a book to have (truth in the title).



2. Gone are the days of DOS console programming. You dont see the types of interfaces that are used in this book anymore. So why is it so good? It teaches some advanced concepts and libraries used in C. Also, you never know when that legacy app will need fixing I found the subject material facinating and learned alot about putting together a database program without a fancy RDMS system. Something that can carry over to my JAVA programming world.



3. The C in 21 days is really a good programming book which provides example, coding, explaination and many more useful exercise. Then, the Advanced C is my next programming book, I'll more expert in C and many more. Explore it today !

   Remember, C IS FUN!




4. This book is fantastic! Previously, I had difficulty with concepts such as pointers, arrays and structures. This book clearly explains the differences, provides excellent examples and also includes good programming advice. I have compiled many of the example programs and they are highly instructional. Each example includes an analysis section that explains the examples by line number which is also extremely helpful. The book is well laid out and each section begins with a checklist that tells you what to expect to learn for that section. I highly recommend this book! Compile the examples and you too can learn C!



5. I started reading this book and the topics didn't seem to me that advanced. Also, I had to debug every code example in the book so far just to get them to run which I guess is a learning experience in itself. I guess I just wasn't that impressed.

5 comments about The C++ Training Guide (Training Guide Series).

1. Every book has things that I don't like and this book has a few. But, compared with ALL the other books I have tried to read, this one is head and shoulders above the crowd. The disk comes with a C++ compiler so you get everything the book tells you that you should be getting. I needed that comfirmation as a confidence builder; I learn by doing. I learned C++ and I am moving on to Heller's "Who's afraid of more C++?," which is the sequel.

   Just another note: Heller doesn't just teach the syntax of the language, he teaches you the details of programming. He taught me hexidecimal math. He helps you understand how the C++ is translated by the compiler. I have never seen such a generous discussion in any C++ book. Which leads me to my complaint... I am impatient and all these details took some discipline. If you want to benefit from these chapter, some of them require a good deal of thinking.

   I am sure that I am much farther along because of this extra information. And maybe my programs won't generate so many General Protection Faults as a result of that discussion.




2. sir/madam,

   I am in the starting stage in c++. Please send c++ programms and Notes.

   Thanking you, Lakshmanakannan.




3. I have not read this book. I don't know alot about programing. I know some HTML and a little Javascript. I know alot about linux and unix but zero C++. I really need to know if this is a good book for a begginer like me.



4. If you are looking for a real book plz don't choose this one. I felt really cheated... it is very very very very beginner ... and the way it is written is very poor.. even the fonts are misrable ....



5. The C++ Training guide is an outstanding book for a beginner who wants to learn programming. Here is why:

   - Crystal clear description of how program code actually works, all the way down to the hardware level (machine language, bits, registers, etc.). - A clear relation of how the various C++ "tools" can be applied in programming, as opposed to simply listing them and how to write them. - The inclusion of dialogues between the author and a novice using the book. An author can easily take for granted that something he understands is just as clear to a beginner. These dialogues help point out and resolve conceptual obstacles the author would not have thought of. - The use of concrete examples to illustrate points. - The provision of a compiler (on a companion CD). - The inclusion of exercises to try your skill, with solutions in the text. - Incredible detail and completely thorough coverage. - A friendly, conversational tone that makes the book a pleasure to read. - Clear, down to earth language. - An author who is INCREDIBLY accessible. I had a lot of problems with installing and setting up the compiler. Steve exchanged a number VERY detailed e-mails with me, sticking with me until it was completely resolved. He is amazingly patient.

   Steve Heller loves programming, and has a natural talent for explaining things. This book was wonderful not only because it teaches the nuts and bolts of the C++ language, but because it shows how it all actually works in the computer, all presented in a straightforward, logical manner, that makes it quite enjoyable to read. It is almost like reading a novel.

   I noticed another review that knocked the writing, and complained the skill level was for beginners. That reviewer must be a plant. I am a writer myself, and can attest to the high level of the writing. As to the skill level, it says on the book that the skill level is "Beginning/Intermediate." Go figure.

5 comments about Professional Software Development with Visual C++ 6.0 & MFC (With CD-ROM) (Programming Series).

1. If you are new to MFC and Visual C++, this book will help you. When you want to start learning why some things are done a certain way, you are out of luck.

   This book will walk you through the basics of using the MFC in Visual C++. You will learn the steps you take in VC to do basic component manipulation in MFC but only on the surface. The examples are not really that good. Sure they convey the principle but that's about it. I found myself with more questions to ask and no answers to be found.

   If you have never done any MFC programming before, this is a good place to start. Otherwise, my advise is to keep looking.

   -=} Randall {=-




2. This is a terribly organized book.

   1. There are lots of errors and inconsistency, which cause lots of confusion. I've only reached chapter 5 and already noticed these errors:
   1) Page 57: the book shows you how to create a "CDataDlg" class, however, on Page 60, inside the code: "CDlgData dlg(this)" - the class name becomes "CDlgData" and this error repeats on Page 61 too;
   2) Page 68: "1. From ClassView, select CDlgData" - well, the figure actually shows "CDlgNew", not "CDlgData" and this discrepancy repeats several times in the chapter;
   3) Page 69, in the code "m_csLastname = "Jones";
   m_edtLastnaem.SetWindowText("Jones");" - the first line is totally unnecessary, besides, variable m_csLastname is not declared so if you follow his code closely, the program won't work.

   2. Looks like the author isn't very sure what type of readers he is addressing:

   Page 57: "6. At the end of this line press [Enter]...The cursor will be placed immediately below this line..."

   Looks like he thinks his readers are bunch of [people] knowing nothing about how to use a text editor, not to mention C++ and we need to follow strictly his explanation. Well, if we really follow his book so closely, we will definitely be frustrated by these errors mentioned above.




3. First things first, if you are a beginner my advise is to read books for beginners then move on to MFC books for the advanced. I noticed in a lot of reviews people seem to think that one book is all they need and expect one book to do it, but the sad thing is they end up using the book as a paper weight or they stop study the language because they got the wrong book, or they get confused. If you study and learn any language in the right order with the right books its hard not to enjoy! Read C++ in 21 days, second edition, by Jesse Liberty. Get through Jesse's book on the C++ language first then move on to learning Microsoft Foundation Classes (MFC). Then read C++ 6.0 in 21 days by Davis Chapman to get some of the MFC learning. Then read everything on advanced Visual C++ 6.0 to enhance you MFC understanding. Now you will have to add all these books to your library reference because it seems one book on C++ 6.0 will not tell you everything you need to know because when you start your own programming you're always do something different than what these books seem to cover and guess what? That's right, you will have to figure this out yourself by referencing more than just one book. Example: I needed more info on property sheets and finally found it in MFC Advanced, which is now discontinued for now on Amazon. This book Visual C++ 6.0 & MFC has some good info in it but it's short on detail but I will have to say it's a good book to help build your library on this subject. I had a problem with property sheets and this book did not cover enough to help me with my problem. It uses a control button you click on a menu to pull up a tabbed property sheet and I wanted to convert my main dialog class to a property sheet class to build my application instead of having the property sheet added to my application in a menu control. But I learned from its CTime class on how to display clock time in a better format. Did find some errors but that seems to happen in most book anyway. So, I give this book 3 stars because it doesn't cover enough in-depth information to be a professional software development book.



4. I think that this is a grate book for beginers. It gives you examples of almost everything you need.



5. This is a very poorly written book. If you follow the instructions, none of your programs will work. If I could give it a ZERO stars I would. I wasted my money on this book.

5 comments about OLE DB Consumer Templates: A Programmer's Guide.

1. With high hopes, I bought this book. But it has been a big disappointment. The book explains the concepts of OLE DB templates and the various macros, quite well. Lot of figures explaining the relationship between objects. But it is very much lacking on real usable examples. There is not a single complete example. Most examples are real simple. Inserts and Deletes get just one page each, hardly useful, and also the example used for these is with a CTable. How many people use a CTable for inserts and deletes? It is like saying "Delete/Update the first row in the database", which is hardly practical. There are about 30 OLE DB types, but no examples on how to use these. In summary, the book is better than the SDK documentation on OLE DB templates, but not much useful if you want to get into OLE DB programming quickly.



2. The coverage for basic OLE DB is not good in this book. To get a decent coverage of this in my opinion you can do no better than: "Beginning Components for ASP" which not only explains basic OLE DB well, but also explains MTS and Writing components for ATL to work with ASP amongst other things.



3. This book isn't exactly what I had hoped for. It seems that only about 30% of the book is actually devoted to "Consumer Templates" and the other 70% talks about raw OLE DB interfaces. However, since it is the only book that covers anything on consumer templates ... it is better than nothing.



4. As you can see, there are not many books on the subject. However, this book contains very few code lines and it is not organized well. The fact that a programming book does not have even 1 (!) full example can't be good. You will get a fair amount of information from this book; however, YOU WILL visit MSDN regularly. The author spend time on known subjects like performance again and again (although that C++ programmers are well aware to this subject) and less to the whole concept of the templates. He is breaking up all the objects very well, but failing terribly in providing the whole system. A "nice to have" book as a second or third reference. Don't buy it as first.



5. I am by now several months into a project using the consumer templates. I have to say at this point that the decision to use them was the biggest mistake I have made on this project. They do not make the grade and it is too late to back out and user another interface.
   
   The templates would be a good idea if carried to completion and fully supported. They are not. The template classes Nallet presents are not a full wrapper, but just a series of incomplete examples. They do not compile under newer versions of C++ and must be hacked just to build. Each hack in turn produces more problems. The publisher's web page no longer contains any reference to this book, nor to it's source code. The author's web page is "404", and the code exists on the Internet only in "pirate" sites. I have turned up references to the author through search engines but see no sign he is maintaining his code.
   
   Microsoft is in the process of abandoning OLEDB in any case in favor of ADO.
   
   In short and in other words: DON'T BOTHER!!

1 comments about C by Example/the Easiest Way to Learn How to Program! (Programming Series).

1. The easiest book to read and understand of any programming language I have read.

5 comments about Professional .NET for Java Developers Using C#.

1. I've been working with Java and JSP Pages for a few years but my company's looking more and more at .NET and I was told to look into it. I'd heard a lot about it's similarity with Java, and so this book seemed a natural starting point. I wasn't dissapointed. It quickly ran through the important parts of .NET and how they related to what I already knew in Java: C# instead of Java, ASP.NET instead of JSP, ADO.NET instead of JDBC, etc.

   It was a quick book to work through (just 400 pages) but now I've finished it I'm writing my apps just as easily with .net as I can with Java - and there are some things like binding to data in web apps that are even easier to do. And I've been able to put together some .Net prototypes for my manager in just a few weeks.

   If you're looking for a overview of .NET and don't want to wade through a lot of stuff you already know, you won't be dissapointed with this.




2. This book is great in its ability to port the Java programmer quickly over to .NET by explaining and comparing the concepts to Java.

   C# is so similar to Java that this book fits the market perfectly by not re-explaining the wheel, but rather focusing on the API's and resources available in .NET and how they relate to those that are available in Java.

   Also in true Wrox fashion, the book is heavy in the code examples department.




3. This is Wrox at its best - working code explained well by working programmers. This book provides the easiest way for a Java programmer to learn the basics of C# and the .NET environment including ASP.NET and database access with ADO.NET. Using this book and freely available software (.NET Framework, SharpDevelop, Web Matrix and MSDE) you have a complete environment for learning .NET for less than $...- hard to beat.



4. What really blew me away was the fact of having a full chat client and server code with step by step explanation in the remoting chapter to give an idea of Java developers that are accustomed in writting programs in RMI.
   Excelent Book!!!!



5. I bought this book on a whim, as it was bundled in a 2-for-1 offer along with the book I was actually interested in (whose title I don't currently recall). Having worked as a Java developer for a number of years, I had recently accepted a job as a C# developer, and thought that I'd buy a book to pick up the basics. In that context, and in accordance with the book's title, I was looking for the book to serve two main purposes - 1) To walk me through the basics of the C# language, pointing out the similarities and explaining the differences between the two languages. 2) To describe how functionality available through the (familiar) standard libraries in Java can be achieved through the (unfamiliar) .NET libraries using C#.
   
   To satisfy the first purpose, I was hoping for some detailed chapters on the core language. Sadly, only 'Chapter 3: Language Syntax' covers this subject, and does so in a mere 47 pages. Of these few pages, I generally found that the discussions were targeted too much at a novice programmer, rather than someone who already has programming experience in a language that is very similar to C#. For example, the page and a half that covers Exceptions simply described what Exceptions are for and how they are used. I already know what they're for and how they're used - I'm a Java developer! It would have been more useful to concentrate on the minor syntax differences, the fact that all Exceptions are unchecked in C#, and that C# doesn't make a distinction between checked Exceptions, runtime Exceptions and Errors, as in Java. Perhaps as icing on the cake, a table of how some commonly used Exceptions in Java map to the commonly used Exceptions in C# (e.g. NullPointerException to NullReferenceException, IllegalArgumentException to ArgumentException or ArgumentNullException, IndexOutOfBoundsException to ArgumentOutOfRangeException) would have been nice. Alas there was none of this.
   
   Multithreading is another key area of the languages that differs between C# and Java in a number if significant ways. It's such an important aspect of modern programming that most programming books tend to devote an entire chapter to it. Fair enough, for a language conversion book rather than an introductory programming book, I wouldn't expect an entire chapter devote to it. I would expect at least something on the subject, however. Sadly, this book contains nothing. Absolutely nothing! Nil! Nada! The keyword 'lock' doesn't even have an entry in the book's index.
   
   I'd also like to mention at this point that although the authors only devoted 47 pages to the core language, they felt it necessary to devote the majority of a 32 page chapter to a discussion of how to use Visual Studio. Any developer worth their salt ought to know how to use an IDE (remember this book is targeted at 'professional' developers), so learning how to use Visual Studio should be relatively straightforward. Even if it's not, those pages wasted introducing Visual Studio would have been better spent covering some of the gaping holes in the book's coverage of its stated subject matter, rather than a cursory introduction to some of the features in Visual Studio that are better covered by its own online help documentation and tutorials.
   
   Coming back to the second purpose - describing how functionality available through the standard Java libraries in Java can be achieved through the .NET libraries - I find that I cannot reasonably comment upon this in any great detail. True, there are the expected chapters devoted to data access (ADO.NET vs JDBC), ASP.NET and Windows Forms, and they might very well be of some use, judging from some of the other reviews. However, I was so disappointed with the poor content and lack of depth in the first few chapters of this book that I decided not to waste any further time with the rest of it. I found the other book that I bought along with this one to be an altogether better read. On the few occassions when I've looked back to this book as a reference source (I left the good book at home, so had to defer to using this one whilst at work), more often that not I've found that I've simply wasted my time with it, and moved on to find some other more useful reference source instead.
   
   The bottom line is, don't waste your money - this is one of the few books that I've actually thrown in the bin (a couple of times, in fact, though each time I end up fishing it back out. Throwing books away just feels so wrong, even if the book does belong with the rest of the rubbish).
   
   Chris (Cambridge, UK)
   
   P.S. I'm sorry that I can't remember the name of the other book - it was actually quite good!