(I finally finished reading the c language programming, and had a general understanding of it. You can use C language as a tool to manage some projects that need to get results through numerical calculation.? In retrospect, I think I have used some learning methods that I personally think are practical. I have roughly experienced several processes such as watching, practicing, simulating, exchanging, and self realization.? At the beginning, when I touched "C language", I didn't buy a computer. I bought the book "C Programming" compiled by Professor Tan Haoqiang. At that time, I chose the method of "looking more". About three times from beginning to end; And they made marks in some places that they did not understand. If I didn't understand "pointer" and "linked list" at that time, I bought a computer after about half a month. Here, what I want to say is that if a person learning "programming" just stays in the "sit and talk", I think it is far from enough. When I bought a computer, I bought a set of "C programming" in the "computer city" From then on, I can only say that I have just started to speak C language. I thought that the "education CD" was designed for comparative science/learning; It is very helpful for my study. In particular, there are some interpretations of definitions. Some concepts that I didn't understand came to me soon. It took me about a week to read the educational content in the CD. And selectively made some "multiple choice questions" and "question and answer questions" about basic knowledge; I have a deeper understanding of some basic concepts.? At the next moment, I began to put some exercises in the book into TRUBOC and check its operation results one by one. (The requirement is that I can't self program at this time.). First, we want to fully understand its computing process. Second, I want this process to cultivate my interest in "programming".? Later, I selectively began to do some exercises given at the back of the chapters in the book. First of all, it is based on your own programming method on paper (it has been introduced in the forum, but I don't think it is very good.) And thought programming. Then, check it again and input it into the computer. At this time, I want to learn how to better debug "C programming". Because I think "debugging" is also an important step for programming. It allows you to constantly summarize experience from failure; It can prevent some routine mistakes you often make. Here, I call it "conventional error" as opposed to "logical error". The principle I distinguish "errors" is that when you program, some errors are caused by human input errors or forgetting. Moreover, I personally think that beginners may often make such mistakes (because I often make such mistakes myself). For example, when "inputting" the code of an input function, I often forget to input the "address sign". Other mistakes are due to some unforeseeable errors in the program coding; I call these mistakes "logical errors". This source code can usually be compiled; However, we can not get the results we want. For example, when solving the "chicken problem", because I used integer variables, the result value is different from the imagined result value.? I had a habit when I was programming; That is, every time a program is completed; If you encounter some problems in "debugging"; I usually use/
...
/Write on the top of the program; And date it. In this way, I personally think we can have a clear understanding of our learning progress.? I don't want to talk much about "logical mistakes"; However, I summarized that I made the following "regular" mistakes: 1. When entering the scanf function, forget to enter the address operator. 2. Forget to input the relevant "file prototype description". 3. Forget to enter break to exit the circular sentence when using the switch sentence. 4. When defining multiple variables, multiple input; semicolon. 5. One or more fewer left parentheses.
C Collection of Speech Materials.chm
..... Too many files omitted)
收藏
