C Programming Naming Conventions

Variables in C

• Variables are named storage locations in C that hold data which can be changed during program execution.
• Each variable has a specific data type which determines the type of data it can store.

Rules for Variable Naming in C

• Must start with a letter (uppercase or lowercase) or an underscore.
• Can be followed by letters, digits, or underscores.
• Cannot contain spaces or special characters (like @, $, %, etc.).
• Case-sensitive – variable and Variable are distinct identifiers.

Reserved Words (Keywords) in C

• Keywords are predefined words in C that have special meaning and cannot be used as identifiers.
• Common keywords include int, float, return, if, else, while, etc.

Naming Conventions in C

• Generally agree on meaningful, descriptive names that indicate the purpose of the variable.
• CamelCase or underscore_case is commonly used for multi-word variable names.

Case Sensitivity Rule

• C is case-sensitive with identifiers, meaning name, Name, and NAME constitute separate variables.

Length of Variable Names

• There is no fixed limit on variable name length, but using concise names (within practicality) is encouraged for readability.

Recommended Starting for Variable Names

• It is recommended to begin variable names with lowercase letters, especially in functions and local variables.

Separating Words in Identifiers

• Words within identifiers can be separated using underscores for better readability, e.g., user_name, totalSum.

Importance of Consistency in Naming Conventions

• Consistent naming enhances code readability and maintainability, making it easier for others (or future you) to understand the code.

Legal Identifiers in C

• Legal identifiers must comply with naming rules and avoid using reserved keywords.

Using Variables in C Programming

• Each variable must be declared before it can be used in the program, allowing the compiler to allocate memory and check types.

Importance of Variable Declarations

• Placing each variable declaration on its own line with descriptive comments aids clarity and reduces the chance of errors.

Significance of Comments Before Code Chunks

• Comments before logical segments of code explain their purpose, enhancing understanding and facilitating debugging.

Use of Spaces Around Operators

• Spaces around arithmetic and assignment operators improve code readability, helping to distinguish between operations easily.

Purpose of Using Blank Lines

• Blank lines are used to enhance code readability, providing visual breaks between logical sections of code.

Benefit of Blank Lines Between Declarations and Executable Statements

• Adding a blank line between the last variable declaration and the first executable statement clarifies the transition from declaration to execution.

Importance of Consistent Indentation

• Consistently indenting the body of the program improves readability, making it easier to follow the program's structure and flow.