Summarize N steps to learn programming. 1: reading .. Listen to others, what is good. Just caught a book began to learn.
2: After reading it. I feel that I want to do something. I don't know what the compiler is, and I don't know the difference between the IDE and the compiler. Of course, I don't know the difference between VC / TC / C . Write a program. Conversing the requirements in the book. Write a program. So started the Coding ... 3: Write it. I compile. F9 (TC is F9. I still remember). Why don't you run? A reading. Oh, it is CTRL-F9. by. Why don't you still run. After several twists, I finally found N Complier Error (I used to see the output of the compiler.).
4: This will last. Why don't you still run? Oh, there is a link error. What elseviVled Symbol? Don't understand. Depressed. Never report a mistake. What to break something. More depressed. 5: It can finally run. I have been running halfway. Listening to people say this is the legendary program crash. But I think my program has no problem. Look at the left. Look at it. There is no problem. How to crash? The teacher is so teaching. Yep. Think about it. It is definitely a problem with the compiler. . . . . . 6: I found that it would have an incorrect program that seems to be correct. I finally didn't collapse. Ok. Go out to turn two circles. Excited carefully. What is the result is wrong. Take a pen, don't do it. How to do? How to see the program so that you have a correct result. Biting, what to do, what to do, God, Lord, save me. 7: Crazy for a Merger. I finally know that the breakpoint debug can be set. . . . . Debuging .... Please don't bother. . . . .
?
