Write the 10 cheats of the C program

Gadget its technology, but the C program, work to its own, the top ten recommendations!

1, you should frequently catalytic lint tools, according to its grammatical statement to practice internal forces, this matter is due to the lint of the thinking of the decision is far away.

2, can not following null pointers, if not, chaos will soon be king in the other shore.

3, the longitudinal has the talent great wisdom, knows its matter to be no harm, RU also when all is forced to be moved the function parameter is the prototype time data type, lest the momentary negligence, causes the data type to your repay blood.

4, if the header file does not declare the return value type in the function prototype, you when kiss this matter, more must be cautious repeatedly, safekeeping descend your body.

5, you must kiss the nuclear string, array operation of the bounds or not. The ancient sage has a word: "Try to pray for the people to answer" "but also", do not reply to the gate "I do not need to worry about the chest," he increasingly will be Xie "-the period of short, the obtained by long, this in the array, the most dangerous place also.

6, if the function declaration mentioned in the exception will return error code so, RU when carefully check the return value. Or have a check statement to make your code more than a few times, so that your fingers because of the pain of the key to the inexplicable thing, Ru also when so. Otherwise, it is rare for you to see this anomaly, and God will punish your arrogance.

7, you should study the library function, improper handwriting rewrite it. If your code will be short and easy to read, your state of mind will be refreshing and indifferent.

8, if you do not want to, you should also borrow brackets, indented the genus, so that your code bridge differences clear, for the latter reference. Your great wisdom is to be solved by doubt, but in the laying of mysteries, confusions style is absolutely not.

9, the external identifier before the six characters when different. This law seems humble, and few, but its utility can continue forever. If you do not from this remark, a future, you want to connect the program on the fallacy, will scratching, unkempt, awkward phase to do now.

10, or a race, the heat of the big words, the cloud "in the Vax, Murphy." In this heresy, thou shalt forsake it, and renounce it, and avoid it.

Even more different people, believe in the magic way, thought that the longitudinal use of your computer frequent replacement, your procedures can be applied for a long time. And thou shalt not associate with such wicked men, and bear in mind.

How to write the worst C language program

1, rewrite the standard library function, change the function name to the obscure name you know.

2, the use of obscure, personalized, can not be ported library functions, so you will never leave your favorite platform.

3, before all function calls, use the most accurate description of function functions of annotations, such as

printf ("Hello World");

4, remember: Only rookie in the Code to use carriage return line break; only the novice apprentice uses tabs; The master adds countless inline assembler instructions to the code.

5, "user interface" is for the imbecile preparation, "user" is never through the interface with your program to deal with.

6. If you have to annotate your code, just draw a few comments from someone else's code and put it in your code. This is the quickest and easiest way to do it, and how happy it is when you see someone else reading your code with a strange look on your face.

7. Use the precompilation option as much as possible, using the new macro definition instead of the existing macro definition in the function library. This is called "do what you can."

8, you do not care about the details of the code, the compiler will help you fix everything.

How to test the worst C language program

1, as long as your code through the compilation, the problem is certainly in other people's code.

2, if you write the code, the problem must be in those untrusted library of functions.

3, to the tester declared: Error report is tainted me as a C language programmer the most pure reputation of the despicable lies! Why are you doing this? You can't even read my code smoothly, how do you know there's a mistake?

4, if the tester can smoothly read your code, then you write bad code of Kungfu still not home.

5, announced: If those stingy companies (or schools, wives, etc.) willing to buy you a set of C + + compiler, the program will not have any errors.

6. Insert or delete blank lines at any point in the code, recompile, execute.

7, if there are problems, rewrite your program in assembly language. This does not reduce the error of the program, but it will ensure that no one can find the wrong location and no one can degrade your programming ability.