First chapter introduction
Question 1.1: The purpose of this chapter? A: The scope of this book is explained, as well as what is the first version of this book, and the electronic version, and finally introduces the agreement. This chapter discusses the purpose of this book and subsequent use agreements, and discussions even if you have bought the first version of this book, read the electronic version, you should still buy this book. Question 1.2: What is "C FAQs"? A: Frequently Asked Questions (Agree, referred to as FAQS) is an answer to object-oriented programming and C language problems. Each FAQ provides an in-depth guidance for problems. In order to clarify the principles of the problem, many FAQs provide a complete and operable example program. FAQS is more like "problem truth". FAQs is not necessarily what readers have been asked, but they should be readers will ask. Although these problems are not discussed, most of the issues are summed up from the actual experience. So the author of this book decided to make these problems, rather than repeating the same principle. Through this book, you can gradually grasp the ability of object-oriented programming and C language. From now on, read these common questions!
Question 1.3: The reader of this book is suitable? A: Professional software developers. This paper-related developers include: programmers, architects and designers. People with programming experience learning object-oriented C will be more effective, this book assumes that the reader has a certain programming background. Don't be familiar with C language, but if you can be familiar, it will be quite beneficial.
Question 1.4: Is this book telling only C itself? A: This book focuses on the aspect of object-oriented (Object-Oriented) in C . Therefore, as long as you see "C " in this book, you should contact "Object-Oriented" (occasionally I also marke "Object-Oriented" to remind the reader). Another focus of this book is to actually use some of the methods when C , but will not explore all language details of C itself. That is, this book does not look at the syntax and characteristics of the C language as the traditional C books. This book is concerned about the key characteristics of C (for example, its OO characteristics) and how to use these features more effectively. This is another reason because the system of C languages is too large, and the developers are too difficult to fully understand and use its characteristics too difficult. It can be said that the success of this book is the expression of C ideas, not to simply describe the rules of C . Master C ideas, supplemented with long-term programming practices, can effectively reduce development risks (such as using some effective C combination rules, rather than simple stacking C grammar). It is more confusing characteristics in C , the same method on the surface, often makes the developer in the selection of dilemmas, so mastering C ideas is critical to improving development efficiency. This book also tried to link software architects, software designers and C programmers (see Chapter 4).
