Code neatness -- format

Preface

When writing code, you can't just focus on whether the code function is perfect , It should also check whether the format of the main code conforms to the specification , Maybe you think " Make code work " Is the top priority developers should consider , however , If there is no good code format , In the iteration and modification of later versions , The readability of the code will have a far-reaching impact on the subsequent modification behavior

---

One 、 Vertical format

1、 Read from the top down

When you read the newspaper , You'll want a headline , Tell you the subject of the newspaper , How the first paragraph is the outline of the whole story , But the details are hidden , Then read on , The details show slowly , Until you know when the whole story happened , Location and so on .
Newspapers consist of many articles , Most are short and exquisite , A few are a little long , But few of them occupy a full page , If the newspaper only carries a very long story , No one will read it .
So should our code , From the top down , From left to right .

2、 Conceptual vertical separation

Between defined functions , Should not be close together , Every function should be separated by blank numbers ;

3、 Approach vertically upwards

Closely related code should be close to each other , Member variables leave no spaces

4、 Closely related functions are close to each other

Avoid jumping from one function to another , So keep jumping . One function calls another , Try to ensure that the called function is next to the caller , It is more convenient to read in this way .

5、 Member variables should be declared in the class header

Function variables should be declared at the beginning of the function , If you need to declare in a function , Consider whether the function needs to be split into multiple functions for execution ;

Two 、 Horizontal format

1、 The width of a line of code

Keep lines of code short , Avoid lines of code that exceed your screen , If exceeded , Consider wrapping lines or changing more refined variable names

2、 Horizontal separation and proximity

Add 、 Subtraction 、 Multiplication 、 Assignment compliance （+、-、==、=） The symbol should be followed by a space , Indicates low priority , Multiplication 、 division （*、/） There should be no space between , Indicates high priority , The comma of a function argument should be followed by a space .

3、 Horizontal alignment is not necessary

Don't do that , There is no need to

4、 Code indentation

Even if the code has only one line , You should also write brackets , Line break , Don't save space

5、 Avoid recycling , Judgment statement , Function body is empty

summary

Write the code , Last review code, Check vertical formatting from top to bottom , Check horizontal formatting from left to right