C ++ experts learn advice and learn with an open mind ~~ [Reprinted], advice and learn modestly

C ++ experts learn advice and learn with an open mind ~~ [Reprinted], advice and learn modestly

1. Take C ++ as a new language learning (it has nothing to do with C! True .);

2. Read Thinking In C ++ instead of C ++.

3. read "The C ++ Programming Language" and "Inside The C ++ Object Model". Do not read them because they are difficult and we are beginners;

4. Do not be confused by words such as VC, BCB, BC, MC, and TC-they are all integrated development environments, and what we want to learn is a language;

5. Don't let go of any seemingly simple small programming problem-they are often not that simple, or they can draw a lot of knowledge points;

6. Visual C ++ is used. It does not mean that you can use C ++;

7. It is not difficult to learn classes. templates, STL, and generic programming are also not difficult. What is difficult is to stick to the practice for a long time and to read a wide range of books;

8. if you are not a genius, you don't want to play games if you want to learn programming. You think you have done it. In fact, your C ++ level has not increased with your customs clearance capability. In fact, you can always remember: C ++ aims to compile games;

9. Reading Visual C ++ books cannot learn the C ++ language;

10. impetuous people can easily say: XX language is not good, so you should learn YY; -- you can't do it yourself !?

11. impetuous people may easily ask: What should I learn? -- don't ask, it's right to learn;

12. It is easy for impetuous people to ask: do XX have money? -- We suggest you rob a bank;

13. impetuous people may say: I want a Chinese version! I cannot use English! -- No? Learn!

14. impetuous people may easily ask: XX and YY, Which is better? -- tell you, good.-As long as you learn;

15. impetuous people can be divided into two types: a) those who only wait and do not learn; B) those who only learn but do not stick to it;

16. It is better to keep outdated technologies in mind when talking about fashionable technologies;

17. C ++ not only supports object-oriented programming languages;

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

19. Do not think that the books in your hands are sufficient at any time;

20. Please read The "The Standard C ++ Bible" (Chinese Version: Standard C ++) and master The C ++ Standard;

21. read carefully the books you can understand. Read the books you can't understand;

22. Don't expect to read the first book to remember and master anything-please read the second and third times;

23. Please refer to Objective C ++, More objective C ++, and predictional C ++.

24. Do not stay on the cradle of the integrated development environment, learn to control the integrated development environment, and learn to process programs using the command line method;

25. Discuss meaningful C ++ knowledge points with others, rather than quarreling XX rows or which is better for YY and ZZ;

26. Please refer to "program design practices" and strictly follow the requirements;

27. Do not think that C and C ++ have the same syntax and keyword, so they have the same meaning and function;

28. C ++ is by no means an "extension" of C. If C ++ is called the Z language at the beginning, you will not be so closely connected with the Z language;

29. do not consider the problem of changing C ++ after learning XX language-you are just learning a brand new language;

30. After reading "Inside The C ++ Object Model", check whether you have learned C ++;

31. The secret to learning programming is: programming, programming, and re-programming;

32. pay attention to the following books: C ++ efficient Object-Oriented Programming (C ++ efficient Object-Oriented SoftwareConstruction) and Object-Oriented Software Construction) design Patterns The Art of Computer Programming

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

34. Please input the program examples in the book into your computer for practice, even if the supporting CD contains the source code;

35. Expand the meaningful examples seen in the book;

36. Pay attention to the Exception Handling Technology in C ++ and apply it to your own programs;

37. I often review my previous programs and try to rewrite them to apply the new knowledge I have learned;

38. Do not miss any exercise questions in the book-please finish all the exercises and record the solution ideas;

39. The integrated development environment of C ++ and C ++ should be learned and mastered at the same time;

40. Since learning C ++ is decided, please keep learning, because the purpose of learning programming language is to master programming technology, while programming technology is cross-language;

41. Let's compete fiercely in various platforms and development environments of the C ++ language. We should focus on learning the C ++ language itself;

42. when you write half of the C ++ program but find that your method is poor, please do not stop immediately; please complete the remaining parts roughly as soon as possible to ensure the integrity of this design, analyze your own errors and redesign and write them (see 43 );

43. Don't worry, it is really not easy to design C ++ class; the class and the class design level in your program are improved and developed in constant programming practices;

44. Never follow certain rules that you are not proficient in because the program is "very small"-Good habits are developed rather than remembered at once;

45. Every time I learned a C ++ difficulty, I tried to explain this knowledge point to someone else and let him understand it. It was just clear that you really understood it;

46. Record the knowledge points that you ignore or do not understand when communicating with others;

47. Please constantly put forward higher requirements for your own programs, even if your program Version will change to Version 100.XX;

48. save all the programs you have written-that is one of your best accumulation;

49. Do not be impetuous people;

50. Please love C ++!