Remember that indentation is useful for people, not the machine Correct use of identifiers, white space and documentation makes your program easier to understand for those humans reading it. Since you also will be reading your own program, you will want to be consistent and current with your documentation.
Properties of good style
1. Program that are easy to read and understand.
2. Programs that communicate the algorithm used in a form easy to follow.
3.Programs that are easy to modify and enhance to adapt to new and changing environments.( It is important to keep in mind that the programmer making the modifications may not be the initial author.)
Principles of good style
1. Clarity and simplicity
Avoid unnecessary complexity.When possible,use the straight forward method.Don't sacrifice clarity for cleverness.
2. Use meaningful identifiers
Choose names for constant, variables,functions,etc. , that accurately describe the purpose of the identifier.For instance, a, x, t are poor identifiers because they are meaningless whereas age, salary, and first_name are good choices.Constant should be all uppercase. Other identifiers should make use of the underscore"_" and uppercase letters to distinguish the words in an identifier (FirstName or first_name but not firstname).
3. One statement per line
4. Use proper indentation of control structures.
Be consistent with indentation.There are several styles to choose from but whichever you choose, be consistent! Some example are given below.Note the placement of the curly braces and the code.
Properties of good style
1. Program that are easy to read and understand.
2. Programs that communicate the algorithm used in a form easy to follow.
3.Programs that are easy to modify and enhance to adapt to new and changing environments.( It is important to keep in mind that the programmer making the modifications may not be the initial author.)
Principles of good style
1. Clarity and simplicity
Avoid unnecessary complexity.When possible,use the straight forward method.Don't sacrifice clarity for cleverness.
2. Use meaningful identifiers
Choose names for constant, variables,functions,etc. , that accurately describe the purpose of the identifier.For instance, a, x, t are poor identifiers because they are meaningless whereas age, salary, and first_name are good choices.Constant should be all uppercase. Other identifiers should make use of the underscore"_" and uppercase letters to distinguish the words in an identifier (FirstName or first_name but not firstname).
3. One statement per line
4. Use proper indentation of control structures.
Be consistent with indentation.There are several styles to choose from but whichever you choose, be consistent! Some example are given below.Note the placement of the curly braces and the code.
Posts
0 Comments:
Post a Comment