5 comments about Fast Track C#.

1. This is an excellent book for C#. It covers almost every topic in C# in a consie, to-the-point fashion. Whether you are new or experienced programmer, this book will give you a head-start on mastering C# concepts. If you are doing MCAD, this is the book you should read first for brushing your concepts. I like the portability of this book (400 pages). Big thumps up for Wrox Fast Track series.



2. If you need to learn C# in a hurry, this is the book that will get you up to speed. The entire "Fast Track" series from Wrox were written to help you learn a subject fast and this is especially helpful if your employer decides to convert to C# or any other .Net technology or language. I purchased both Fast Track C# and Fast Track ASP.NET C# Edition together. I am impressed with both books. The Fast Track C# book is 413 pages and the chapters are not to long. This makes the reading very easy and the chapters don't take weeks to read. The book starts out with the basics of .NET and C# and then progresses to more advanced C# subjects. Note: The authors do not go into great detail on the various subjects and you should augment this book with a more advanced books on C#. There are ample examples but the authors do not provide the "results". This is a book for the intermediate developer making the conversion from Java or C++ but I think Visual Basic 6 developers will benefit from this book.

   In Chapter 1 - Overview of .Net and the CLR (Common Language Runtime), the authors explain the fundamentals of .Net.

   Chapter 2 - Introduction to C#, Chapter 3 - C# Basics, and Chapter 4 - Object-Oriented Features of C# provide the basics that you will need to know about C#. If you are coming from Visual Basic.Net, you might want to skip over these chapters but I read these chapters twice.

   The authors explain the more advanced features of C# in Chapters 5 - Advanced C#, 6 - .NET Programming with C#, and 7 - Working with the .Net Base Class. These chapters will help you get beyond the "Hello World" type of applications. These chapters provide some real-world examples.

   In Chapter 8 - Building Windows Applications, the authors explain all of the basics to windows development. The GUI or the presentation layer is what the end-user will be most familar with.

   The next chapters will help you with real-world applications that you may encounter.

   Chapter 9 - Assemblies and ILDASM.
   Chapter 10 - Data Access with ADO.Net
   Chapter 11 - COM and COM+ Interoperability
   Chapter 12 - ASP.Net
   Chapter 13 - Web Services




3. Wrox guys, you have done it really well. I am a beginner to C# but have previous experience with C/C++. Really wanted to get into the C# field. Tried 2-3 books but was bogged down by details everytime. Then I got hold of this book. Man this is awesome...really takes no time if you have some programming background..esp. OO related.
   
   Just devote 1-2 hours for each chapter..and this will cause the Sams 24 hours series some serious worries.



4. Excellent book. I am a VB 6 programmer making the jump to C#.
   
   C# instead of VB.NET? Mostly because there seems to be more contract jobs for C#.
   
   This is an excellent book. If you are a long time programmer like myself and want to get into C# programming I highly recommend this book. This book can make you a very functional C# programmer in a very few hours.



5. I thought this book did a great job at getting me up to speed on C#. I came from C++ and MFC development, so this definitely fit the bill for bridging me into C#.
   
   Worth the read!

5 comments about C++ for Real Programmers (For Real Programmers Series).

1. For the first time in my life I returned this book to the library. It is full of mistakes and so out of date that a lot of the discussion is either irrelevant or redundant. It uses old-style casts, is not const-correct, doesn't make any reference to the standard library. I've even seen a '#define kPoolSize 4096'! (p. 285) This is supposed to be an advanced book on C++ (although it repeats what exceptions and templates are) but read instead 'Design Patterns' and '(More) Effective C++'. You will know a lot more afterwards.



2. A worthy addition to my C++ library. The fact that Meyers and More Meyers are truly worthy of their universal acclaim, doesn't detract, in the least, from the value of this extremely well written text. This book is aimed at competent C++ programmers who want an in depth look at the motivations behind and the ramifications of a few well chosen C++ mechanisms. The comprehensive treatment of topics such as smart pointers and memory management offers a great introduction to the potential behind the somtimes exasperating scope of C++. Jeff Alger provides a real service for his target audience. Bravo... And Thanks.



3. Jeff's book isn't a tutorial, design handbook or step-by-step guide for C++ users, rather, it's an entry point into the C++ "Twilight Zone". It makes you think about C++ in completely new and exciting ways. I liked the book so much that I recommended it to all the members on my development team.



4. This is the a unique book I've read during my life. Its style is exceptionally relax.

   It discusses some confusing c++ syntax and three special themes: indirection (smart pointer etc), homomorphic class hierachies (multiple dispatch, envelope-letter idiom) and memory spaces (reference counting techniques and relateds classes).

   Some chpaters are especially intersting, for example:

   Chapter 8 about collections, cursors, and iterators, the cursor idiom was also discussed in <> as proxy, here, it is treated as kind of smart pointer.

   chapter 9 about transactions, which discussions how to implement this important feature with brillang pointers (variation of smart pointer)..

   I agree with the customer from Princeton, USA that the book is out of date & contains mistakes, for example

   It uses old-style casts, is not const-correct (rarely use const member functions), doesn't make any reference to the standard library. It does not use protected instead of public when defining a class used for base class only (page 78, class UnsafeNode). Other detail errors: for example, on page 100, the name of the template used is Ptr, and the template defined is SP; on page 156, class ArrayOfFoo contains member Foo** contents, constructed by contents(new Foo*[size]), and the destructor should be delete[] contents and not delete contents.

   Some important design errors, for example, on page 108, you see a template SPOS (stands for "Smart Pointer for Object Statistics").

   class Counter { ... public: int conversions; int members;

   };

   template class SPOS { private: Type* pointee; public operator Type*() { pointeee->conversions++; return pointee; } }

   It's better to hide data "members" and "converions" in private section of Counter, and define increment functions for conversions++ and members++.

   It is not exception safe, as almost every c++ book, except <>, for example, on page 119, we see

   template class class MP { private: Type* t; public: MP& opertor=(const MP& mp) { if (&mp != this) { delete t; t = new Type(*(mp.t)); } return this; } }

   We should replace delete t; t = new Type(*(mp.t));

   by (no self assignment test!)

   Type *tnew=new Type(*(mp.t)); delete t; t=tnew;

   Why? consider what happens if you delete t and an exception was thrown during t=new Type(*(mp.t)).

   For this class, we can also consider reference counting to avoid copy, see <> for a deeper discusion.

   Overall, this is a good book, but not must have. You can read <> and <> instead, but reading this book really will open your eyes, since its point of view is different and sometimes it's deeper. Concentrate on its interesting ideas and pay attention to its potential mistakes.




5. Many books are about how to write code. This book is about how to design software. Also it is a reference to many classic programming problems with practical tips for resolving.

   Jeff opens your eyes. This book in conjunction with Design Patterns, Advanced C++ Styles and Idioms, Effective C++ and More Effective C++ guarantees that you will sleep at night instead of caching bugs or rewriting the code :-)

3 comments about Framework-Based Software Development in C++ (Prentice Hall Series on Programming Tools and Methodologies).

1. Possibly the Wirfs-Brock of the late '90's (approach that is likely to be emulated by high-profile experts), this book has uncanny insight for framework-based development. Especially liked the coverage of domain analysis, which provides unique reuse benefits for developers.



2. This book is intended for those who already know C++ but also want to be exposed to the future trends of applying STL integrating with Object Oriented Database Systems and CORBA. Although STL, ODMG-93 and CORBA are covered in an introductory manner, their relationship with the process of framework design is very appropriate.

   Rogers writes well and the presents his topics in an organized manner. After reading it completely, I enjoyed rereading individual chapters in a random order to glean more of his insight. I recommend the book to those programmers that want to look into the future of effectively designing their products to be used in a distibuted environment.




3. Useful book, but consider the second example. Listing 2.5a: Spec() constructor in wrong place (causes multiple definition errors as is; move inside the struct) Listing 2.5b: needs #include ; references to npos should be string::npos. Listing 2.6: AVvector should be ValueExtractor::AVvector, AVmap should be ValueExtractor::AVmap. I thought this code was supposed to have been tested? When you finally fix it and compile it, you find C++ STL version: 128(text)+40(data)k, 33.2(usr)+11.0(sys)sec Plain C version: 8(text)+ 8(data)k, 7.2(usr)+ 0.8(sys)sec The plain C code is shorter and considerably simpler than listing 2.6, and runs 5.5 times faster (Alpha/OSF, cc,cxx) when reading 100 000 copies of the sample data in the book. What's more, I had to try three C++ compilers before finding one that could handle the code at all.

   There are good things later in the book, but this was a very off-putting introduction.

No comments about C / C ++ - Curso de Programacion.

1 comments about Complete Book of C Programming.

1. This is the only C book that I would recommend to anyone.
   I have several of C books, but after I bought this book, it is the only one I 've been using! Thanks to the author with clear explanation & good examples. I really appreciated his work, it is my honor to write this review, really! I borrow a lot of codes from this book. I have one in the office and another copy at home.
   It is "a complete Book of C programming" as the name mention. You will never be regret if you buy it, I assure you.

No comments about Borland C++ Power Programming/Book and Disk (Programming).

1 comments about PC Magazine Guide to C Programming.

1. If you don't know anything about C, this book will teach you. Easy to understand and logical steps in learning. An excelent foundation for C++ GET IT!!!

5 comments about Learn C on the Macintosh (2nd Edition).

1. I have to admit, this book was very good at teaching me the concepts of programming (structures, pointers, variables, algorithm design, etc) but for learning the C language it was terrible. Very little Macintosh programming is covered at all, it's just the dry ANSI C. Needless to say, I did not know how to program after using this book. However, it was a useful guide (albeit a bit confusing at times) to learning the basics of programming.



2. Now this is what a programming book for the mac is supposed to be! From the beginning this book takes you on a tour introducing you to the mac and how to program it, with useful source code and good exsamples.

   The only minor about this book is the fact it`s nearly 6 years old, but it`s not a big problem. It`s well written, and I can absolutely recommend it to everyone.




3. I've found this book a good introduction to C, it has refreshed my forgotten c knowledges with good explanations and examples.
   But I haven't learned about Mac programming. Just one chapter and not in a depth way.



4. I've found this book a good introduction to C, it has refreshed my forgotten c knowledges with good explanations and examples.
   But I haven't learned about Mac programming. Just one chapter and not in a depth way.



5. There is a new (February 2005) edition of this book available as a PDF from Spiderworks. It's an update for OS X, using the XCode software that comes free with OS X. Otherwise, the book is unchanged, including a few minor errors carried through from the 1995 edition. I don't know of any other resource for learning C on the Mac, but I don't hesitate to recommend it. It could use more programming exercises; I recommend supplementing it with Oualline's "Practical C Programming". After you've done this, read the ObjectiveC primer that comes with XCode and use a Cocoa programming book by Hillegas or Anguish.

No comments about C ++ Primer Plus.

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