The so-called reread, of course, because it has been read. I remember that when I read it last time, I basically understanding C is a new C language plus Class. Oh, I read this book at the time, I wanted to learn grammar: I didn't understand that the words were talking about it. Then start jumping into grammar learning, but I found that the examples didn't understand, I didn't understand what I did, jumping, and quickly jumped over the book, then doubting my own IQ, while swearing the translator, see The C of money can go. This reread, the feeling is finally understanding some stuff, first of all: The name is C programming idea, it is understood that it is not a book based on the syntax. This book C grammar explains most of the design issues in conjunction with practical applications. The author emphasizes that C is used to design applications, not the simple accumulated algorithm in process design. (Useful containers and algorithms in C STL, this book is just over, more description is how we should build a self-container, how to solve the problem in practical reality.). I think, if you want to see the grammar, or money, then C Primer is relatively appropriate. As for the standard library of C , it must be preferred to choose a C standard library.
At the same time: it is not a book of software engineering (design technology). It does not have a system's explanation of object-oriented design, but more in the main line of C grammar, according to the author's practical experience, explain the understanding of C characteristics and the application in design, all said designs The method did not distinguish between the main second, and there is no main line or induction. Personally, Java can make pure object-oriented objects, so seeing Java-oriented books may more understand the object-oriented design ideas. Three: The examples of this book are very classic. If you go carefully, you will find some examples to include classic design patterns, and some are some of the key implementation techniques of the C class library we are well known. This also reflects the power of the C language. IV: The program guidelines of the Appendix B after the book are very worth seeing to see if they want to see how their book is understood, see Appendix B. One of the reasons why, all answers are in the book. I remember that when I was watching the code written by people, I always don't understand why this is written, and many people have written like this, and I have never been speaking on the grammar. There is an answer in this book. More, more clear principles, you can look at Effective C and Move Effectivec ,
5: C language Some lower things. This book has not been mentioned in the depth exploration of the C object model book, such as multi-inheritance complexity, copy-constructed compiler generation principle, etc. . Look at this book, there are several places that will not understand.
Translation level. OK, of course, the translator's C level may not be very high, some statements are not passing, or some misinterpret, but if you have a certain understanding of C and object-oriented objects, you can read more times, understand the original author. intention. Harvest: Some coding custom programming principles, I didn't pay attention before, I can remember this time. There are some deeper understandings for C , and there is a different sentence. 2004-11-29
