I think that the difficult to understand, the face of a job interview written, Quick to see this book!

If you are a C + + beginners, please read this book, because the other books may be better than you see it, must choose a good book;
If you are looking for a job, please read this book carefully, because this book will teach you the necessary knowledge in your work, and believe that the grammatical problems you are about to face won't go beyond the scope of this book.
If you have been working for 1-3 years, then it is time to improve your skill level, and from the first chapter, the book explains the confusion in the work.
If you have been working for more than three years and are ready to develop your career as a software developer, I have nothing more to say and see for myself.

Enter a text tutorial

Go to the official video tutorials @ Youku

Enter Message

Enter 1000-C + + + + Exercises pen questions and answers about the book

In the 2014, I had the opportunity to contact a computer undergraduate at school and found that they were still using textbooks from the last century. It is a sad thing that China's IT industry is booming, but it is still using this ancient textbook for the industry to send talent. When those students do not know how to worry about, I can only say that even if the students can be admitted to Tsinghua University, it is not necessarily able to read this book. Let the industry evaluate the book, it has brought at least the following problems: ① discouraged the learner's interest, because it seems too difficult, so that a part of the original industry to leave the industry ② reduced the ability of the graduates, so that the company in the takeover of new graduates very headache.

It's not difficult, and it's interesting to say, but whether it's interesting or not depends on a good book guide. A bad book, unintelligible, let you half the effort, a good book, and the Persuasion, it will make you more effort. It is the intention of this book to keep the young students from suffering and avoid detours, so that the real return of the programming of C + + is interesting. Although the original idea began in the 2008, but like most people in the industry, I have no time and will to complete the book. It was not until 2014 that I made up my mind: it was time to do it. I can hardly challenge the existing monopoly, but I will be satisfied as long as some people see my book and gain from my book.

Let's talk about the title first. On the one hand, why is it a "C + + Learning Guide" rather than a "C + + Programming Guide"? Industry insiders know that C + + language is the extension of C language, syntactically compatible (cover) C language. However, given that some readers may be beginners, not necessarily understand the relationship between C and C + +, so in the title explicitly show that the book " both for C learners, but also for C + + learners ." This is also considered in the specific chapter arrangement, and for readers who need only C, the first 18 chapters (except the 14th chapter) should be studied, together with the Appendix "C + + and the language difference".

On the other hand, why is it called the Learning Guide instead of the Programming Guide? This is because of this grammar tutorial, which focuses on explaining grammar. And programming is a larger concept, not only to understand the grammar, but also to understand the actual operation and special knowledge (multithreading, mutual exclusion, network communication, graphical interface, etc.). But in order to let learners have certain engineering ability, this book specially supporting VC basic use, debugging method, standard C function usage, Standard Template Library (STL) usage.

And then again, the body part. The text is a total of 27 chapters, covering all the syntax points of C + +. Their order is carefully arranged, in order to learn the book is the most effective way of learning . Some of the chapters are marked with asterisks, which means: ① in the first round of study, this chapter should be skipped; it is generally not possible to go too far into these chapters, otherwise it will affect the continuity of learning ② skip this section, do not affect the subsequent chapters of the learning ③ some concepts in C + + belong to uncommon grammar, commonly used, or do not recommend use , all of which have special tips.

A central feature of this book is the use of memory views to explain the problem. The variable corresponds to memory and the memory has an address. Readers should understand this, and do not need to understand this very deeply. As long as the understanding of this point, C + + many seemingly difficult concepts will be the inevitable break. For example, the problem of pointers, the problem of dynamically allocating memory, and the problem of passing and referencing, if understood from the memory view, should become very simple.

Another key feature of this book is the avoidance of programming errors. Some things are well understood, but because they are not properly guided, the understanding of it is muddled. For example, char clearly represents an integer, but most textbooks call it a character. For example, explicitly indicate that the "pointer" and the int type are essentially the same address. For example, the problem of passing values and passing references is a core issue in C + + programming, which is clearly explained in this book.

Another core feature of this book is its strong engineering nature. Unlike most textbooks, this book is not only grammar, but also practical operation, so that the reader has the most basic engineering capabilities. Only grammar is done, so this book is also equipped with the standard C function number, STL Standard Template Library explanation and demonstration, as well as the engineers extremely important technology: debugging technology. And for the "programming specification" that only comes into contact with the enterprise, the author also wants to tell the reader at the beginning of programming to share some of the pressure on the training department of the enterprise. By the time the reader finishes this book, it is easy to get a blank look at the actual work, not like the previous graduates.

Finally, I'll say the appendix. Some people think that the appendix contains "Fan", which is not important. It is a serious mistake to understand this. The appendix exists because some knowledge is not suitable to be put on the main line, that is to say, it is impossible to follow the same sequence as the text. There are several reasons why the appendix becomes an appendix. ① It is comprehensive, does not belong to a chapter, a certain knowledge point, but with several chapters are related. For example, the techniques in the VC2008 debugging method can be applied to the 第3-16 chapters. ② It is long, inserted in the main body of the visual reversal of primary and secondary. ③ It is a summary of ④ it has a higher technical difficulty, through its learning can better understand the text.

In short, I hope this is an easy to read book, like I have read the good books, as good as to make people "impossible to read". I hope this book is good for most people, and that doesn't seem to worry. I hope this is a popular book, because the more it spreads, the more people benefit.

Shaofa

2015/3/10