A summary of lessons learned from C + +

The following is what you should pay attention to when you learn C + +.

1. Think of C + + as a new language learning (and C doesn't matter!) It's true. ）；

2. See "Thinking in C + +", do not see "C + + into die mutually";

3. See "The C + + programming Language" and "Inside the C + + Object

Model ", do not because they are difficult and we ourselves are beginners so do not look;

4. Do not be confused by VC, BCB, BC, MC, TC and other words-they are integrated development environment, and we have to learn a language;

5. Do not let go of any small programming problem that seems simple-they are often not so simple, or they can draw out a lot of knowledge.

6. will use Visual C + +, does not mean that you will C + +;

7. Learning class is not difficult, template, STL, generic

Programming is still the case-the difficult is long-term adherence to practice and spare no effort to read;

8. If it is not genius, want to learn programming do not want to play games-you think you have done, in fact, your C + + level and your ability to clear the high--in fact, you can always remember: learning C + + is to make up the game;

9. See the Visual C + + book, is not learning C + + language;

10. Impetuous people easy to say: xx language is not enough, you should learn yy;--is not your own!?

11. Impetuous people are easy to ask: what should I learn;--don't ask, learn is right;

12. Impetuous people are easy to ask: xx rich way;--suggest you rob a bank;

13. Impetuous people easy to say: I want the Chinese version! My English is not good! --no? Learn!

14. Impetuous people easy to ask: xx and yy which good;--tell you, all good--as long as you learn it;

15. Impulsive people are divided into two kinds: a) only to wait and see and not to learn, B) only learn and not adhere to the people;

16. It is better to keep the outdated technology in mind by hanging on to the lips of fashionable technology;

17.c++ not only supports object-oriented programming language;

18. One of the best ways to learn programming is to read the source code;

19. Do not at any time consider that the book in your hands is sufficient;

20. Please read the standard C + + Bible (Chinese version: standard C + + book), master C + + standards;

21. Read the book, please look carefully, read the book, please bite the bullet to see;

22. Don't expect to see what you can remember and master in the first book-see the second and third times;

23. See "Effective C + +" and "more effective C + +" and "exceptional C + +";

24. Do not stay in the cradle of the integrated development environment, to learn to control the integrated development environment, but also to learn to use the command-line approach to processing programs;

25. Discuss meaningful C + + knowledge points with others instead of arguing xx line or yy with ZZ which is good;

26. Please see "Program design Practice", and strictly in accordance with its requirements to do;

27. Do not think that the meanings and functions of C and C + + are exactly the same, because there are some syntax and keywords that look the same;

28.c++ is by no means the so-called "expansion" of C--if C + + begins with the name Z language, you will not associate the C and Z languages so tightly;

29. Please do not think that the study of XX language and then modify the C + + will have a problem-you are only learning a new language only;

30. After reading "Inside the C + + Object Model" to determine whether they have learned C + +;

31. The secret of learning programming is: programming, programming, re-programming; http://hovertree.com/menu/cpp/

32. Please pay attention to the following books: "C + + Object-oriented programming (C + + effective object-oriented Software construction)" Object-oriented Software construction (object-oriented software Construction) "Design Patterns", "The Art of computer programming";

33. Remember: Object-oriented technology is not just C + + proprietary;

34. Please input the program example of the book into the computer practice, even if the supporting CD has the source code;

35. Expand the meaningful examples that are seen in the book;

36. Please attach importance to the exception handling technology in C + +, and apply it to your own program effectively;

37. Always review the procedures that you have written before and try to rewrite and apply the new knowledge that you have learned.

38. Do not omit any of the book exercises-please complete and record the problem-solving ideas;

39.c++ language and C + + integrated development environment to learn and master at the same time;

40. Since the decision to learn C + +, please insist on learning, because the purpose of learning programming language is to master the design technology, and programming technology is cross-language;

41. Let the C + + language of the various platforms and development environment to fierce competition, we have to learn the C + + language itself mainly;

42. Do not stop immediately when you write half of the C + + program and find that you are using it in a very poor way; Please complete the remainder as soon as possible to ensure the integrity of the design, then analyze your mistakes and redesign and write them (see 43);

43. Don't be impatient, the design of C + + class is really not easy, the class and their class design level in their own program is perfected and developed in the continuous programming practice;

44. Never do not follow certain rules that you are not proficient in because the program is "very small"--good habits are cultivated, not once remembered;

45. Every time you learn a C + + difficult point, try to explain this knowledge to others and let him understand-you can speak clearly to show that you really understand;

46. Record the points of knowledge that you have overlooked or not understood while communicating with others;

47. Please keep on your own writing procedures to make higher requirements, even if your program version number will become version 100.XX;

48. Keep all the programs you've written--one of your best builds;

49. Please do not be impetuous person;

50. Please love c++!

Add:

Some thoughts on C + + learning, I hope to have some help for beginners

1. If you have never been in touch with C + + before, then the first C + + tutorial chosen is particularly important, and I think you can choose from the following criteria:

A. The standard C + + is explained, after all, C + + has changed a lot than before.

B. The requirements are comprehensive, but not very deep, which will help you to have a comprehensive understanding of C + +, lay a good foundation, and easy-to-understand textbooks can also accelerate the progress of learning, so that they maintain a sense of accomplishment.

C. To have a complete example of how each knowledge point is used, please note that what is said here is not a single piece of code. Because you've never been exposed to programming in C + + before, the complete code can make you have a whole concept and be able to do a lot of practice quickly, since programming is the beginning of imitation, and the complete code tells you a complete step. Don't have to speculate on your own.

D. Recommendation: "C + + Primer Plus"

2. When you have a certain foundation, you should choose some books to quickly improve yourself. This kind of book is characterized by not only teaching you how to use it, but also how to think about it, and how easy it is for you to read it. It means far-reaching, not something you can read it over.

Recommendation: "Thinking in C + +", "effective C + +", "more effective C + +"

"C + + programming language" ... "Meditation on C + +"

3. The next step is to read and practice the books presented in the second stage. Because these books are a far-reaching one, each person will have different results based on their own foundation, for example, if your foundation has not reached a certain height, then you are blind to some profound technology, do not believe? You can try it and see how many new things you'll find when you come back and read a previous book.

Recommendation: http://www.cnblogs.com/roucheng/p/cpphong.html

A summary of lessons learned from C + +