Linux内核编码风格（Linux kernel coding style）.docVIP

Linux内核编码风格（Linux kernel coding style） Linux kernel encoding style This short article describes the preferred coding style of the Linux kernel. Coding style is very personal, and I dont impose my views on anyone. However, the Linux kernels code, after all, is what I have to be able to maintain, so I prefer its coding style to my preference. Please consider this at least. First of all, I would recommend printing a GNU coding standard instead of reading it. Burn it, its just a gesture. Then, please look: The first chapter: indentation The Tabs (TAB) is 8 characters in size, so the indent should be 8 characters in size. Some rebel advocates try to turn the indentation into 4 (or even 2)! The length of this character), as if trying to get the PI (case, PI) is defined as 3 is the same. Rule: the idea behind the indentation is to clearly define where a control block starts and where it ends. Especially after you keep staring at the screen for 20 hours, if you have large indentation. You will be more likely to discover the benefits of indentation. Now, some people say that 8 character indentation causes the code to be too right and looks uncomfortable on a 80 character wide terminal screen. The answer to this question is, if you have more than 3 levels of indentation, youre a little confused, and you should change your program.. In short, the indentation of 8 characters makes the program easier to read, and when you hide the function too deep, multi-level indentation is a very intuitive warning. Take heed of this warning message. The second chapter: put curly braces Another idea in the C program is the placement of curly braces. Unlike indent sizes, there is no technical reason for placing curly braces. But, like Brain Kernighan and Dennis Ritchie the prophet shown is the preferred method: the left brace at the end of the line, put in the right bracket. Namely: If (x, is, true) { We do y } However, there is another case, is the function: the function should be put on the r