More efficient css code writing Page 1/3_Experience exchange

This is a question that many web page makers and developers are concerned about. There is probably no magic that can guarantee that your style sheet will be reduced to a certain percentage in one go, but reasonable CSS coding and organization skills can indeed help you write clearer and more efficient code more efficiently. Naturally, style The reduction in table size also reduces download time.​

1. Typesetting:

1. Add appropriate spaces between keywords and operators.

2. Add blank lines between relatively independent program blocks

3. Longer statements, expressions, etc. should be written in multiple lines.

4. The new lines must be indented appropriately to make the layout neat and the statements readable.

5. Long expressions should be divided into new lines at low-priority operators, and the operators should be placed at the beginning of the new line.

6. If there are long expressions or statements in loops, judgments and other statements, they must be divided appropriately.

7. If the parameters in the function or procedure are long, they must be divided appropriately.

8. It is not allowed to write multiple short statements in one line, that is, only write one statement in one line.

9. The beginning of a function or procedure, the definition of a structure, and the code in statements such as loops and judgments must be indented.

10.C/C language uses curly braces '{' and '}' to delimit a program block. When writing a program block, '{' and '}' should each occupy an exclusive line and be located in the same column. , while being left aligned with the statements that refer to them. The above indentation method must be adopted at the beginning of the function body, the definition of the class, the definition of the structure, the definition of the enumeration, and the programs in if, for, do, while, switch, and case statements.

2. Comments

1. Comments should be simple and clear.

2. Comment while writing the code, modify the code and modify the corresponding comments at the same time to ensure the consistency between the comments and the code.

3. Comment where necessary and the amount of comments should be moderate. The content of the annotation must be clear and concise, and the meaning must be accurate to prevent ambiguity in the annotation. Keep comments adjacent to the code they describe, that is, the proximity principle of comments.

4. Comments on the code should be placed adjacent to them above, not below.

5. Comments on the data structure should be placed adjacent to it, not below; comments on each field in the structure should be placed to the right of this field; in the same structure Comments in different fields should be aligned.

　6. Comments on variables and constants should be placed adjacent to or to the right above them.

7. Global variables should have more detailed comments, including descriptions of their functions, value ranges, which functions or procedures access them, and precautions when accessing them.

8. There must be necessary annotation information at the head of each source file, including: file name; version number; author; generation date; module function description (such as functions, main algorithms, internal The relationship between parts, the relationship between this file and other files, etc.); list of main functions or processes and historical modification records of this file, etc.

9. There must be necessary annotation information in front of each function or procedure, including: function or procedure name; function description; input, output and return value description; calling relationship and called relationship description, etc.

3. Naming

1. Shorter words can be abbreviated by removing the "vowels";

2. For longer words, you can take the priority of the first few symbols of the word, and use parentheses to clarify the order of operation of the expression to avoid using the default priority.

　3. Use Hungarian notation