I am thinking about it, but the C procedure, my work is self-contained, and the top ten suggestions!
1. If you frequently urinate the LINT tool, according to its grammatical statement, this matter is due to the thinking of Lint's contemplation.
2, can not follow the NULL pointer, if so, the chaotic 俟 俟 君.
3, there is a big wisdom, knowing his business, and you will use the forced migration function parameters as the data type of the prototype period, so as not to neglect, cause the data type to dramatically.
4. When the file is not declared in the function prototype, if you are doing things, you must be cautious, and you should prevent it.
5, 汝 汝 核 字字, the cross-alliance of array operations. The ancient saints have a saying: Tasting the doctors to answer the answer "Right," I don't want the door to answer "I am, I don't have to think about it, I have to be a big truth," I will be a long-term, " This is the array, and the trip is the risk.
6. If the function declaration is mentioned, the error code cloud cloud will return to the error code, and the return value is cautious. Or have a school-reviewed statement to increase the code of the 汝, and the fingers are painful because of the knocking, and they are the same. Otherwise, 汝 固 以 为 事 难 难 得 慢 慢 慢 慢. 慢 慢.. 慢. 为.. 为 惩 惩 惩 惩 上 惩 惩 惩
7. If you should work in the study library function, improperly rewriting it. If so, the code will be short to read, and the mood of the 汝 will be clear and bleak.
8. If you are not willing, you should also bracket, indent the genus, so that the code is clear, you can learn from the latter. The wisdom of the 汝 决 决 解 解 解 解 解 解.... 团 团.. 团 团 团 团 团 团 团 团 团 团 团 团 团 团.
9. The six characters before the external identifier are different. This law seems to be rough, and it is awkward, but its utility can continue forever. If you don't say this, when he, when he wants to connect the procedure on the old work, you will scratch the scorpion, and the wolf is full.
10, or a family class, big words, cloud "Under the way, cax". He is waiting for this abandoned, abandoned it, disconnect, and avoid it. There are more people, I believe in the magic, thinking that the computer used the computer is frequently replaced, and the procedure can also apply for a long time. You can't ask for this wicked, you can remember.
How to write the most bad C language program
1. Rewote the standard library function, change the function name to the name you know.
2, use obscure, personalized, unmatched functions, so you will never leave your favorite platform.
3. Before all function calls, use the most accurate description of the function function, such as Printf ("Hello WORLD / N");
4, remember: Only the rookie uses the carriage return in the code; only the apprentice of the rookie uses tabs; the master will add countless embedded assembly instructions in the code.
5, "User Interface" is prepared for low energy, "users" will never be deal with your program through the interface.
6, if you have to note your code, then take a few comments from the code of others, put it in your code. This is the fastest, easiest way, and when you see other people read your code, what happiness is like a different expression on your face.
7. Try to use the pre-compilation option to use the new macro definition instead of the macro definition in the function library. This is called "do it".
8, you don't have to care about the details of the code, the compiler will help you get everything.
How to test the most bad C language program
1. As long as your code is compiled, the problem is sure to be in other people's code.
2, if you are writing the code, the problem is definitely in the untrusted library.
3. Declare to the tester: The error report is to tarnish me as the chief of the chief of the C language programmer! Why do you want to do this? You can't even read my code smoothly, how do you know that there is an error inside? 4. If the tester can read your code smoothly, then the kung fu you write bad code is not home.
5, announced: If those small corporate companies (or schools, wives, etc.) are willing to buy a C compiler for you, there will be no mistakes.
6. Insert or remove blank lines in any position of the code, recompile, execute.
7. If there is any problem, use the assembly language to override your program. This will not reduce the error of the program, but this will ensure that no one can find the wrong location, no one can devalue your programming ability.
